-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI support for customProperties in DatasetProperties aspect #1730
Comments
Link to slack discussion: https://datahubspace.slack.com/archives/CV2UXSE9L/p1594430884039000 |
Is this feature helpful for the display of tags information? |
I was focused more on |
may be we can look at two steps
|
I really want to know the progress of this work, and I look forward to setting some tags on the dataset on the page. Due to some practical factors, some descriptive meta-information cannot be collected at present, and it can only be configured through the post page. |
Is your feature request related to a problem? Please describe.
The aspect
com.linkedin.pegasus2avro.dataset.DatasetProperties
has a fieldcustomProperties
that is valuable in representing data properties that don't quite fit in any other (current) data model which is very valuable. However, the UI doesn't currently display any custom properties.Describe the solution you'd like
Please add a UI representation (tab?) to convey all custom properties in that aspect. Perhaps similar to the Schema tab?
Describe alternatives you've considered
No other alternatives have been considered
Additional context
For the DataHub users/devs that are not able to afford forking the repo and creating their own data models, having basic support (UI display) for non-off-the-shelf data assets is extremely valuable because it can be used as a stop-gap while developing more explicit data models (or waiting for "official" DataHub models to be released).
As DataHub begins to have a greater presence and influence in users'/devs' tech stack, more prioritization and resources can be allocated into developing code (or making open-source contributions) that enables them to move data out of
customProperties
and into a more explicit data model.The text was updated successfully, but these errors were encountered: