Microsoft Fabric OneLake Connector > Mappings for Microsoft Fabric OneLake > Configure a lakehouse override in mappings

Configure a lakehouse override in mappings

When you read from or write to Microsoft Fabric OneLake, you can specify the lakehouse override path in the advanced source and target properties to override the object path at runtime. The lakehouse override path can be an absolute or a relative path.

Consider the following guidelines when you override the object path:

Absolute Path

When you specify an absolute path in the lakehouse override property, the lakehouse override path overrides the object path.

Note: You must prefix the lakehouse name to the absolute path.

The following table exemplifies if you include the lakehouse name in the absolute path, the object path is correctly generated in the logs:

Object path	Lakehouse override path	Object path generated in logs
<<WorkSpace Name>>/<<Lakehouse Name>>/<<Files>>/<<Folder1>>/Object.txt	<<Lakehouse Name>>/<<Files>>/<<Folder2>>	<<<Lakehouse Name.lakehouse>>/<<Files>>/<<Folder2>>

The following table exemplifies if you do not include the lakehouse name in the absolute path, the object path is incorrectly generated and the mapping fails:

Object path	Lakehouse override path	Object path generated in logs
<<WorkSpace Name>>/<<Lakehouse Name>>/<<Files>>/<<Folder1>>/Object.txt	<<Folder2>>/<<Folder3>>	<<Folder2>>>.lakehouse/<<Folder3>>

Relative Path

When you specify a relative path in the lakehouse override property, the lakehouse override path appends to the object path.

Note: You must not prefix the lakehouse name to the relative path.

The following table exemplifies if you do include the lakehouse name in the relative path, the object path is correctly generated in the logs:

Object path	Lakehouse override path	Object path generated in logs
<<WorkSpace Name>>/<<Lakehouse Name>>/<<Files>>/<<Folder1>>/Object.txt	/<<Folder2>>/<<Folder3>>	<<Lakehouse Name.lakehouse>>/<<Files>>/<<Folder1>>/<<Folder2>>/<<Folder3>>

The following table exemplifies if you include the lakehouse name in the relative path, the object path is incorrectly generated and the mapping fails:

Object path	Lakehouse override path	Object path generated in logs
<<WorkSpace Name>>/<<Lakehouse Name>>/<<Files>>/<<Folder1>>/Object.txt	/<<Lakehouse Name>>/<<Files>>/<<Folder2>>	<<Lakehouse Name.lakehouse>>/<<Files>>/<<Folder1>>/<<Lakehouse Name>>/<<Files>>/<<Folder2>>