Just a quick suggestion - may be it would be better to store everything in lower case as long as case is ignored in the UI? I've spent few hours trying to figure out, why foreign keys ingestion is not working, and it appeared that I ingested columns in the original (upper) case and foreign key information was in lower case. As long as everything in the UI was in the lower case, that was not obvious at all 😅

many databases have case sensitive names. This will cause issues

Then I'd say they should not be converted to lower case in the UI

that I agree with.

@handsome-belgium-11927 This is definitely not an ideal experience.... I agree in the UI we should reflect the natural casing of fields so that this is more obvious

Hi folks! I’ve migrated this over to our new feature request portal - please upvote/subscribe so you can keep up with our progress https://feature-requests.datahubproject.io/b/Developer-Experience/p/entity-metadata-should-reflect-the-native-casing-of-fields

you never call, you never write, YEESH! thanks for the tag, and for all the effort in navigating these slack posts to a separate backlog!