https://datahubproject.io logo
Join Slack
Powered by
Hello, for our use-case I would have to add two fa...
# getting-started
l
Hello, for our use-case I would have to add two fabrics (test, preprod) to datahub, to have consistent browsing paths/naming. I have found that one has to add these fabrics to an enum in various places and rebuild, or has the new noCode metadata update changed something in this regard?
g
For browse paths, no-code does have a solution
Datahub generates browse paths automatically if no browse path is provided
but you are also able to emit a BrowsePaths aspect for any browsable entity
that will override the default browse path and allow you to customize your browse path structure
l
Thanks for the answer. I looked a bit into the browsepaths and realized they alone won't work as i have datasets which are only uniquely identified by datasetname+fabricname. So I guess I have to add them.
Is adding custom fabrics something you would consider for a feature sometime in the future? I'm not sure how difficult this would be and if the work one has to do for this would be justified by the payoff.
g
Did you have to edit code aside from the 
.pdl
schema files?
We are considering making Fabric Type more flexible- I agree it is a bit rigid right now.
b
Yeah we should move this from enum to string
Shouldn't be too difficult to do
If you wanted to take a stab!
l
I'm not sure if this would only work with changing the .pdl, in the 0.7 version I also changed UrnUtils.java, a few snapshot.json and found fabtric types in two .ts files and two graphql files.
b
You are correct that this exists in graphql also. We’d have to make the change there as well
2 Views
Open in Slack
PreviousNext
Powered by