Working with a physical address in lakeFS, the address is URL decoded.

If the path contains percent-encoding (e.g., file%3Aname.txt), lakeFS converts it to file:name.txt.

This affects operations like import where this transformation of the file address fails to find the data as part of import and skips it (not found).

lakeFS should preserve the exact string supplied for the object path in the physical address.