[
https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-376:
-----------------------------------
Fix Version/s: (was: trunk)
> UI: Use the Schema API of the backend to populate details for Schema tab
> ------------------------------------------------------------------------
>
> Key: ATLAS-376
> URL: https://issues.apache.org/jira/browse/ATLAS-376
> Project: Atlas
> Issue Type: Sub-task
> Reporter: Hemanth Yamijala
> Assignee: Darshan Kumar
> Priority: Major
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-376-ATLAS-314-v1.patch,
> ATLAS-376-ATLAS-314-v2.patch, ATLAS-376-ATLAS-314.patch, schema_response.json
>
>
> Currently, the information that comes in the schema tab seems to be populated
> from the entity information that is fired to get the details of the entity.
> In the API, we have a specific API to get schema of any dataset. This API
> should be used to populate the schema tab instead of using information from
> the entity information.
> Specifically:
> * Use the entity API, something of the form /lineage/hive/table/$name$/schema
> where $name$ is the name attribute of the entity in question. For e.g. for
> hive_tables an example URL would be
> /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where
> default.tbl16@primary is the name.
> * The results of the API should be parsed to populate the details of the
> Schema table. (Will attach a sample response, and expand more details on this
> point in the comments).
> * If the results contains a referenceable entity, i.e. has an $id$, (for e.g.
> Hive columns), it should put up the 'Add tag' action and should allow the
> user to associate a tag to that entity. In addition, it should put up the
> list of available tags currently associated with the entity. (Note this
> functionality is similar to how the search results are handled for
> reference-able entities)
> * The API could return a 404 if the name does not exist, or the name is
> something that does not represent a dataset. This should be handled, and upon
> receipt should not display the Schema tab at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)