Hello everyone, I'm having some issues with DataHu...
# troubleshoot
g
Hello everyone, I'm having some issues with DataHub. At the company I work for, the organization of tables and views within the same BigQuery dataset is done by adopting a naming pattern. In other words, tables are only given lowercase names separated by '_' while views follow the upper camelcase pattern. However, there are some cases in which the name of the table and the view are distinguished by only 1 capital letter (e.g., <dataset>.order and <dataset>.Order). With that, in the UI when I search for 'order' I get several 500 messages and a JSON parsing error message and when I try to explore in search of the table, I only find the view. As I can't change the defaults adopted, does anyone have any idea how I can solve this?
I suppose these bugs occur because of some process step that considers case insensitive names or urns.
I avoided these errors by separating the ingestion of tables and views into different executions, each in an ENV. Thus, the URNs of views and tables are differentiated by PROD/DEV, but I don't think this is a good practice. Would it be possible to add a "urn_suffix" parameter in the ingest process?
l
Hi @gentle-camera-33498! I’m chatting with @mammoth-bear-12532 - we’ll need to think about this a bit more.. would you mind opening a GH issue for us to track this?
g
Hello Maggie, I will create the issue on GitHub. For now, using the ingestion ENVs solves my problem. But I can try to recreate the problem to give more details about it. what do you think? Feel free for asking anything about that!
l
Glad that assigning ENVs does the trick for now; thanks for taking the time to open an issue!