Tracker should interpret and display external dataset schemas
Description
When viewing external datasets in Tracker where the schema is stored as a user property, it should be smart enough to interpret that and display it in the schema section of the details page
Release Notes
None
Attachments
1
12 Jul 2016, 12:01 AM
Activity
Show:
Russ SavageAugust 8, 2016 at 11:35 PM
So you want us to hardcode it instead?! Yes this could be made into a Tracker API that could be called for any dataset to get the schema. Assuming that exists, not much change would be needed in the frontend i assume.
Ajai NarayananAugust 8, 2016 at 11:07 PM
@Russ Savage Yes we can do that. But we are again hardcoding things in UI for every use case. What happens in the future if we bump onto scenarios where we need to check for something name for schema property? Can the Tracker API provide this as one "schema" property for UI so that we can safely use that all the time
Russ SavageAugust 8, 2016 at 6:44 PM
Is there any way to have fallback checks in case the schema property isn't there? in this case, it is the "parquet.avro.schema" property you need to check for.
Ajai NarayananAugust 8, 2016 at 5:53 PM
@Russ SavageToday the UI is hardcoded to check for 'schema' property in the metadata call for a dataset ("http://<host>:<port>/v3/namespaces/default/datasets/<dataset-name>/metadata"). Is there a way for UI to know which property is a schema property for us to show it under schema column?
Todd GreensteinAugust 5, 2016 at 8:55 PM
Need to determine LOE to show schema in UI. Assigning to Ajai.
Won't Fix
Pinned fields
Click on the next to a field label to start pinning.
When viewing external datasets in Tracker where the schema is stored as a user property, it should be smart enough to interpret that and display it in the schema section of the details page