atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <>
Subject [jira] [Commented] (ATLAS-339) UI: Improve the flow for associating tags to entities
Date Fri, 27 Nov 2015 07:15:10 GMT


Hemanth Yamijala commented on ATLAS-339:

There are a couple of ways we get the list of entities:

* Search by specific DSL of form <type> where name='<name>': E.g. Search term:
hive_table where name=‘tbl42’ OR hive_column where name=‘column421’.  Typically, this
gives pointed and good results.
* Search by type: E.g. Search term: hive_table. Shows all entities of this type. Locating
the specific entity of interest here involves manual lookup.
* Search by freetext: E.g. Search term: name of table or column. Since this is a full text
search, the results might involve a lot of extraneous results. For e.g. searching for a table,
also lists the column descriptors.
* Search by selecting a tag: E.g. Search term is a tag. Lists all entities tagged with this

On the entities returned via search, we can add tags in the following views:

* Search views by specific DSL or type return results that contain the name and also a column
that allows for tags to be added.
* Search views by other types, display entity GUIDs. Clicking on them takes one to the details
page for that entity from where tags can be added.
* If the GUID is a hive_table, there is an additional UI element called Schema in the details
page which lists the columns of the table.

In addition to these current modes, the proposal is to make the following improvements:

* All search results (by DSL, free text or by trait) should return a name and GUID at a minimum.
UI should display the name and link using the GUID.
* Add / Remove tag functionality should be available in the search results view whenever the
result has a referenceable entity. 

> UI: Improve the flow for associating tags to entities
> -----------------------------------------------------
>                 Key: ATLAS-339
>                 URL:
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Hemanth Yamijala
> A primary use case for Atlas is to assist discovery and policy management through metadata
that is managed by it. Tags (aka Traits) is a way of enabling this.
> From a UI perspective, the flow to assign tags to entities involves the following steps:
> * Getting to an entity of interest (currently realized through search results and details
page for an entity)
> * Adding tags to entities.
> This JIRA is to discuss and implement changes to improve the experience of this flow.

This message was sent by Atlassian JIRA

View raw message