<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/e02b4daba764483782f99a52f6afe915&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/e02b4daba764483782f99a52f6afe915-71059c69d52b880e.gif</thumbnail_url><duration>104.447</duration><title>Fixing Ownership Lookup with Special Characters 🛠️</title><description>I have known myself Talhamjid and I participated in an open metadata hackathon where I picked four issues, raised PRs, and one PR was merged while three are still in review. The merged issue was about ownership association with special characters. The lookup path relied on search queries that did not safely handle query construction, and name matching had fuzzy behavior that caused incorrect matches in edge cases with similar names. I fixed it with two parts: properly encoding and filtering the name input for search, and trying exact name lookup first before falling back to search. I did not request any specific action from viewers.</description></oembed>