search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.28k stars 21.46k forks source link

house or House ? #122106

Closed mikeblakeuk closed 5 months ago

mikeblakeuk commented 6 months ago

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.

PesalaPavan commented 6 months ago

@mikeblakeuk Thanks for your feedback! We will investigate and update as appropriate.

TPavanBalaji commented 6 months ago

Hi @mikeblakeuk

According to this below article Lakehouse is correct.

https://learn.microsoft.com/en-us/azure/data-factory/connector-microsoft-fabric-lakehouse?tabs=data-factory

If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

mikeblakeuk commented 6 months ago

So the Open API is "wrong"?

Naveenommi-MSFT commented 6 months ago

@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.

jonburchel commented 5 months ago

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