[jira] [Commented] (ATLAS-412) UI : Lineage arrow head to are leading to miss understanding for end user
[ https://issues.apache.org/jira/browse/ATLAS-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1666#comment-1666 ] Anilsg commented on ATLAS-412: -- Need look for new graph > UI : Lineage arrow head to are leading to miss understanding for end user > - > > Key: ATLAS-412 > URL: https://issues.apache.org/jira/browse/ATLAS-412 > Project: Atlas > Issue Type: Task >Reporter: Anilsg >Assignee: Anilsg > > Lineage arrows leading user to miss understand the flow of connectivity, > This need to worked with centralizing the arrow head on the path/node > connecting length. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-502) UI: Provide the ability to search for tags
[ https://issues.apache.org/jira/browse/ATLAS-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-502: - Attachment: ATLAS-502_v0.patch > UI: Provide the ability to search for tags > -- > > Key: ATLAS-502 > URL: https://issues.apache.org/jira/browse/ATLAS-502 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.7-incubating > > Attachments: ATLAS-502_v0.patch > > > In the left hand navigation of Atlas, where tags are displayed, there needs > to be an ability to search for tags (in the event that there are too many > tags to display). The functionality should be similar to what is found in the > Ambari Hive view; see: > https://monosnap.com/file/1aQ1uRwikvnjdhqKOSVvDfTv1ui2zl > A user should be able to type in a partial query (no wildcards required) and > the list of tags displayed should dynamically update based on search box > contents. > The query should be executed against what is cached (vs. querying the > backend). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-502) UI: Provide the ability to search for tags
[ https://issues.apache.org/jira/browse/ATLAS-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156124#comment-15156124 ] Anilsg commented on ATLAS-502: -- Implemented as expected, Tested on http://162.249.6.39:3367/#!/search On Left nave the Input box is added on Text enter Hit the Result’s in nav will be sorted for matching text, Below the list “Load more..” Text is add on click of more content will be displayed. If the list count / filtered count is less then the limit count the "Load more.." will be disabled. > UI: Provide the ability to search for tags > -- > > Key: ATLAS-502 > URL: https://issues.apache.org/jira/browse/ATLAS-502 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.7-incubating > > > In the left hand navigation of Atlas, where tags are displayed, there needs > to be an ability to search for tags (in the event that there are too many > tags to display). The functionality should be similar to what is found in the > Ambari Hive view; see: > https://monosnap.com/file/1aQ1uRwikvnjdhqKOSVvDfTv1ui2zl > A user should be able to type in a partial query (no wildcards required) and > the list of tags displayed should dynamically update based on search box > contents. > The query should be executed against what is cached (vs. querying the > backend). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-213) UI: When searching for Tag/Trait, Search results show guid instead of name
[ https://issues.apache.org/jira/browse/ATLAS-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-213. -- Resolution: Fixed Patch applied for ATLAS-287, Hence resolving > UI: When searching for Tag/Trait, Search results show guid instead of name > -- > > Key: ATLAS-213 > URL: https://issues.apache.org/jira/browse/ATLAS-213 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Rohit > Fix For: trunk > > > UI: When searching for Tag/Trait, Search results show guid instead of name. > See: https://monosnap.com/file/m9857DlVtUWCwkAbRQ3kcOZla6pdaa -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (ATLAS-465) UI : Guid on details page
[ https://issues.apache.org/jira/browse/ATLAS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reopened ATLAS-465: -- Patch applied for ATLAS-287, Hence resolving > UI : Guid on details page > -- > > Key: ATLAS-465 > URL: https://issues.apache.org/jira/browse/ATLAS-465 > Project: Atlas > Issue Type: Improvement >Reporter: Anilsg >Assignee: Anilsg >Priority: Critical > > As per comments of Erik on ATLAS-287 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-465) UI : Guid on details page
[ https://issues.apache.org/jira/browse/ATLAS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-465. -- Resolution: Fixed > UI : Guid on details page > -- > > Key: ATLAS-465 > URL: https://issues.apache.org/jira/browse/ATLAS-465 > Project: Atlas > Issue Type: Improvement >Reporter: Anilsg >Assignee: Anilsg >Priority: Critical > > As per comments of Erik on ATLAS-287 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-287) UI: GUID on table details page
[ https://issues.apache.org/jira/browse/ATLAS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-287: - Attachment: ATLAS-287_v1.patch > UI: GUID on table details page > -- > > Key: ATLAS-287 > URL: https://issues.apache.org/jira/browse/ATLAS-287 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Labels: patch-available > Fix For: trunk > > Attachments: ATLAS-287_v0.patch, ATLAS-287_v1.patch, Screen Shot > 2015-11-06 at 9.49.57 pm.png > > > On the column details page, a GUID is displayed for the DB instead of the > name of the DB. We should display the fully qualified name of the database as > the href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-287) UI: GUID on table details page
[ https://issues.apache.org/jira/browse/ATLAS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15054428#comment-15054428 ] Anilsg edited comment on ATLAS-287 at 2/1/16 6:41 PM: -- To go with, This has been implemented with api call for each row to get the name. Tested on http://52.33.160.226:3218/#!/search Currently this is the performance concern, What we have doing to show the Name Note : Name to be sent from back end in response, was (Author: anilg): To go with, This has been implemented with api call for each row to get the name. Tested on http://52.27.169.250:3217/#!/search?query=PII Currently this is the performance concern, What we have doing to show the Name Note : Name to be sent from back end in response, > UI: GUID on table details page > -- > > Key: ATLAS-287 > URL: https://issues.apache.org/jira/browse/ATLAS-287 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: trunk > > Attachments: ATLAS-287_v0.patch, Screen Shot 2015-11-06 at 9.49.57 > pm.png > > > On the column details page, a GUID is displayed for the DB instead of the > name of the DB. We should display the fully qualified name of the database as > the href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-213) UI: When searching for Tag/Trait, Search results show guid instead of name
[ https://issues.apache.org/jira/browse/ATLAS-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124943#comment-15124943 ] Anilsg edited comment on ATLAS-213 at 2/1/16 6:43 PM: -- To go with, This has been implemented with api call for each row to get the name. Tested on http://52.33.160.226:3218/#!/search?query=PII Currently this is the performance concern, What we have done to show the Name Note : Name to be sent from back end in response, This is same as ATLAS-287 was (Author: anilg): To go with, This has been implemented with api call for each row to get the name. Tested on http://52.33.160.226:3217/#!/search?query=PII Currently this is the performance concern, What we have done to show the Name Note : Name to be sent from back end in response, This is same as ATLAS-287 > UI: When searching for Tag/Trait, Search results show guid instead of name > -- > > Key: ATLAS-213 > URL: https://issues.apache.org/jira/browse/ATLAS-213 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Rohit > Fix For: trunk > > > UI: When searching for Tag/Trait, Search results show guid instead of name. > See: https://monosnap.com/file/m9857DlVtUWCwkAbRQ3kcOZla6pdaa -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-287) UI: GUID on table details page
[ https://issues.apache.org/jira/browse/ATLAS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126720#comment-15126720 ] Anilsg commented on ATLAS-287: -- [~yhemanth] [~rohitl] [~bergenholtz] The patch "ATLAS-287_v0.patch" is updated with the current master, please do review and let us know if there is anything. Thank you > UI: GUID on table details page > -- > > Key: ATLAS-287 > URL: https://issues.apache.org/jira/browse/ATLAS-287 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: trunk > > Attachments: ATLAS-287_v0.patch, Screen Shot 2015-11-06 at 9.49.57 > pm.png > > > On the column details page, a GUID is displayed for the DB instead of the > name of the DB. We should display the fully qualified name of the database as > the href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-424) UI: The UI Should not expose guids
[ https://issues.apache.org/jira/browse/ATLAS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124942#comment-15124942 ] Anilsg commented on ATLAS-424: -- To go with, This has been implemented with api call for each row to get the name. Tested on http://52.33.160.226:3217/#!/search?query=PII Currently this is the performance concern, What we have done to show the Name Note : Name to be sent from back end in response, This is same as ATLAS-287 > UI: The UI Should not expose guids > -- > > Key: ATLAS-424 > URL: https://issues.apache.org/jira/browse/ATLAS-424 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Rohit > > In the cases where guids are displayed in the UI, we should change to display > something meaningful to users. In the cases where the REST API does not > support or provide the name, Jiras should be filed to enhance the API as > necessary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-213) UI: When searching for Tag/Trait, Search results show guid instead of name
[ https://issues.apache.org/jira/browse/ATLAS-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124943#comment-15124943 ] Anilsg commented on ATLAS-213: -- To go with, This has been implemented with api call for each row to get the name. Tested on http://52.33.160.226:3217/#!/search?query=PII Currently this is the performance concern, What we have done to show the Name Note : Name to be sent from back end in response, This is same as ATLAS-287 > UI: When searching for Tag/Trait, Search results show guid instead of name > -- > > Key: ATLAS-213 > URL: https://issues.apache.org/jira/browse/ATLAS-213 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Rohit > Fix For: trunk > > > UI: When searching for Tag/Trait, Search results show guid instead of name. > See: https://monosnap.com/file/m9857DlVtUWCwkAbRQ3kcOZla6pdaa -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-270) Performance - UI : Minify css files and combining view level
[ https://issues.apache.org/jira/browse/ATLAS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124788#comment-15124788 ] Anilsg commented on ATLAS-270: -- [~shwethags] We have the code ready for this, This is not patch sent, We will be sending once ATLAS-318 is applied http://mprhost.com/hw/atlas/patches.html --> Please refer the page for list of patches ready with code > Performance - UI : Minify css files and combining view level > - > > Key: ATLAS-270 > URL: https://issues.apache.org/jira/browse/ATLAS-270 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Anilsg > Fix For: trunk > > > Performance : Minify css files and combining view level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-270) Performance - UI : Minify css files and combining view level
[ https://issues.apache.org/jira/browse/ATLAS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124787#comment-15124787 ] Anilsg commented on ATLAS-270: -- [~shwethags] We have the code ready for this, This is not patch sent, We will be sending once ATLAS-318 is applied http://mprhost.com/hw/atlas/patches.html --> Please refer the page for list of patches ready with code > Performance - UI : Minify css files and combining view level > - > > Key: ATLAS-270 > URL: https://issues.apache.org/jira/browse/ATLAS-270 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Anilsg > Fix For: trunk > > > Performance : Minify css files and combining view level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-456) Loader of all Ui functionality until the api response, On Esc stop loader
Anilsg created ATLAS-456: Summary: Loader of all Ui functionality until the api response, On Esc stop loader Key: ATLAS-456 URL: https://issues.apache.org/jira/browse/ATLAS-456 Project: Atlas Issue Type: Task Reporter: Anilsg Assignee: Anilsg Priority: Critical Loader for all the api call's from UI, The loader to be shown until the backend Api is response is success or failure If the Api is taking to long time to respond, On User Esc button press Loader to be stopped. This need's to implemented through out application, in frame work level We need to show loader until the Api call is responded, By block the screen for any other click's. So that user will no be allowed to click any other button's, Only "Esc" to stop the loade -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-311) UI: Local storage for traits - caching [not cleared on refresh] To be cleared on time lapse for 1hr.
[ https://issues.apache.org/jira/browse/ATLAS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106654#comment-15106654 ] Anilsg commented on ATLAS-311: -- ATLAS-318 will be addressed for entire application level, the code is ready. In Upcomming 3 patches will be sending ATLAS-318 patch. > UI: Local storage for traits - caching [not cleared on refresh] To be cleared > on time lapse for 1hr. > > > Key: ATLAS-311 > URL: https://issues.apache.org/jira/browse/ATLAS-311 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-311-issue1.png, ATLAS-311.patch, > ATLAS-311_v2.patch, ATLAS-311_v3.patch > > > Local storage for traits - caching [not cleared on refresh] To be cleared on > time lapse for 1hr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-311) UI: Local storage for traits - caching [not cleared on refresh] To be cleared on time lapse for 1hr.
[ https://issues.apache.org/jira/browse/ATLAS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-311: - Attachment: ATLAS-311_v3.patch > UI: Local storage for traits - caching [not cleared on refresh] To be cleared > on time lapse for 1hr. > > > Key: ATLAS-311 > URL: https://issues.apache.org/jira/browse/ATLAS-311 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-311-issue1.png, ATLAS-311.patch, > ATLAS-311_v2.patch, ATLAS-311_v3.patch > > > Local storage for traits - caching [not cleared on refresh] To be cleared on > time lapse for 1hr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-311) UI: Local storage for traits - caching [not cleared on refresh] To be cleared on time lapse for 1hr.
[ https://issues.apache.org/jira/browse/ATLAS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105707#comment-15105707 ] Anilsg commented on ATLAS-311: -- [~yhemanth] [~bergenholtz] [~rohitl] PFA patch "ATLAS-311_v3.patch", with updated code for comments. . small pixelated block coming up . Refresh icon to refresh the Tags on create Tag with Title on mouse hover > UI: Local storage for traits - caching [not cleared on refresh] To be cleared > on time lapse for 1hr. > > > Key: ATLAS-311 > URL: https://issues.apache.org/jira/browse/ATLAS-311 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-311-issue1.png, ATLAS-311.patch, > ATLAS-311_v2.patch, ATLAS-311_v3.patch > > > Local storage for traits - caching [not cleared on refresh] To be cleared on > time lapse for 1hr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-425) UI: Column in search results should link to Table view
[ https://issues.apache.org/jira/browse/ATLAS-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103202#comment-15103202 ] Anilsg commented on ATLAS-425: -- [~bergenholtz] Need your inputs on this. > UI: Column in search results should link to Table view > -- > > Key: ATLAS-425 > URL: https://issues.apache.org/jira/browse/ATLAS-425 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Rohit > > If a user selects a type column in the search results, it should link to the > Table view page and highlight the column on the schema tab. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-434) Add tags does not support non-English characters
[ https://issues.apache.org/jira/browse/ATLAS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-434: - Attachment: Screen Shot 2016-01-14 at 10.43.06 pm.png Screen Shot 2016-01-14 at 10.42.52 pm.png Screen Shot 2016-01-14 at 10.41.40 pm.png Screen Shot 2016-01-14 at 10.41.33 pm.png > Add tags does not support non-English characters > - > > Key: ATLAS-434 > URL: https://issues.apache.org/jira/browse/ATLAS-434 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating > Environment: sandbox >Reporter: Chethana >Assignee: Anilsg > Attachments: 434.png, Screen Shot 2016-01-14 at 10.41.33 pm.png, > Screen Shot 2016-01-14 at 10.41.40 pm.png, Screen Shot 2016-01-14 at 10.42.52 > pm.png, Screen Shot 2016-01-14 at 10.43.06 pm.png > > > Steps: > Create a tag with non English characters 漢字 > Expected: > Tag 漢字 should be displayed. > Actual: > Tag is displayed as �� -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-434) Add tags does not support non-English characters
[ https://issues.apache.org/jira/browse/ATLAS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096844#comment-15096844 ] Anilsg commented on ATLAS-434: -- [~ckrishnakumar] [~yhemanth] On create tag the special non-english characters as expected as well the entity is getting created. On get “api/atlas/types?type=TRAIT” Traits the response api is not responding with proper characters, Thats the reason we are getting ��, Do we have to send some additional request from UI to get this. Please check on this, PFA "434.png" screen shot. > Add tags does not support non-English characters > - > > Key: ATLAS-434 > URL: https://issues.apache.org/jira/browse/ATLAS-434 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating > Environment: sandbox >Reporter: Chethana >Assignee: Anilsg > Attachments: 434.png > > > Steps: > Create a tag with non English characters 漢字 > Expected: > Tag 漢字 should be displayed. > Actual: > Tag is displayed as �� -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-434) Add tags does not support non-English characters
[ https://issues.apache.org/jira/browse/ATLAS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-434: - Attachment: 434.png > Add tags does not support non-English characters > - > > Key: ATLAS-434 > URL: https://issues.apache.org/jira/browse/ATLAS-434 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating > Environment: sandbox >Reporter: Chethana >Assignee: Anilsg > Attachments: 434.png > > > Steps: > Create a tag with non English characters 漢字 > Expected: > Tag 漢字 should be displayed. > Actual: > Tag is displayed as �� -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-434) Add tags does not support non-English characters
[ https://issues.apache.org/jira/browse/ATLAS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096844#comment-15096844 ] Anilsg edited comment on ATLAS-434 at 1/14/16 2:22 AM: --- [~ckrishnakumar] [~yhemanth] On create tag the special non-english characters as expected as well the entity is getting created. On (“api/atlas/types?type=TRAIT”) Traits api response, it is sending for non-english characters as ��, Do we have to send some additional request parameter from UI to get this. PFA "434.png" screen shot. was (Author: anilg): [~ckrishnakumar] [~yhemanth] On create tag the special non-english characters as expected as well the entity is getting created. On get “api/atlas/types?type=TRAIT” Traits the response api is not responding with proper characters, Thats the reason we are getting ��, Do we have to send some additional request from UI to get this. Please check on this, PFA "434.png" screen shot. > Add tags does not support non-English characters > - > > Key: ATLAS-434 > URL: https://issues.apache.org/jira/browse/ATLAS-434 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating > Environment: sandbox >Reporter: Chethana >Assignee: Anilsg > Attachments: 434.png > > > Steps: > Create a tag with non English characters 漢字 > Expected: > Tag 漢字 should be displayed. > Actual: > Tag is displayed as �� -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-311) UI: Local storage for traits - caching [not cleared on refresh] To be cleared on time lapse for 1hr.
[ https://issues.apache.org/jira/browse/ATLAS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096443#comment-15096443 ] Anilsg commented on ATLAS-311: -- [~yhemanth] Patch "ATLAS-311_v2.patch" is update with master code, Tested on http://162.212.133.190:3263/#!/search Do apply this patch, once this is applied will be sending ATLAS-388. > UI: Local storage for traits - caching [not cleared on refresh] To be cleared > on time lapse for 1hr. > > > Key: ATLAS-311 > URL: https://issues.apache.org/jira/browse/ATLAS-311 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-311.patch, ATLAS-311_v2.patch > > > Local storage for traits - caching [not cleared on refresh] To be cleared on > time lapse for 1hr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-311) UI: Local storage for traits - caching [not cleared on refresh] To be cleared on time lapse for 1hr.
[ https://issues.apache.org/jira/browse/ATLAS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15094625#comment-15094625 ] Anilsg commented on ATLAS-311: -- [~yhemanth] : Added refresh and Time based invalidate. Can be tested on : http://162.212.133.190:3263/#!/search > UI: Local storage for traits - caching [not cleared on refresh] To be cleared > on time lapse for 1hr. > > > Key: ATLAS-311 > URL: https://issues.apache.org/jira/browse/ATLAS-311 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-311.patch > > > Local storage for traits - caching [not cleared on refresh] To be cleared on > time lapse for 1hr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-311) UI: Local storage for traits - caching [not cleared on refresh] To be cleared on time lapse for 1hr.
[ https://issues.apache.org/jira/browse/ATLAS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15094129#comment-15094129 ] Anilsg commented on ATLAS-311: -- We can add the refresh Icon on right top of the Tag's container. As well as we will be include the time base cache invalidate. > UI: Local storage for traits - caching [not cleared on refresh] To be cleared > on time lapse for 1hr. > > > Key: ATLAS-311 > URL: https://issues.apache.org/jira/browse/ATLAS-311 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-311.patch > > > Local storage for traits - caching [not cleared on refresh] To be cleared on > time lapse for 1hr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-311) UI: Local storage for traits - caching [not cleared on refresh] To be cleared on time lapse for 1hr.
[ https://issues.apache.org/jira/browse/ATLAS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-311: - Attachment: ATLAS-311.patch > UI: Local storage for traits - caching [not cleared on refresh] To be cleared > on time lapse for 1hr. > > > Key: ATLAS-311 > URL: https://issues.apache.org/jira/browse/ATLAS-311 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-311.patch > > > Local storage for traits - caching [not cleared on refresh] To be cleared on > time lapse for 1hr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-388) UI : On creating Tag, the page to be reset for creating new Tag
[ https://issues.apache.org/jira/browse/ATLAS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-388: - Attachment: ATLAS-388.patch > UI : On creating Tag, the page to be reset for creating new Tag > --- > > Key: ATLAS-388 > URL: https://issues.apache.org/jira/browse/ATLAS-388 > Project: Atlas > Issue Type: Improvement >Reporter: Anilsg >Assignee: Anilsg > Attachments: ATLAS-388.patch > > > On create tag's (Traits) the form fields to be cleared for creating new Tag, > Currently it has to refreshed or navigated from other tab to create new one -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-408) UI : Add a close link (x) on the top right when Tag is added
[ https://issues.apache.org/jira/browse/ATLAS-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-408: - Description: Modal pop-up, which is opened on Search Add Tag & From details page Add Tag, Need to have the 'X' on top right corner for user to close the modal pop up > UI : Add a close link (x) on the top right when Tag is added > > > Key: ATLAS-408 > URL: https://issues.apache.org/jira/browse/ATLAS-408 > Project: Atlas > Issue Type: Task >Reporter: Anilsg >Assignee: Anilsg > > Modal pop-up, which is opened on Search Add Tag & From details page Add Tag, > Need to have the 'X' on top right corner for user to close the modal pop up -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-408) UI : Add a close link (x) on the top right when Tag is added
[ https://issues.apache.org/jira/browse/ATLAS-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076090#comment-15076090 ] Anilsg edited comment on ATLAS-408 at 1/2/16 2:32 AM: -- Implemented as expected, Patch needs to be sent once requested on updating with latest mater was (Author: anilg): Implemented as expected, Performance is improved due to this, Patch needs to be sent once requested on updating with latest mater > UI : Add a close link (x) on the top right when Tag is added > > > Key: ATLAS-408 > URL: https://issues.apache.org/jira/browse/ATLAS-408 > Project: Atlas > Issue Type: Task >Reporter: Anilsg >Assignee: Anilsg > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-221) UI: Ability to remove added attribute from Tag definition screen
[ https://issues.apache.org/jira/browse/ATLAS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-221. -- Resolution: Fixed This was part of ATLAS-211 UI Face lift, Its merged in Master > UI: Ability to remove added attribute from Tag definition screen > > > Key: ATLAS-221 > URL: https://issues.apache.org/jira/browse/ATLAS-221 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > > Currently on the Tag screen when creating a new Trait definition it is not > possible to remove an added attribute and the UI does not allow you to "save" > until you have filled out a value. The UI should allow a user to remove > attributes prior to saving - an x or similar should be made available to > allow removal of an attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-286) UI: The result set should be consistent
[ https://issues.apache.org/jira/browse/ATLAS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-286: Assignee: Anilsg (was: Rohit) > UI: The result set should be consistent > --- > > Key: ATLAS-286 > URL: https://issues.apache.org/jira/browse/ATLAS-286 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > Attachments: Dimension_response.png, Table_response.png > > > The result set should be consistent, regardless of what you search for. > * Today, if I get a heterogeneous search result set I get a different screen > than if I search for i.e. Table > * In the heterogeneous search result I see GUIDs instead of names of the > entity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-407) Make lineage graph Zoom on Zoom-out on click of button on [+ - ]
[ https://issues.apache.org/jira/browse/ATLAS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076091#comment-15076091 ] Anilsg edited comment on ATLAS-407 at 12/31/15 7:01 PM: Implemented as expected, Patch needs to be sent once requested on updating with latest mater was (Author: anilg): Implemented as expected, Performance is improved due to this, Patch needs to be sent once requested on updating with latest mater > Make lineage graph Zoom on Zoom-out on click of button on [+ - ] > > > Key: ATLAS-407 > URL: https://issues.apache.org/jira/browse/ATLAS-407 > Project: Atlas > Issue Type: Task >Reporter: Anilsg >Assignee: Anilsg > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-407) Make lineage graph Zoom on Zoom-out on click of button on [+ - ]
[ https://issues.apache.org/jira/browse/ATLAS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076091#comment-15076091 ] Anilsg commented on ATLAS-407: -- Implemented as expected, Performance is improved due to this, Patch needs to be sent once requested on updating with latest mater > Make lineage graph Zoom on Zoom-out on click of button on [+ - ] > > > Key: ATLAS-407 > URL: https://issues.apache.org/jira/browse/ATLAS-407 > Project: Atlas > Issue Type: Task >Reporter: Anilsg >Assignee: Anilsg > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-408) UI : Add a close link (x) on the top right when Tag is added
[ https://issues.apache.org/jira/browse/ATLAS-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076090#comment-15076090 ] Anilsg commented on ATLAS-408: -- Implemented as expected, Performance is improved due to this, Patch needs to be sent once requested on updating with latest mater > UI : Add a close link (x) on the top right when Tag is added > > > Key: ATLAS-408 > URL: https://issues.apache.org/jira/browse/ATLAS-408 > Project: Atlas > Issue Type: Task >Reporter: Anilsg >Assignee: Anilsg > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-365) Lineage graph was throwing error "Uncaught TypeError: Cannot read property '0' of null"
[ https://issues.apache.org/jira/browse/ATLAS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-365. -- Resolution: Cannot Reproduce > Lineage graph was throwing error "Uncaught TypeError: Cannot read property > '0' of null" > --- > > Key: ATLAS-365 > URL: https://issues.apache.org/jira/browse/ATLAS-365 > Project: Atlas > Issue Type: Bug >Reporter: Anilsg >Assignee: Anilsg >Priority: Minor > > Lineage graph was throwing error "Uncaught TypeError: Cannot read property > '0' of null" > This was review comments of ATLAS-279, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-266) Performance - UI : Precompile template for HTML files
[ https://issues.apache.org/jira/browse/ATLAS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076083#comment-15076083 ] Anilsg commented on ATLAS-266: -- Implemented as expected, Performance is improved due to this, Patch needs to be sent once requested on updating with latest mater > Performance - UI : Precompile template for HTML files > - > > Key: ATLAS-266 > URL: https://issues.apache.org/jira/browse/ATLAS-266 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Anilsg > Fix For: 0.6-incubating > > > HTML file's call can be reduced by using precompiled template loading, > as well as browser caching is added advantage -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-288) UI: Link to column from Table details tab
[ https://issues.apache.org/jira/browse/ATLAS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076089#comment-15076089 ] Anilsg commented on ATLAS-288: -- Merged > UI: Link to column from Table details tab > - > > Key: ATLAS-288 > URL: https://issues.apache.org/jira/browse/ATLAS-288 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > Attachments: details_view.png > > > On the Table Detail -> Schema tab, we should link to the details page for > each column as an href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-288) UI: Link to column from Table details tab
[ https://issues.apache.org/jira/browse/ATLAS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-288. -- Resolution: Fixed > UI: Link to column from Table details tab > - > > Key: ATLAS-288 > URL: https://issues.apache.org/jira/browse/ATLAS-288 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > Attachments: details_view.png > > > On the Table Detail -> Schema tab, we should link to the details page for > each column as an href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-270) Performance - UI : Minify css files and combining view level
[ https://issues.apache.org/jira/browse/ATLAS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076087#comment-15076087 ] Anilsg commented on ATLAS-270: -- Implemented as expected, Performance is improved due to this, Patch needs to be sent once requested on updating with latest mater > Performance - UI : Minify css files and combining view level > - > > Key: ATLAS-270 > URL: https://issues.apache.org/jira/browse/ATLAS-270 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Anilsg > Fix For: 0.6-incubating > > > Performance : Minify css files and combining view level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-412) UI : Lineage arrow head to are leading to miss understanding for end user
[ https://issues.apache.org/jira/browse/ATLAS-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-412: - Summary: UI : Lineage arrow head to are leading to miss understanding for end user (was: UI : Lineage arrow head to are leading to miss understanding ) > UI : Lineage arrow head to are leading to miss understanding for end user > - > > Key: ATLAS-412 > URL: https://issues.apache.org/jira/browse/ATLAS-412 > Project: Atlas > Issue Type: Task >Reporter: Anilsg >Assignee: Anilsg > > Lineage arrows leading user to miss understand the flow of connectivity, > This need to worked with centralizing the arrow head on the path/node > connecting length. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-412) UI : Lineage arrow head to are leading to miss understanding
Anilsg created ATLAS-412: Summary: UI : Lineage arrow head to are leading to miss understanding Key: ATLAS-412 URL: https://issues.apache.org/jira/browse/ATLAS-412 Project: Atlas Issue Type: Task Reporter: Anilsg Assignee: Anilsg Lineage arrows leading user to miss understand the flow of connectivity, This need to worked with centralizing the arrow head on the path/node connecting length. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-407) Make lineage graph Zoom on Zoom-out on click of button on [+ - ]
Anilsg created ATLAS-407: Summary: Make lineage graph Zoom on Zoom-out on click of button on [+ - ] Key: ATLAS-407 URL: https://issues.apache.org/jira/browse/ATLAS-407 Project: Atlas Issue Type: Task Reporter: Anilsg Assignee: Anilsg -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-408) UI : Add a close link (x) on the top right when Tag is added
Anilsg created ATLAS-408: Summary: UI : Add a close link (x) on the top right when Tag is added Key: ATLAS-408 URL: https://issues.apache.org/jira/browse/ATLAS-408 Project: Atlas Issue Type: Task Reporter: Anilsg Assignee: Anilsg -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-317) UI: current active table name in lineage should be highlighted.
[ https://issues.apache.org/jira/browse/ATLAS-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065868#comment-15065868 ] Anilsg commented on ATLAS-317: -- Merged as part of ATLAS-405 patch > UI: current active table name in lineage should be highlighted. > --- > > Key: ATLAS-317 > URL: https://issues.apache.org/jira/browse/ATLAS-317 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > > current active table name in lineage should be highlighted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-405) UI: Lineage is broken seemingly if there are more than one input Processes creating a Dataset
[ https://issues.apache.org/jira/browse/ATLAS-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065610#comment-15065610 ] Anilsg commented on ATLAS-405: -- Do find "spikedMockData.png" the attached screenshot. > UI: Lineage is broken seemingly if there are more than one input Processes > creating a Dataset > - > > Key: ATLAS-405 > URL: https://issues.apache.org/jira/browse/ATLAS-405 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar >Priority: Blocker > Labels: patch-available > Attachments: ATLAS-405.patch, failing_lineage.png, > failing_lineage_api_responses.txt, failing_lineage_entity_responses.txt, > spikedMockData.png, working_lineage.png, working_lineage_api_responses.txt > > > I have a slightly complex lineage which is like this: > [DataSet 1] -> (3 processes) -> [DataSet 2] -> (1 process) -> [DataSet 3] > When I click on DataSet1, the lineage graph is showing correctly. > When I click on DataSet2, the lineage graph is broken. What is happening is > that there are 2 dangling processes on the input side of DataSet 2 which are > not linked to the DataSet 1. Only one of the processes seems linked. It > appears that maybe the graph walking is not taking into effect multiple > inputs to a vertex like DataSet 2. > The API response is right. I will upload images of working and failing > lineages with the corresponding responses in follow-up comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-388) UI : On creating Tag, the page to be reset for creating new Tag
Anilsg created ATLAS-388: Summary: UI : On creating Tag, the page to be reset for creating new Tag Key: ATLAS-388 URL: https://issues.apache.org/jira/browse/ATLAS-388 Project: Atlas Issue Type: Improvement Reporter: Anilsg Assignee: Anilsg On create tag's (Traits) the form fields to be cleared for creating new Tag, Currently it has to refreshed or navigated from other tab to create new one -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet
[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-385: Assignee: Anilsg > Support for Lineage for entities with SuperType as DataSet > --- > > Key: ATLAS-385 > URL: https://issues.apache.org/jira/browse/ATLAS-385 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Rishabh Bhardwaj >Assignee: Anilsg > Attachments: feed_enhancements.txt, lineage.png, > sample_graph_api_output.txt > > > Currently from the trunk code,the lineage only comes to type "Table" while > previously It used to come when `superType` is "DataSet" for the entities. > Due to this change now lineage only comes for the entities of type "Table" > and not for custom entities with superType 'DataSet'. > Can we get this support for DataSet back ? > Or is there any workaround for the same ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-287) UI: GUID on table details page
[ https://issues.apache.org/jira/browse/ATLAS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15054428#comment-15054428 ] Anilsg commented on ATLAS-287: -- To go with, This has been implemented with api call for each row to get the name. Tested on http://52.27.169.250:3217/#!/search?query=PII Currently this is the performance concern, What we have doing to show the Name Note : Name to be sent from back end in response, > UI: GUID on table details page > -- > > Key: ATLAS-287 > URL: https://issues.apache.org/jira/browse/ATLAS-287 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > Attachments: Screen Shot 2015-11-06 at 9.49.57 pm.png > > > On the column details page, a GUID is displayed for the DB instead of the > name of the DB. We should display the fully qualified name of the database as > the href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-268) Performance - UI : Search page, TRAIT service call to be called once
[ https://issues.apache.org/jira/browse/ATLAS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15049140#comment-15049140 ] Anilsg commented on ATLAS-268: -- [~yhemanth] As ATLAS-279 is merged, can we move this to Resolve status. > Performance - UI : Search page, TRAIT service call to be called once > - > > Key: ATLAS-268 > URL: https://issues.apache.org/jira/browse/ATLAS-268 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Anilsg > Fix For: 0.6-incubating > > > Performance : Search page, > TRAIT service call not to be called multiple time. > On each search with different query the TRAIT call is getting called, which > should not be called multiple time's -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-239) UI: Tag screen should make it possible to specify parent tag
[
https://issues.apache.org/jira/browse/ATLAS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15049148#comment-15049148
]
Anilsg commented on ATLAS-239:
--
[~yhemanth]
As ATLAS-279 is merged, can we move this to Resolve status.
> UI: Tag screen should make it possible to specify parent tag
>
>
> Key: ATLAS-239
> URL: https://issues.apache.org/jira/browse/ATLAS-239
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Anilsg
> Fix For: 0.6-incubating
>
>
> From the tag screen there should be a drop down below the "Tag Name" that
> lists all of the available Tags. The default should be blank. However, a user
> should be able to select another tag and if the user selects a named parent
> tag then when constructing the Trait, the selected Tag should be used as the
> super class in the definition as follows (where PII is the parent tag name):
> {code}
> ...],
> "traitTypes":[
> {
> "superTypes":[
> “PII"
> ],
>
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType",
> "typeName": ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity
[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045130#comment-15045130 ] Anilsg edited comment on ATLAS-345 at 12/7/15 4:03 PM: --- [~yhemanth] Patch updated with latest code of ATLAS-279 "ATLAS-345_V2.patch" Do apply this on Applying ATLAS-279 was (Author: anilg): Patch updated with latest code of ATLAS-279 "ATLAS-345_V2.patch" Do apply this on Applying ATLAS-279 > UI: Should allow tag addition on any search result that returns a > reference-able entity > --- > > Key: ATLAS-345 > URL: https://issues.apache.org/jira/browse/ATLAS-345 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-345_V1.patch, ATLAS-345_V2.patch, > ATLAS-345_v0.patch, hive_storagedesc_results.png, > hive_storagedesc_results_json.txt > > > We have a use case to associate tags to entities such as columns in hive > tables and thereby drive integration with other components that can provide > tag based policy enforcement, such as Apache Ranger. > In order to enable a user to associate tags to columns, the UI should allow > an "add tag" action on the search results page against entities that are > provided in the result list. > For e.g. if we search for hive_column where name=, we > should allow add tags against each column that comes up in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity
[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045130#comment-15045130 ] Anilsg commented on ATLAS-345: -- Patch updated with latest code of ATLAS-279 "ATLAS-345_V2.patch" Do apply this on Applying ATLAS-279 > UI: Should allow tag addition on any search result that returns a > reference-able entity > --- > > Key: ATLAS-345 > URL: https://issues.apache.org/jira/browse/ATLAS-345 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-345_V1.patch, ATLAS-345_V2.patch, > ATLAS-345_v0.patch, hive_storagedesc_results.png, > hive_storagedesc_results_json.txt > > > We have a use case to associate tags to entities such as columns in hive > tables and thereby drive integration with other components that can provide > tag based policy enforcement, such as Apache Ranger. > In order to enable a user to associate tags to columns, the UI should allow > an "add tag" action on the search results page against entities that are > provided in the result list. > For e.g. if we search for hive_column where name=, we > should allow add tags against each column that comes up in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilsg updated ATLAS-279:
-
Attachment: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v10.patch
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239-ATLAS-345_v8.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v10.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v6.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v7.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v9.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch,
> can_select_empty_line_in_parents.png, hive_table_select_bug.png,
> hive_table_select_bug.txt, tag_addition_missing_attr_name_bug.png,
> tag_addition_missing_attr_name_bug.txt,
> tag_association_missing_child_attrs.png
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity
[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044266#comment-15044266 ] Anilsg commented on ATLAS-345: -- Patch updated with latest code of ATLAS-279 "ATLAS-345_V1.patch" Do apply this on Applying ATLAS-279 > UI: Should allow tag addition on any search result that returns a > reference-able entity > --- > > Key: ATLAS-345 > URL: https://issues.apache.org/jira/browse/ATLAS-345 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-345_V1.patch, ATLAS-345_v0.patch, > hive_storagedesc_results.png, hive_storagedesc_results_json.txt > > > We have a use case to associate tags to entities such as columns in hive > tables and thereby drive integration with other components that can provide > tag based policy enforcement, such as Apache Ranger. > In order to enable a user to associate tags to columns, the UI should allow > an "add tag" action on the search results page against entities that are > provided in the result list. > For e.g. if we search for hive_column where name=, we > should allow add tags against each column that comes up in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity
[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-345: - Attachment: ATLAS-345_V1.patch > UI: Should allow tag addition on any search result that returns a > reference-able entity > --- > > Key: ATLAS-345 > URL: https://issues.apache.org/jira/browse/ATLAS-345 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-345_V1.patch, ATLAS-345_v0.patch, > hive_storagedesc_results.png, hive_storagedesc_results_json.txt > > > We have a use case to associate tags to entities such as columns in hive > tables and thereby drive integration with other components that can provide > tag based policy enforcement, such as Apache Ranger. > In order to enable a user to associate tags to columns, the UI should allow > an "add tag" action on the search results page against entities that are > provided in the result list. > For e.g. if we search for hive_column where name=, we > should allow add tags against each column that comes up in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044049#comment-15044049
]
Anilsg commented on ATLAS-279:
--
[~yhemanth] [~rohitl]
This is updated with all the issues listed,
Tested on: http://52.27.169.250:3208/#!/search
Do find the new patch file
"ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v10.patch"
Note : Issue like No. 1 probably will be occurring, as the Json response is not
consistent across all the search quires.
For Issue No. 2,3 we have tested with the quick start data available
with us, As we know we don't have hive module set up ( Taking help from Hemanth
to set up Hive module). So we have not able to test with the hive search test
quires.
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239-ATLAS-345_v8.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v10.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v6.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v7.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v9.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch,
> can_select_empty_line_in_parents.png, hive_table_select_bug.png,
> hive_table_select_bug.txt, tag_addition_missing_attr_name_bug.png,
> tag_addition_missing_attr_name_bug.txt,
> tag_association_missing_child_attrs.png
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
>
[jira] [Commented] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity
[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042655#comment-15042655 ] Anilsg commented on ATLAS-345: -- Implemented as expected. Tested on http://52.27.169.250:3256/#!/search?query=DB, This is created on Top of ATLAS-279 patch, This need's to be merged on merge of ATLAS-279 > UI: Should allow tag addition on any search result that returns a > reference-able entity > --- > > Key: ATLAS-345 > URL: https://issues.apache.org/jira/browse/ATLAS-345 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Attachments: hive_storagedesc_results.png, > hive_storagedesc_results_json.txt > > > We have a use case to associate tags to entities such as columns in hive > tables and thereby drive integration with other components that can provide > tag based policy enforcement, such as Apache Ranger. > In order to enable a user to associate tags to columns, the UI should allow > an "add tag" action on the search results page against entities that are > provided in the result list. > For e.g. if we search for hive_column where name=, we > should allow add tags against each column that comes up in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-365) Lineage graph was throwing error "Uncaught TypeError: Cannot read property '0' of null"
[ https://issues.apache.org/jira/browse/ATLAS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042677#comment-15042677 ] Anilsg commented on ATLAS-365: -- Tested on http://52.27.169.250:3256/#!/search?query=DB http://52.27.169.250:3208/#!/search?query=DB not able to reproduce, Keep this as tracker. > Lineage graph was throwing error "Uncaught TypeError: Cannot read property > '0' of null" > --- > > Key: ATLAS-365 > URL: https://issues.apache.org/jira/browse/ATLAS-365 > Project: Atlas > Issue Type: Bug >Reporter: Anilsg >Assignee: Anilsg >Priority: Minor > > Lineage graph was throwing error "Uncaught TypeError: Cannot read property > '0' of null" > This was review comments of ATLAS-279, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-365) Lineage graph was throwing error "Uncaught TypeError: Cannot read property '0' of null"
Anilsg created ATLAS-365: Summary: Lineage graph was throwing error "Uncaught TypeError: Cannot read property '0' of null" Key: ATLAS-365 URL: https://issues.apache.org/jira/browse/ATLAS-365 Project: Atlas Issue Type: Bug Reporter: Anilsg Assignee: Anilsg Priority: Minor Lineage graph was throwing error "Uncaught TypeError: Cannot read property '0' of null" This was review comments of ATLAS-279, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity
[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042679#comment-15042679 ] Anilsg commented on ATLAS-345: -- Patched attached "ATLAS-345_v0.patch" Do apply this on Applying ATLAS-279 > UI: Should allow tag addition on any search result that returns a > reference-able entity > --- > > Key: ATLAS-345 > URL: https://issues.apache.org/jira/browse/ATLAS-345 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-345_v0.patch, hive_storagedesc_results.png, > hive_storagedesc_results_json.txt > > > We have a use case to associate tags to entities such as columns in hive > tables and thereby drive integration with other components that can provide > tag based policy enforcement, such as Apache Ranger. > In order to enable a user to associate tags to columns, the UI should allow > an "add tag" action on the search results page against entities that are > provided in the result list. > For e.g. if we search for hive_column where name=, we > should allow add tags against each column that comes up in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity
[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036286#comment-15036286 ] Anilsg commented on ATLAS-345: -- [~yhemanth] ATALS-345 - “hive_storagedesc” - Is not showing any column apart from Tag & Tool’s, due to none of response object properties are mapping to any of the list defined (i.e. any response property matches to these group ['name', 'guid', 'typeName', 'owner', 'description', 'createTime', '$traits$', '$id$', 'comment', 'dataType’] and "_col_..." will be shown on the Grid/ Table ), This is a temporary solution, Until we get the response, As we discussed on 16th Nov meeting, Where the api will be sending response with helper properties/ Json, based on which the UI will be showing the columns on the Table/Grid, Which is will be consistent for UI to write the logic which will work for all the response types. Currently to make this work do share the Properties of response Object, which to be showed on the Ui for "hive_storagedesc" (E.g. qualifiedName ) > UI: Should allow tag addition on any search result that returns a > reference-able entity > --- > > Key: ATLAS-345 > URL: https://issues.apache.org/jira/browse/ATLAS-345 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Anilsg > Attachments: hive_storagedesc_results.png, > hive_storagedesc_results_json.txt > > > We have a use case to associate tags to entities such as columns in hive > tables and thereby drive integration with other components that can provide > tag based policy enforcement, such as Apache Ranger. > In order to enable a user to associate tags to columns, the UI should allow > an "add tag" action on the search results page against entities that are > provided in the result list. > For e.g. if we search for hive_column where name=, we > should allow add tags against each column that comes up in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity
[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-345. -- Resolution: Fixed > UI: Should allow tag addition on any search result that returns a > reference-able entity > --- > > Key: ATLAS-345 > URL: https://issues.apache.org/jira/browse/ATLAS-345 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Anilsg > > We have a use case to associate tags to entities such as columns in hive > tables and thereby drive integration with other components that can provide > tag based policy enforcement, such as Apache Ranger. > In order to enable a user to associate tags to columns, the UI should allow > an "add tag" action on the search results page against entities that are > provided in the result list. > For e.g. if we search for hive_column where name=, we > should allow add tags against each column that comes up in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity
[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-345: Assignee: Anilsg Code updated as per expected, If the Json response contain's $Id$ the Tag's and add Tag's column's are shown . This is sent as a part of ATLAS-279 > UI: Should allow tag addition on any search result that returns a > reference-able entity > --- > > Key: ATLAS-345 > URL: https://issues.apache.org/jira/browse/ATLAS-345 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Anilsg > > We have a use case to associate tags to entities such as columns in hive > tables and thereby drive integration with other components that can provide > tag based policy enforcement, such as Apache Ranger. > In order to enable a user to associate tags to columns, the UI should allow > an "add tag" action on the search results page against entities that are > provided in the result list. > For e.g. if we search for hive_column where name=, we > should allow add tags against each column that comes up in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilsg updated ATLAS-279:
-
Attachment:
ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239-ATLAS-345_v8.patch
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239-ATLAS-345_v8.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v6.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v7.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-151) UI: Make lineage graph Fit the window size
[ https://issues.apache.org/jira/browse/ATLAS-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-151. -- Resolution: Fixed This is send as part of ATLAS-211 > UI: Make lineage graph Fit the window size > --- > > Key: ATLAS-151 > URL: https://issues.apache.org/jira/browse/ATLAS-151 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.6-incubating >Reporter: Anilsg > Fix For: 0.6-incubating > > > UI: Make lineage graph Fit the window size > All the node's to be visible on initial load -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-260) if the trait name is long, UI does not handle it properly
[ https://issues.apache.org/jira/browse/ATLAS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-260. -- Resolution: Fixed This is merged to apache master as part of ATLAS-211 - Ui face lift > if the trait name is long, UI does not handle it properly > -- > > Key: ATLAS-260 > URL: https://issues.apache.org/jira/browse/ATLAS-260 > Project: Atlas > Issue Type: Bug >Reporter: Darshan Kumar >Assignee: Anilsg > Attachments: Apache-Atlas-long-trait-name.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-221) UI: Ability to remove added attribute from Tag definition screen
[ https://issues.apache.org/jira/browse/ATLAS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-221: Assignee: Anilsg (was: Rohit) > UI: Ability to remove added attribute from Tag definition screen > > > Key: ATLAS-221 > URL: https://issues.apache.org/jira/browse/ATLAS-221 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > > Currently on the Tag screen when creating a new Trait definition it is not > possible to remove an added attribute and the UI does not allow you to "save" > until you have filled out a value. The UI should allow a user to remove > attributes prior to saving - an x or similar should be made available to > allow removal of an attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-132) Search Controller Optimization
[ https://issues.apache.org/jira/browse/ATLAS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-132: Assignee: Anilsg (was: Rohit) > Search Controller Optimization > -- > > Key: ATLAS-132 > URL: https://issues.apache.org/jira/browse/ATLAS-132 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.5.1-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > Attachments: ATLAS-132-v0.patch > > > Search Controller currently makes multiple calls. This can and should be > optimized as a single API call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-244) UI: Add Tag Tab
[ https://issues.apache.org/jira/browse/ATLAS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-244: Assignee: Darshan Kumar (was: Rohit) > UI: Add Tag Tab > --- > > Key: ATLAS-244 > URL: https://issues.apache.org/jira/browse/ATLAS-244 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Darshan Kumar > Fix For: 0.6-incubating > > > The detailed entity screen needs to add a Tag tab. See: > https://monosnap.com/file/en3YL2ARN111d9UDlCozZpBnUhkPwv for additional > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022789#comment-15022789
]
Anilsg commented on ATLAS-279:
--
Updated the code for Hive table,
Tested on http://52.27.169.250:3179/#!/
patch file "ATLAS-279ATLAS-268ATLAS-244ATLAS-264ATLAS-239_v4.patch"
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilsg reopened ATLAS-279:
--
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilsg updated ATLAS-279:
-
Attachment: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilsg resolved ATLAS-279.
--
Resolution: Fixed
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-318) Config file conatining UI: API endpoint + all api calls to be centralized -- config JS file for stand alone UI.
[ https://issues.apache.org/jira/browse/ATLAS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1502#comment-1502 ] Anilsg commented on ATLAS-318: -- Over all domain/ server endpoint to configurable, currently takes the domain of which the UI is hosted. Even it needs to support COR (Cross origin resource sharing), So that Ui can work in cross domain's mode. All the api call url to be configureable from centralize-ed location. So that if any change / updates to api can done easily, which is even a good practices > Config file conatining UI: API endpoint + all api calls to be centralized -- > config JS file for stand alone UI. > --- > > Key: ATLAS-318 > URL: https://issues.apache.org/jira/browse/ATLAS-318 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Priority: Minor > Labels: Atlas-UI > > Config file conatining API endpoint + all api calls to be centralized -- > config JS file for stand alone UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-318) UI. Config file conatining UI: API endpoint + all api calls to be centralized -- config JS file for stand alone
[ https://issues.apache.org/jira/browse/ATLAS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-318: - Summary: UI. Config file conatining UI: API endpoint + all api calls to be centralized -- config JS file for stand alone (was: Config file conatining UI: API endpoint + all api calls to be centralized -- config JS file for stand alone UI.) > UI. Config file conatining UI: API endpoint + all api calls to be centralized > -- config JS file for stand alone > --- > > Key: ATLAS-318 > URL: https://issues.apache.org/jira/browse/ATLAS-318 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > > Config file conatining API endpoint + all api calls to be centralized -- > config JS file for stand alone UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-317) UI: current active table name in lineage should be highlighted.
[ https://issues.apache.org/jira/browse/ATLAS-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021112#comment-15021112 ] Anilsg commented on ATLAS-317: -- In the details page the Lineage should highlight the current Image, So that user can easy identify the what is the input and what are the output's for current entity > UI: current active table name in lineage should be highlighted. > --- > > Key: ATLAS-317 > URL: https://issues.apache.org/jira/browse/ATLAS-317 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Priority: Minor > Labels: Atlas-UI > > current active table name in lineage should be highlighted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-319) UI: if config not able to get response show a error message - config.js
[ https://issues.apache.org/jira/browse/ATLAS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021115#comment-15021115 ] Anilsg commented on ATLAS-319: -- This is part of ATLAS-318, Where if the domain / server endpoint is not configurable, on deploying UI, User should get the appropriate error message > UI: if config not able to get response show a error message - config.js > --- > > Key: ATLAS-319 > URL: https://issues.apache.org/jira/browse/ATLAS-319 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Priority: Minor > Labels: Atlas-UI > > if config not able to get response show a error message - config.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-320) UI: Atlas backend support for CORS
[ https://issues.apache.org/jira/browse/ATLAS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-320: Assignee: Anilsg > UI: Atlas backend support for CORS > -- > > Key: ATLAS-320 > URL: https://issues.apache.org/jira/browse/ATLAS-320 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > > Atlas backend support for CORS -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-319) UI: if config not able to get response show a error message - config.js
[ https://issues.apache.org/jira/browse/ATLAS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-319: Assignee: Anilsg > UI: if config not able to get response show a error message - config.js > --- > > Key: ATLAS-319 > URL: https://issues.apache.org/jira/browse/ATLAS-319 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Anilsg >Priority: Minor > Labels: Atlas-UI > > if config not able to get response show a error message - config.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-258) Lineage api performance issue
[
https://issues.apache.org/jira/browse/ATLAS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15018399#comment-15018399
]
Anilsg commented on ATLAS-258:
--
Service api call’s
api/atlas/entity/{guid} — 1.5 s — 2 calls needs to reduce one
one for detail’s page ( detailsController ) — 800 ms
another from tag’s display ( instanceTagsController ) — 1.2 s
/api/atlas/lineage/hive/table/{name}/{type}/graph - 2 calls
One for Input — 2 s
Another for Output — 2 s
/api/atlas/entity/{guid} — multiple call’s for all missing vertices
in /grap call response — each call 800 ms
Expected : A service "api" which returns with all the edges and vertices
details, in response.
> Lineage api performance issue
> --
>
> Key: ATLAS-258
> URL: https://issues.apache.org/jira/browse/ATLAS-258
> Project: Atlas
> Issue Type: Bug
>Reporter: Darshan Kumar
>Assignee: Anilsg
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-258) Lineage api performance issue
[
https://issues.apache.org/jira/browse/ATLAS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15018399#comment-15018399
]
Anilsg edited comment on ATLAS-258 at 11/20/15 5:49 PM:
[~bergenholtz]
Service api call’s
/api/atlas/lineage/hive/table/{name}/{type}/graph - 2 calls
One for Input — 2 s
Another for Output — 2 s
/api/atlas/entity/{guid} — multiple call’s for all missing vertices
in /grap call response — each call 800 ms
Expected : A service "api" which returns with all the edges and vertices
details, in response.
was (Author: anilg):
[~bergenholtz]
Service api call’s
api/atlas/entity/{guid} — 1.5 s — 2 calls needs to reduce one
one for detail’s page ( detailsController ) — 800 ms
another from tag’s display ( instanceTagsController ) — 1.2 s
/api/atlas/lineage/hive/table/{name}/{type}/graph - 2 calls
One for Input — 2 s
Another for Output — 2 s
/api/atlas/entity/{guid} — multiple call’s for all missing vertices
in /grap call response — each call 800 ms
Expected : A service "api" which returns with all the edges and vertices
details, in response.
> Lineage api performance issue
> --
>
> Key: ATLAS-258
> URL: https://issues.apache.org/jira/browse/ATLAS-258
> Project: Atlas
> Issue Type: Bug
>Reporter: Darshan Kumar
>Assignee: Anilsg
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998345#comment-14998345
]
Anilsg commented on ATLAS-279:
--
Patch for ATLAS-279,268,244,264 are in one patch available in ATLAS-279 [
http://52.27.169.250:3208/#!/search] Please review
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilsg updated ATLAS-279:
-
Labels: patch-available (was: )
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-268) Performance - UI : Search page, TRAIT service call to be called once
[ https://issues.apache.org/jira/browse/ATLAS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-268. -- Resolution: Fixed Implemented as expected, On search page the trait api will be called on page load first time on reclusive search, the trait api will not be called again. This is implemented as part of ATLAS-279 [HDPDGI-208] - UI not displaying results for certain successful "select" search queries. Tested on http://52.27.169.250:3208/#!/search Patch is sent as part of ATLAS-279 > Performance - UI : Search page, TRAIT service call to be called once > - > > Key: ATLAS-268 > URL: https://issues.apache.org/jira/browse/ATLAS-268 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Anilsg > Fix For: 0.6-incubating > > > Performance : Search page, > TRAIT service call not to be called multiple time. > On each search with different query the TRAIT call is getting called, which > should not be called multiple time's -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-264) UI: As part of trait/tag creation, POST response(201 created) is enough to say the request is successful. Extra http GET call can be removed.
[ https://issues.apache.org/jira/browse/ATLAS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14997156#comment-14997156 ] Anilsg commented on ATLAS-264: -- This is implemented as part of ATLAS-279 [HDPDGI-208] - UI not displaying results for certain successful "select" search queries. Tested on http://52.27.169.250:3208/#!/search Patch is sent as part of ATLAS-279 > UI: As part of trait/tag creation, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed. > - > > Key: ATLAS-264 > URL: https://issues.apache.org/jira/browse/ATLAS-264 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Anilsg > Labels: PatchAvailable > Attachments: ATLAS-264_v0.patch, > Apache-Atlas-Avoid-Extra-Get-For-Trait-Creation.png > > > As part of trait/tag creation in UI, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed/avoided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-288) UI: Link to column from Table details tab
[ https://issues.apache.org/jira/browse/ATLAS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-288: Assignee: Anilsg (was: Rohit) > UI: Link to column from Table details tab > - > > Key: ATLAS-288 > URL: https://issues.apache.org/jira/browse/ATLAS-288 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > Attachments: details_view.png > > > On the Table Detail -> Schema tab, we should link to the details page for > each column as an href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-288) UI: Link to column from Table details tab
[ https://issues.apache.org/jira/browse/ATLAS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-288: - Attachment: details_view.png > UI: Link to column from Table details tab > - > > Key: ATLAS-288 > URL: https://issues.apache.org/jira/browse/ATLAS-288 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Rohit > Fix For: 0.6-incubating > > Attachments: details_view.png > > > On the Table Detail -> Schema tab, we should link to the details page for > each column as an href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-288) UI: Link to column from Table details tab
[ https://issues.apache.org/jira/browse/ATLAS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995508#comment-14995508 ] Anilsg commented on ATLAS-288: -- [~bergenholtz] This was part of ATLAS-211 patch, Do refer screenshot "details_view.png". http://52.27.169.250:3010/#!/details/dbedc9c4-67b3-40c3-92ac-8e920d278f27 > UI: Link to column from Table details tab > - > > Key: ATLAS-288 > URL: https://issues.apache.org/jira/browse/ATLAS-288 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > Attachments: details_view.png > > > On the Table Detail -> Schema tab, we should link to the details page for > each column as an href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-286) UI: The result set should be consistent
[ https://issues.apache.org/jira/browse/ATLAS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-286: - Attachment: Table_response.png Dimension_response.png > UI: The result set should be consistent > --- > > Key: ATLAS-286 > URL: https://issues.apache.org/jira/browse/ATLAS-286 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Rohit > Fix For: 0.6-incubating > > Attachments: Dimension_response.png, Table_response.png > > > The result set should be consistent, regardless of what you search for. > * Today, if I get a heterogeneous search result set I get a different screen > than if I search for i.e. Table > * In the heterogeneous search result I see GUIDs instead of names of the > entity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-287) UI: GUID on table details page
[ https://issues.apache.org/jira/browse/ATLAS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-287: Assignee: Anilsg (was: Rohit) > UI: GUID on table details page > -- > > Key: ATLAS-287 > URL: https://issues.apache.org/jira/browse/ATLAS-287 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Fix For: 0.6-incubating > > Attachments: Screen Shot 2015-11-06 at 9.49.57 pm.png > > > On the column details page, a GUID is displayed for the DB instead of the > name of the DB. We should display the fully qualified name of the database as > the href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-287) UI: GUID on table details page
[
https://issues.apache.org/jira/browse/ATLAS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993891#comment-14993891
]
Anilsg commented on ATLAS-287:
--
>From UI to display the name for the GUID, we might need to call a additional
>service call's ,
"/api/atlas/entities/{GUID}"
As the service response is not giving the Name,
Do refer the screenshot
> UI: GUID on table details page
> --
>
> Key: ATLAS-287
> URL: https://issues.apache.org/jira/browse/ATLAS-287
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
> Fix For: 0.6-incubating
>
> Attachments: Screen Shot 2015-11-06 at 9.49.57 pm.png
>
>
> On the column details page, a GUID is displayed for the DB instead of the
> name of the DB. We should display the fully qualified name of the database as
> the href.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-287) UI: GUID on table details page
[ https://issues.apache.org/jira/browse/ATLAS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-287: - Attachment: Screen Shot 2015-11-06 at 9.49.57 pm.png > UI: GUID on table details page > -- > > Key: ATLAS-287 > URL: https://issues.apache.org/jira/browse/ATLAS-287 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Rohit > Fix For: 0.6-incubating > > Attachments: Screen Shot 2015-11-06 at 9.49.57 pm.png > > > On the column details page, a GUID is displayed for the DB instead of the > name of the DB. We should display the fully qualified name of the database as > the href. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-264) UI: As part of trait/tag creation, POST response(201 created) is enough to say the request is successful. Extra http GET call can be removed.
[ https://issues.apache.org/jira/browse/ATLAS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg updated ATLAS-264: - Attachment: ATLAS-264_v0.patch > UI: As part of trait/tag creation, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed. > - > > Key: ATLAS-264 > URL: https://issues.apache.org/jira/browse/ATLAS-264 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Anilsg > Labels: patch-available > Attachments: ATLAS-264_v0.patch, > Apache-Atlas-Avoid-Extra-Get-For-Trait-Creation.png > > > As part of trait/tag creation in UI, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed/avoided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-264) UI: As part of trait/tag creation, POST response(201 created) is enough to say the request is successful. Extra http GET call can be removed.
[ https://issues.apache.org/jira/browse/ATLAS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14994327#comment-14994327 ] Anilsg commented on ATLAS-264: -- New patch attached "ATLAS-264_v0.patch" > UI: As part of trait/tag creation, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed. > - > > Key: ATLAS-264 > URL: https://issues.apache.org/jira/browse/ATLAS-264 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Anilsg > Labels: patch-available > Attachments: ATLAS-264_v0.patch, > Apache-Atlas-Avoid-Extra-Get-For-Trait-Creation.png > > > As part of trait/tag creation in UI, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed/avoided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-264) UI: As part of trait/tag creation, POST response(201 created) is enough to say the request is successful. Extra http GET call can be removed.
[ https://issues.apache.org/jira/browse/ATLAS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14994317#comment-14994317 ] Anilsg commented on ATLAS-264: -- [~suma.shivaprasad] Fixed as per expected, Tested on http://52.27.169.250:3211/#!/search > UI: As part of trait/tag creation, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed. > - > > Key: ATLAS-264 > URL: https://issues.apache.org/jira/browse/ATLAS-264 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Darshan Kumar > Labels: patch-available > Attachments: Apache-Atlas-Avoid-Extra-Get-For-Trait-Creation.png > > > As part of trait/tag creation in UI, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed/avoided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (ATLAS-264) UI: As part of trait/tag creation, POST response(201 created) is enough to say the request is successful. Extra http GET call can be removed.
[ https://issues.apache.org/jira/browse/ATLAS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reopened ATLAS-264: -- > UI: As part of trait/tag creation, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed. > - > > Key: ATLAS-264 > URL: https://issues.apache.org/jira/browse/ATLAS-264 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Anilsg > Labels: patch-available > Attachments: ATLAS-264_v0.patch, > Apache-Atlas-Avoid-Extra-Get-For-Trait-Creation.png > > > As part of trait/tag creation in UI, POST response(201 created) is enough to > say the request is successful. Extra http GET call can be removed/avoided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-262) UI: Entities displayed after attaching long tags can be handled properly
[ https://issues.apache.org/jira/browse/ATLAS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14988782#comment-14988782 ] Anilsg commented on ATLAS-262: -- Corrected and resolved in patch, available in ATLAS-211 > UI: Entities displayed after attaching long tags can be handled properly > > > Key: ATLAS-262 > URL: https://issues.apache.org/jira/browse/ATLAS-262 > Project: Atlas > Issue Type: Bug >Reporter: Ayub Khan >Assignee: Anilsg > Attachments: Apache-Atlas-Entities-with-long-tags.png > > > UI: Entities displayed after attaching long tags cab be handled properly > Attaching the snsphot for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-256) Details page display name for the entity Db and Sd column
[ https://issues.apache.org/jira/browse/ATLAS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14988790#comment-14988790 ] Anilsg commented on ATLAS-256: -- The Fix is updated in ATLAS-211 Patch. Thanks > Details page display name for the entity Db and Sd column > - > > Key: ATLAS-256 > URL: https://issues.apache.org/jira/browse/ATLAS-256 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Anilsg >Priority: Critical > Fix For: 0.6-incubating > > > Details page display name for the entity Db and Sd column > Database and Storage Descriptor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-219) UI: Add ability to detach trait from the entity
[
https://issues.apache.org/jira/browse/ATLAS-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985717#comment-14985717
]
Anilsg commented on ATLAS-219:
--
In details page add 'X' to every tag's , on click the 'X' tag's will be removed
on confirmation
Patch sent as part of ATLAS-211
Tested on http://162.212.133.190:3172/#!/search
> UI: Add ability to detach trait from the entity
> ---
>
> Key: ATLAS-219
> URL: https://issues.apache.org/jira/browse/ATLAS-219
> Project: Atlas
> Issue Type: Improvement
>Reporter: Ayub Khan
>Assignee: Anilsg
>Priority: Blocker
>
> Currently we are able to detach trait from the entity using REST API.
> Similar support can be provided via ATLAS-UI.
> {code}
> curl -X DELETE -v
> 'http://localhost:21000/api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII'
> * Trying ::1...
> * Connected to localhost (::1) port 21000 (#0)
> > DELETE /api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII
> > HTTP/1.1
> > Host: localhost:21000
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Mon, 12 Oct 2015 15:34:15 GMT
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host localhost left intact
> {"requestId":"qtp468469-162 -
> 387b46eb-4fca-4547-aef7-f53590b9c069","GUID":"9646d28d-bbea-4cc5-9d84-0d37f0ca536c","traitName":"PII"}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
