Closed mikeblakeuk closed 6 months ago
@mikeblakeuk Thanks for your feedback! We will investigate and update as appropriate.
Hi @mikeblakeuk
According to this below article Lakehouse
is correct.
If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
So the Open API is "wrong"?
@mikeblakeuk Thank you for bringing this to our attention. I've assigned this task to our content author, @jianleishen, who will carefully review it and provide their valuable insights. The feedback they provide will help guide any necessary adjustments by the PM/ EM Teams.
Hi @mikeblakeuk, and thanks for your feedback. I checked and confirmed in fact, LakeHouse is the correct casing for the API usage, despite it not matching the convention we use in the docs, where Lakehouse is correct. The product team might consider a change to the API to correct that, but to engage them regarding a change to an API, please open a new free support case from the Azure portal, selecting the menu at the top left of the screen to choose its last item, Help + support, and then choosing Create a new support case. Our support team can follow up and the product group might be able to change this to the correct casing. They might hesitate to do so though, too, since it could be a breaking change for existing code that uses it. Since I confirmed for now that this is the correct casing for use of the API (even if you're correct that it's wrong for our usage standard in the docs), I will close this issue out. However, we can continue this discussion here in this thread if necessary, even after it's closed. #please-close
Should the type be Lakehouse or LakeHouse as per https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/datafactory/Azure.ResourceManager.DataFactory/src/Generated/Models/LakeHouseTableDataset.cs
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.