![]() You can perform CRUD operations on any folder or file created within these managed folders. Fabric-managed folders include the top-level folder in an item (for example, /MyLakehouse.lakehouse) and the first level of folders within it (for example, /MyLakehouse.lakehouse/Files and /MyLakehouse.lakehouse/Tables). You must perform these operations via Fabric experiences, such as the Fabric portal or Fabric management APIs. OneLake does enforce the Fabric item structure, meaning you can't create, read, update, or delete (CRUD) certain folders, even if you're the item or workspace owner. Only HEAD calls are supported at the workspace level and account level, as you must make changes to the Fabric tenant and Fabric workspaces in the Fabric administration portal. OneLake doesn't support creating, updating, or deleting workspaces or items through the ADLS Gen2 APIs. For more information on ADLS Gen2 APIs, see Azure Data Lake Storage Gen2 REST APIs. ![]() The following sections describe how OneLake differs from ADLS Gen2, from unsupported request headers to changes in response headers. While OneLake matches all ADLS Gen2 behavior wherever possible, not every concept in ADLS Gen2 has a direct correlation to OneLake. For example: '/mylakehouse.lakehouse/Files/'.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |