[jira] [Assigned] (ATLAS-799) UI: Searching for a tag should never be a full text search.
[ https://issues.apache.org/jira/browse/ATLAS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-799: --- Assignee: Darshan Kumar > UI: Searching for a tag should never be a full text search. > --- > > Key: ATLAS-799 > URL: https://issues.apache.org/jira/browse/ATLAS-799 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > > * Create a tag. > * Click on it from the assets page. > * This is firing a full text search with the tag, which doesn't make sense. > Expected result is that this should always result in a DSL ISA search. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-799) UI: Searching for a tag should never be a full text search.
[ https://issues.apache.org/jira/browse/ATLAS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357342#comment-15357342 ] Darshan Kumar commented on ATLAS-799: - [~yhemanth] please tell, while creating tags do we specify DSL or all the tags are for DSL. > UI: Searching for a tag should never be a full text search. > --- > > Key: ATLAS-799 > URL: https://issues.apache.org/jira/browse/ATLAS-799 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala > > * Create a tag. > * Click on it from the assets page. > * This is firing a full text search with the tag, which doesn't make sense. > Expected result is that this should always result in a DSL ISA search. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-472) UI : Pagination is failing when the search result has more numbers of pages
[ https://issues.apache.org/jira/browse/ATLAS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275151#comment-15275151 ] Darshan Kumar commented on ATLAS-472: - [~bergenholtz] and [~yhemanth] please let me know the bug details of new version, so that i can fix it. Thanks > UI : Pagination is failing when the search result has more numbers of pages > --- > > Key: ATLAS-472 > URL: https://issues.apache.org/jira/browse/ATLAS-472 > Project: Atlas > Issue Type: Task >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: Atlas-UI > Fix For: 0.7-incubating > > Attachments: ATLAS-472.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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:all-tabpanel ] Darshan Kumar updated ATLAS-270: Attachment: ATLAS-270.patch > 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: Darshan Kumar > Fix For: trunk > > Attachments: ATLAS-270.patch > > > Performance : Minify css files and combining view level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (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:all-tabpanel ] Darshan Kumar reassigned ATLAS-270: --- Assignee: Darshan Kumar (was: Anilsg) > 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: Darshan Kumar > Fix For: trunk > > Attachments: ATLAS-270.patch > > > Performance : Minify css files and combining view level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-269) Performance - UI : Combining all external Js file minified version
[ https://issues.apache.org/jira/browse/ATLAS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-269: Attachment: ATLAS-269.patch > Performance - UI : Combining all external Js file minified version > --- > > Key: ATLAS-269 > URL: https://issues.apache.org/jira/browse/ATLAS-269 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Darshan Kumar > Fix For: trunk > > Attachments: ATLAS-269.patch > > > All the 3rd party js files need to be merged in a single file, > E.g. angular js , bootstrap , jquery, d3 .. etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-269) Performance - UI : Combining all external Js file minified version
[ https://issues.apache.org/jira/browse/ATLAS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-269: --- Assignee: Darshan Kumar (was: Anilsg) > Performance - UI : Combining all external Js file minified version > --- > > Key: ATLAS-269 > URL: https://issues.apache.org/jira/browse/ATLAS-269 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Darshan Kumar > Fix For: trunk > > Attachments: ATLAS-269.patch > > > All the 3rd party js files need to be merged in a single file, > E.g. angular js , bootstrap , jquery, d3 .. etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-310) UI: Remove tools title from search result.
[ https://issues.apache.org/jira/browse/ATLAS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-310: --- Assignee: Darshan Kumar > UI: Remove tools title from search result. > -- > > Key: ATLAS-310 > URL: https://issues.apache.org/jira/browse/ATLAS-310 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > Remove tools title from search result. -- 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 ] Darshan Kumar updated ATLAS-408: Attachment: ATLAS-408.patch > 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: Darshan Kumar > Labels: Atlas-UI > Attachments: ATLAS-408.patch > > > 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] [Updated] (ATLAS-322) UI: All existing CSS to converted to LESS.
[ https://issues.apache.org/jira/browse/ATLAS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-322: Attachment: (was: ATLAS-322.patch) > UI: All existing CSS to converted to LESS. > -- > > Key: ATLAS-322 > URL: https://issues.apache.org/jira/browse/ATLAS-322 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > All existing CSS to converted to LESS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-310) UI: Remove tools title from search result.
[ https://issues.apache.org/jira/browse/ATLAS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-310: Attachment: ATLAS-310.patch > UI: Remove tools title from search result. > -- > > Key: ATLAS-310 > URL: https://issues.apache.org/jira/browse/ATLAS-310 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-310.patch > > > Remove tools title from search result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (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 ] Darshan Kumar reassigned ATLAS-408: --- Assignee: Darshan Kumar (was: Anilsg) > 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: Darshan Kumar > > 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] [Updated] (ATLAS-322) UI: All existing CSS to converted to LESS.
[ https://issues.apache.org/jira/browse/ATLAS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-322: Attachment: ATLAS-322.patch > UI: All existing CSS to converted to LESS. > -- > > Key: ATLAS-322 > URL: https://issues.apache.org/jira/browse/ATLAS-322 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-322.patch > > > All existing CSS to converted to LESS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-322) UI: All existing CSS to converted to LESS.
[ https://issues.apache.org/jira/browse/ATLAS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-322: Attachment: ATLAS-322.patch > UI: All existing CSS to converted to LESS. > -- > > Key: ATLAS-322 > URL: https://issues.apache.org/jira/browse/ATLAS-322 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-322.patch > > > All existing CSS to converted to LESS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-322) UI: All existing CSS to converted to LESS.
[ https://issues.apache.org/jira/browse/ATLAS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-322: --- Assignee: Darshan Kumar > UI: All existing CSS to converted to LESS. > -- > > Key: ATLAS-322 > URL: https://issues.apache.org/jira/browse/ATLAS-322 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > All existing CSS to converted to LESS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-472) UI : Pagination is failing when the search result has more numbers of pages
[ https://issues.apache.org/jira/browse/ATLAS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-472: Attachment: ATLAS-472.patch > UI : Pagination is failing when the search result has more numbers of pages > --- > > Key: ATLAS-472 > URL: https://issues.apache.org/jira/browse/ATLAS-472 > Project: Atlas > Issue Type: Bug >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: Atlas-UI > Fix For: 0.7-incubating > > Attachments: ATLAS-472.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-316) UI: Css show hand pointer while clicking lineage.
[ https://issues.apache.org/jira/browse/ATLAS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-316: Attachment: ATLAS-318.patch > UI: Css show hand pointer while clicking lineage. > - > > Key: ATLAS-316 > URL: https://issues.apache.org/jira/browse/ATLAS-316 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-318.patch > > > Css show hand pointer while clicking lineage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-364) UI Code standardization
[ https://issues.apache.org/jira/browse/ATLAS-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-364: Attachment: ATLAS-364-v0.patch > UI Code standardization > --- > > Key: ATLAS-364 > URL: https://issues.apache.org/jira/browse/ATLAS-364 > Project: Atlas > Issue Type: Bug >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: ATLAS-UI-BUGS > Attachments: ATLAS-364-v0.patch > > > 1. css class names must be standardize. lisp-case is the standard way to name > a css class. Lower camelCase is used for javascript variables. > 2. Files names must be standardized. Mostly its lower camel, but some are > using snake. > 3. Remove commented code > 4. Indentation must be same everywhere -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (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&focusedCommentId=15152400#comment-15152400 ] Darshan Kumar edited comment on ATLAS-266 at 2/18/16 3:03 PM: -- [~yhemanth] This is one of the performance improvement patch. Please review and let me know if there is anything. Thank you was (Author: darshankumar89): [~yhemanth] This one of the performance improvement patch. Please review and let me know if there is anything. Thank you > 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: Darshan Kumar > Labels: ATLAS-UI-BUGS > Fix For: trunk > > Attachments: ATLAS-266-V0.patch > > > 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] [Updated] (ATLAS-266) Performance - UI : Precompile template for HTML files
[ https://issues.apache.org/jira/browse/ATLAS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-266: Attachment: (was: ATLAS-266.patch) > 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: Darshan Kumar > Labels: ATLAS-UI-BUGS > Fix For: trunk > > Attachments: ATLAS-266-V0.patch > > > 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] [Updated] (ATLAS-266) Performance - UI : Precompile template for HTML files
[ https://issues.apache.org/jira/browse/ATLAS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-266: Attachment: ATLAS-266-V0.patch > 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: Darshan Kumar > Labels: ATLAS-UI-BUGS > Fix For: trunk > > Attachments: ATLAS-266-V0.patch, ATLAS-266.patch > > > 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-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&focusedCommentId=15152400#comment-15152400 ] Darshan Kumar commented on ATLAS-266: - [~yhemanth] This one of the performance improvement patch. Please review and let me know if there is anything. Thank you > 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: Darshan Kumar > Labels: ATLAS-UI-BUGS > Fix For: trunk > > Attachments: ATLAS-266.patch > > > 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] [Assigned] (ATLAS-266) Performance - UI : Precompile template for HTML files
[ https://issues.apache.org/jira/browse/ATLAS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-266: --- Assignee: Darshan Kumar (was: Anilsg) > 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: Darshan Kumar > Labels: ATLAS-UI-BUGS > Fix For: trunk > > Attachments: ATLAS-266.patch > > > 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] [Updated] (ATLAS-266) Performance - UI : Precompile template for HTML files
[ https://issues.apache.org/jira/browse/ATLAS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-266: Attachment: ATLAS-266.patch > 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 > Labels: ATLAS-UI-BUGS > Fix For: trunk > > Attachments: ATLAS-266.patch > > > 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] [Assigned] (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 ] Darshan Kumar reassigned ATLAS-502: --- Assignee: Darshan Kumar (was: Rohit) > 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: Darshan Kumar > 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] [Updated] (ATLAS-318) UI. Config file containing 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 ] Darshan Kumar updated ATLAS-318: Attachment: ATLAS-318-V2.patch > UI. Config file containing 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: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-318-V2.patch, ATLAS-318-v1.patch, ATLAS-318.patch > > > 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-318) UI. Config file containing 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:comment-tabpanel&focusedCommentId=15148287#comment-15148287 ] Darshan Kumar commented on ATLAS-318: - Thanks [~yhemanth] for the findings, we will look into it. Sorry for the inconvenience. [~sanjayp] please review the code and test, I will also test from my end. Thank you > UI. Config file containing 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: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-318-v1.patch, ATLAS-318.patch > > > 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 containing 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 ] Darshan Kumar updated ATLAS-318: Attachment: ATLAS-318-v1.patch > UI. Config file containing 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: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-318-v1.patch, ATLAS-318.patch > > > 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] [Resolved] (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 ] Darshan Kumar resolved ATLAS-434. - Resolution: Fixed > 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: Darshan Kumar > 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, Screen Shot 2016-01-20 at > 9.18.18 pm.png, Screen Shot 2016-01-20 at 9.18.23 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&focusedCommentId=15143955#comment-15143955 ] Darshan Kumar commented on ATLAS-434: - [~ckrishnakumar] Thank you for verifying and Add tag supports non-english characters. > 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: Darshan Kumar > 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, Screen Shot 2016-01-20 at > 9.18.18 pm.png, Screen Shot 2016-01-20 at 9.18.23 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] [Created] (ATLAS-472) UI : Pagination is failing when the search result has more numbers of pages
Darshan Kumar created ATLAS-472: --- Summary: UI : Pagination is failing when the search result has more numbers of pages Key: ATLAS-472 URL: https://issues.apache.org/jira/browse/ATLAS-472 Project: Atlas Issue Type: Bug Reporter: Darshan Kumar Assignee: Darshan Kumar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-316) UI: Css show hand pointer while clicking lineage.
[ https://issues.apache.org/jira/browse/ATLAS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-316: --- Assignee: Darshan Kumar > UI: Css show hand pointer while clicking lineage. > - > > Key: ATLAS-316 > URL: https://issues.apache.org/jira/browse/ATLAS-316 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > Css show hand pointer while clicking lineage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15135919#comment-15135919 ] Darshan Kumar commented on ATLAS-318: - Thank you providing the details [~sneethiraj].I have requested [~suma.shivaprasad] and [~bergenholtz] to verify the patch. Thanks. > 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: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-318.patch > > > 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] [Assigned] (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 ] Darshan Kumar reassigned ATLAS-318: --- Assignee: Darshan Kumar (was: Sanjay Patel) > 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: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-318.patch > > > 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-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:comment-tabpanel&focusedCommentId=15135822#comment-15135822 ] Darshan Kumar commented on ATLAS-318: - [~ckrishnakumar], [~yhemanth], [~ayubkhan] please help me out to understand the above comments. Thanks. > 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: Sanjay Patel >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-318.patch > > > 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 ] Darshan Kumar updated ATLAS-318: Attachment: ATLAS-318.patch > 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: Sanjay Patel >Priority: Minor > Labels: Atlas-UI > Attachments: ATLAS-318.patch > > > 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-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 ] Darshan Kumar updated ATLAS-388: Attachment: ATLAS-388-v3.patch please review the link below and if there is anything please let me know.The patch is update [ATLAS-388-v3.patch ].Thanks http://ec2-52-33-160-226.us-west-2.compute.amazonaws.com:3088/#!/tags > 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-v1.patch, ATLAS-388-v2.patch, > ATLAS-388-v3.patch, ATLAS-388.patch, ui-red-tag-name.png > > > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15120751#comment-15120751 ] Darshan Kumar commented on ATLAS-388: - Sure will take a look at it. Thanks > 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-v1.patch, ATLAS-388-v2.patch, ATLAS-388.patch, > ui-red-tag-name.png > > > 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-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 ] Darshan Kumar updated ATLAS-388: Attachment: ATLAS-388-v2.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-v1.patch, ATLAS-388-v2.patch, ATLAS-388.patch, > ui-red-tag-name.png > > > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15116608#comment-15116608 ] Darshan Kumar commented on ATLAS-388: - [~yhemanth] The patch is updated as per comments. Please review. Thanks > 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-v1.patch, ATLAS-388.patch, ui-red-tag-name.png > > > 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-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 ] Darshan Kumar updated ATLAS-388: Attachment: (was: ATLAS-388-v2.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-v1.patch, ATLAS-388.patch, ui-red-tag-name.png > > > 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-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 ] Darshan Kumar updated ATLAS-388: Attachment: ATLAS-388-v2.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-v1.patch, ATLAS-388-v2.patch, ATLAS-388.patch, > ui-red-tag-name.png > > > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15115224#comment-15115224 ] Darshan Kumar commented on ATLAS-388: - sure will do and update it. Thanks > 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-v1.patch, ATLAS-388.patch, ui-red-tag-name.png > > > 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] [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&focusedCommentId=15108787#comment-15108787 ] Darshan Kumar commented on ATLAS-434: - Shwetha G S,Chethana and Hemanth Yamijala Please look into the screenshot [Screen Shot 2016-01-20 at 9.18.18 pm] which is build from current backend. Please review and let us know the feedback. Thanks > 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: Darshan Kumar > 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, Screen Shot 2016-01-20 at > 9.18.18 pm.png, Screen Shot 2016-01-20 at 9.18.23 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] [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 ] Darshan Kumar updated ATLAS-434: Attachment: Screen Shot 2016-01-20 at 9.18.23 pm.png Screen Shot 2016-01-20 at 9.18.18 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: Darshan Kumar > 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, Screen Shot 2016-01-20 at > 9.18.18 pm.png, Screen Shot 2016-01-20 at 9.18.23 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] [Assigned] (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 ] Darshan Kumar reassigned ATLAS-434: --- Assignee: Darshan Kumar (was: Anilsg) > 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: Darshan Kumar > 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-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:comment-tabpanel&focusedCommentId=15108353#comment-15108353 ] Darshan Kumar commented on ATLAS-388: - The patch is updated with the current master and please review and let me know if there is anything. Thank you > 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-v1.patch, 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-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 ] Darshan Kumar updated ATLAS-388: Attachment: ATLAS-388-v1.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-v1.patch, 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-406) Resizing lineage window – should be an anchor on a corner – like ppt for graphic
[ https://issues.apache.org/jira/browse/ATLAS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-406: Attachment: ATLAS-406_v3.patch > Resizing lineage window – should be an anchor on a corner – like ppt for > graphic > > > Key: ATLAS-406 > URL: https://issues.apache.org/jira/browse/ATLAS-406 > Project: Atlas > Issue Type: Task >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Sanjay Patel > Attachments: ATLAS-406_v1.patch, ATLAS-406_v2.patch, > ATLAS-406_v3.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-406) Resizing lineage window – should be an anchor on a corner – like ppt for graphic
[ https://issues.apache.org/jira/browse/ATLAS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-406: Attachment: ATLAS-406_v2.patch > Resizing lineage window – should be an anchor on a corner – like ppt for > graphic > > > Key: ATLAS-406 > URL: https://issues.apache.org/jira/browse/ATLAS-406 > Project: Atlas > Issue Type: Task >Affects Versions: 0.6-incubating >Reporter: Anilsg >Assignee: Sanjay Patel > Attachments: ATLAS-406_v1.patch, ATLAS-406_v2.patch > > -- 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&focusedCommentId=15065739#comment-15065739 ] Darshan Kumar commented on ATLAS-405: - Thank you :) > 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 > Fix For: 0.6-incubating, trunk > > Attachments: ATLAS-405-v0.patch, ATLAS-405.patch, > failing_lineage.png, failing_lineage_api_responses.txt, > failing_lineage_entity_responses.txt, lineage_view_issue.png, > 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] [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&focusedCommentId=15065714#comment-15065714 ] Darshan Kumar commented on ATLAS-405: - [~yhemanth] Please find the latest patch updated with lineage view issue fix. Please review and let us know. Thanks > 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-v0.patch, ATLAS-405.patch, > failing_lineage.png, failing_lineage_api_responses.txt, > failing_lineage_entity_responses.txt, lineage_view_issue.png, > 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] [Updated] (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:all-tabpanel ] Darshan Kumar updated ATLAS-405: Attachment: ATLAS-405-v0.patch > 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-v0.patch, ATLAS-405.patch, > failing_lineage.png, failing_lineage_api_responses.txt, > failing_lineage_entity_responses.txt, lineage_view_issue.png, > 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] [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&focusedCommentId=15065681#comment-15065681 ] Darshan Kumar commented on ATLAS-405: - Yes I got to know the issue with the mock data, we are working on it.Will update you on this. Thanks for the 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, > lineage_view_issue.png, 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] [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&focusedCommentId=15065679#comment-15065679 ] Darshan Kumar commented on ATLAS-405: - Sure we will work on it. Thanks > 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, > lineage_view_issue.png, 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] [Updated] (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:all-tabpanel ] Darshan Kumar updated ATLAS-405: Attachment: spikedMockData.png > 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] [Updated] (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:all-tabpanel ] Darshan Kumar updated ATLAS-405: Attachment: ATLAS-405.patch We have used some mock data into the data model and tested with one of the complex graph. Please review and lets us know. Thanks [~Anilg] and [~yhemanth] > 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, > 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] [Commented] (ATLAS-402) UI : Validation of Associating a Tag
[ https://issues.apache.org/jira/browse/ATLAS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065397#comment-15065397 ] Darshan Kumar commented on ATLAS-402: - Sure. Thanks. > UI : Validation of Associating a Tag > --- > > Key: ATLAS-402 > URL: https://issues.apache.org/jira/browse/ATLAS-402 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-401-ATLAS-402-v0.patch, ATLAS-402-v1.patch, > ATLAS-402.patch > > > Tag association - no confirmation when linking it to an asset. I click save > the second time and I get an error saying its already there… so I know it > works but we should confirm or close the window -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-402) UI : Validation of Associating a Tag
[
https://issues.apache.org/jira/browse/ATLAS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065383#comment-15065383
]
Darshan Kumar commented on ATLAS-402:
-
This response is coming from the backend with the below error message :
{
"error": "trait=Dimension is already defined for
entity=33c58231-1f99-403b-9629-f769669101fd",
}
Thanks
> UI : Validation of Associating a Tag
> ---
>
> Key: ATLAS-402
> URL: https://issues.apache.org/jira/browse/ATLAS-402
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
> Labels: patch-available
> Attachments: ATLAS-401-ATLAS-402-v0.patch, ATLAS-402-v1.patch,
> ATLAS-402.patch
>
>
> Tag association - no confirmation when linking it to an asset. I click save
> the second time and I get an error saying its already there… so I know it
> works but we should confirm or close the window
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (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:all-tabpanel ] Darshan Kumar reassigned ATLAS-405: --- Assignee: Darshan Kumar > 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 > Attachments: failing_lineage.png, failing_lineage_api_responses.txt, > 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] [Commented] (ATLAS-402) UI : Validation of Associating a Tag
[ https://issues.apache.org/jira/browse/ATLAS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065254#comment-15065254 ] Darshan Kumar commented on ATLAS-402: - Sure I have checked and updated the patch "ATLAS-402-v1.patch". Please let me know if anything required. Thanks [~yhemanth] > UI : Validation of Associating a Tag > --- > > Key: ATLAS-402 > URL: https://issues.apache.org/jira/browse/ATLAS-402 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-401-ATLAS-402-v0.patch, ATLAS-402-v1.patch, > ATLAS-402.patch > > > Tag association - no confirmation when linking it to an asset. I click save > the second time and I get an error saying its already there… so I know it > works but we should confirm or close the window -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-402) UI : Validation of Associating a Tag
[ https://issues.apache.org/jira/browse/ATLAS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-402: Attachment: ATLAS-402-v1.patch > UI : Validation of Associating a Tag > --- > > Key: ATLAS-402 > URL: https://issues.apache.org/jira/browse/ATLAS-402 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-401-ATLAS-402-v0.patch, ATLAS-402-v1.patch, > ATLAS-402.patch > > > Tag association - no confirmation when linking it to an asset. I click save > the second time and I get an error saying its already there… so I know it > works but we should confirm or close the window -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-402) UI : Validation of Associating a Tag
[ https://issues.apache.org/jira/browse/ATLAS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-402: Attachment: ATLAS-401-ATLAS-402-v0.patch > UI : Validation of Associating a Tag > --- > > Key: ATLAS-402 > URL: https://issues.apache.org/jira/browse/ATLAS-402 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-401-ATLAS-402-v0.patch, ATLAS-402.patch > > > Tag association - no confirmation when linking it to an asset. I click save > the second time and I get an error saying its already there… so I know it > works but we should confirm or close the window -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-403) UI : On navigating to details page, Lineage api call refresh to be handled
Darshan Kumar created ATLAS-403: --- Summary: UI : On navigating to details page, Lineage api call refresh to be handled Key: ATLAS-403 URL: https://issues.apache.org/jira/browse/ATLAS-403 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Darshan Kumar Assignee: Darshan Kumar Priority: Minor Sometimes we need to refresh details page manually, occurred due to handling of response and also due to broadcast and emit I believe. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-395) UI : In details page maps not displayed for different data models
[
https://issues.apache.org/jira/browse/ATLAS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064055#comment-15064055
]
Darshan Kumar commented on ATLAS-395:
-
Thanks [~yhemanth]. I will work on it separately for the lineage and fix it.
> UI : In details page maps not displayed for different data models
> -
>
> Key: ATLAS-395
> URL: https://issues.apache.org/jira/browse/ATLAS-395
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
> Labels: patch-available
> Attachments: ATLAS-395-v1.patch, ATLAS-395.patch
>
>
> The response for scope data model
> commandlineOpts : key,value
> {
>"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
>"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
>"definition":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
> "version":0,
> "typeName":"sqoop_process"
> },
> "typeName":"sqoop_process",
> "values":{
> "name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
> "startTime":1450342252394,
> "description":null,
> "outputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "commandlineOpts":{
> "option2":"value2",
> "option1":"value1",
> "option4":"value4",
> "option3":"value3"
> },
> "endTime":1450342262394,
> "inputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "operation":"select",
> "userName":"sqoop_admin"
> },
> "traitNames":[
> ],
> "traits":{
> }
>}
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-395) UI : In details page maps not displayed for different data models
[
https://issues.apache.org/jira/browse/ATLAS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-395:
Attachment: ATLAS-395-v1.patch
As discussed [~yhemanth] I have hyperlinked the ID in details page. Please
review and let me know.
The first comment code is working for me and I checked with the trunk. Please
clear cache.Please let me know if there is anything.Thanks
> UI : In details page maps not displayed for different data models
> -
>
> Key: ATLAS-395
> URL: https://issues.apache.org/jira/browse/ATLAS-395
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
> Labels: patch-available
> Attachments: ATLAS-395-v1.patch, ATLAS-395.patch
>
>
> The response for scope data model
> commandlineOpts : key,value
> {
>"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
>"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
>"definition":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
> "version":0,
> "typeName":"sqoop_process"
> },
> "typeName":"sqoop_process",
> "values":{
> "name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
> "startTime":1450342252394,
> "description":null,
> "outputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "commandlineOpts":{
> "option2":"value2",
> "option1":"value1",
> "option4":"value4",
> "option3":"value3"
> },
> "endTime":1450342262394,
> "inputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "operation":"select",
> "userName":"sqoop_admin"
> },
> "traitNames":[
> ],
> "traits":{
> }
>}
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-402) UI : Validation of Associating a Tag
[ https://issues.apache.org/jira/browse/ATLAS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063747#comment-15063747 ] Darshan Kumar edited comment on ATLAS-402 at 12/18/15 11:09 AM: The patch has fix for Add tag validation and notification of tag associated.Please apply this patch after ATLAS-395 [~yhemanth] Thanks was (Author: darshankumar89): The patch has fix for Add tag validation and notification of tag associated. [~yhemanth] Thanks > UI : Validation of Associating a Tag > --- > > Key: ATLAS-402 > URL: https://issues.apache.org/jira/browse/ATLAS-402 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-402.patch > > > Tag association - no confirmation when linking it to an asset. I click save > the second time and I get an error saying its already there… so I know it > works but we should confirm or close the window -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-395) UI : In details page maps not displayed for different data models
[
https://issues.apache.org/jira/browse/ATLAS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063748#comment-15063748
]
Darshan Kumar commented on ATLAS-395:
-
Sure will test it and let you know. Thanks
> UI : In details page maps not displayed for different data models
> -
>
> Key: ATLAS-395
> URL: https://issues.apache.org/jira/browse/ATLAS-395
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
> Labels: patch-available
> Attachments: ATLAS-395.patch
>
>
> The response for scope data model
> commandlineOpts : key,value
> {
>"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
>"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
>"definition":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
> "version":0,
> "typeName":"sqoop_process"
> },
> "typeName":"sqoop_process",
> "values":{
> "name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
> "startTime":1450342252394,
> "description":null,
> "outputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "commandlineOpts":{
> "option2":"value2",
> "option1":"value1",
> "option4":"value4",
> "option3":"value3"
> },
> "endTime":1450342262394,
> "inputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "operation":"select",
> "userName":"sqoop_admin"
> },
> "traitNames":[
> ],
> "traits":{
> }
>}
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-402) UI : Validation of Associating a Tag
[ https://issues.apache.org/jira/browse/ATLAS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-402: Attachment: ATLAS-402.patch The patch has fix for Add tag validation and notification of tag associated. [~yhemanth] Thanks > UI : Validation of Associating a Tag > --- > > Key: ATLAS-402 > URL: https://issues.apache.org/jira/browse/ATLAS-402 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-402.patch > > > Tag association - no confirmation when linking it to an asset. I click save > the second time and I get an error saying its already there… so I know it > works but we should confirm or close the window -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-402) UI : Validation of Associating a Tag
Darshan Kumar created ATLAS-402: --- Summary: UI : Validation of Associating a Tag Key: ATLAS-402 URL: https://issues.apache.org/jira/browse/ATLAS-402 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Darshan Kumar Assignee: Darshan Kumar Tag association - no confirmation when linking it to an asset. I click save the second time and I get an error saying its already there… so I know it works but we should confirm or close the window -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-401) UI : Search Result table isn’t aligned well for scoop data model
[ https://issues.apache.org/jira/browse/ATLAS-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-401: Attachment: screen1.png > UI : Search Result table isn’t aligned well for scoop data model > - > > Key: ATLAS-401 > URL: https://issues.apache.org/jira/browse/ATLAS-401 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Darshan Kumar >Assignee: Darshan Kumar >Priority: Minor > Attachments: screen1.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-401) UI : Search Result table isn’t aligned well for scoop data model
Darshan Kumar created ATLAS-401: --- Summary: UI : Search Result table isn’t aligned well for scoop data model Key: ATLAS-401 URL: https://issues.apache.org/jira/browse/ATLAS-401 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Darshan Kumar Assignee: Darshan Kumar Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-395) UI : In details page maps not displayed for different data models
[
https://issues.apache.org/jira/browse/ATLAS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062647#comment-15062647
]
Darshan Kumar commented on ATLAS-395:
-
The patch is updated. Please review [~yhemanth]. Thanks
> UI : In details page maps not displayed for different data models
> -
>
> Key: ATLAS-395
> URL: https://issues.apache.org/jira/browse/ATLAS-395
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
> Labels: patch-available
> Attachments: ATLAS-395.patch
>
>
> The response for scope data model
> commandlineOpts : key,value
> {
>"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
>"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
>"definition":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
> "version":0,
> "typeName":"sqoop_process"
> },
> "typeName":"sqoop_process",
> "values":{
> "name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
> "startTime":1450342252394,
> "description":null,
> "outputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "commandlineOpts":{
> "option2":"value2",
> "option1":"value1",
> "option4":"value4",
> "option3":"value3"
> },
> "endTime":1450342262394,
> "inputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "operation":"select",
> "userName":"sqoop_admin"
> },
> "traitNames":[
> ],
> "traits":{
> }
>}
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-395) UI : In details page maps not displayed for different data models
[
https://issues.apache.org/jira/browse/ATLAS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-395:
Attachment: ATLAS-395.patch
> UI : In details page maps not displayed for different data models
> -
>
> Key: ATLAS-395
> URL: https://issues.apache.org/jira/browse/ATLAS-395
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
> Labels: patch-available
> Attachments: ATLAS-395.patch
>
>
> The response for scope data model
> commandlineOpts : key,value
> {
>"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
>"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
>"definition":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
> "version":0,
> "typeName":"sqoop_process"
> },
> "typeName":"sqoop_process",
> "values":{
> "name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
> "startTime":1450342252394,
> "description":null,
> "outputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "commandlineOpts":{
> "option2":"value2",
> "option1":"value1",
> "option4":"value4",
> "option3":"value3"
> },
> "endTime":1450342262394,
> "inputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "operation":"select",
> "userName":"sqoop_admin"
> },
> "traitNames":[
> ],
> "traits":{
> }
>}
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-395) UI : In details page maps not displayed for different data models
[
https://issues.apache.org/jira/browse/ATLAS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-395:
Description:
The response for scope data model
commandlineOpts : key,value
{
"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
"definition":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
"version":0,
"typeName":"sqoop_process"
},
"typeName":"sqoop_process",
"values":{
"name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
"startTime":1450342252394,
"description":null,
"outputs":[
{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
"version":0,
"typeName":"DataSet"
}
],
"commandlineOpts":{
"option2":"value2",
"option1":"value1",
"option4":"value4",
"option3":"value3"
},
"endTime":1450342262394,
"inputs":[
{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
"version":0,
"typeName":"DataSet"
}
],
"operation":"select",
"userName":"sqoop_admin"
},
"traitNames":[
],
"traits":{
}
}
}
was:
commandlineOpts : key,value
{
"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
"definition":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
"version":0,
"typeName":"sqoop_process"
},
"typeName":"sqoop_process",
"values":{
"name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
"startTime":1450342252394,
"description":null,
"outputs":[
{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
"version":0,
"typeName":"DataSet"
}
],
"commandlineOpts":{
"option2":"value2",
"option1":"value1",
"option4":"value4",
"option3":"value3"
},
"endTime":1450342262394,
"inputs":[
{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
"version":0,
"typeName":"DataSet"
}
],
"operation":"select",
"userName":"sqoop_admin"
},
"traitNames":[
],
"traits":{
}
}
}
> UI : In details page maps not displayed for different data models
> -
>
> Key: ATLAS-395
> URL: https://issues.apache.org/jira/browse/ATLAS-395
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
>
> The response for scope data model
> commandlineOpts : key,value
> {
>"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
>"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
>"definition":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
> "version":0,
> "typeName":"sqoop_process"
> },
> "typeName":"sqoop_process",
> "values":{
> "name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
> "startTime":1450342252394,
> "description":null,
> "outputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "commandlineOpts":{
> "option2":"value2",
> "option1":"value1",
> "option4":"value4",
>
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15062226#comment-15062226 ] Darshan Kumar commented on ATLAS-385: - Thank you [~yhemanth] and [~rishabhbhardwaj] > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, > ATLAS-385-v3.patch, ATLAS-385.patch, 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] [Updated] (ATLAS-395) UI : In details page maps not displayed for different data models
[
https://issues.apache.org/jira/browse/ATLAS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-395:
Summary: UI : In details page maps not displayed for different data models
(was: UI : In details page maps not displayed )
> UI : In details page maps not displayed for different data models
> -
>
> Key: ATLAS-395
> URL: https://issues.apache.org/jira/browse/ATLAS-395
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
>
> commandlineOpts : key,value
> {
>"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
>"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
>"definition":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
> "version":0,
> "typeName":"sqoop_process"
> },
> "typeName":"sqoop_process",
> "values":{
> "name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
> "startTime":1450342252394,
> "description":null,
> "outputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "commandlineOpts":{
> "option2":"value2",
> "option1":"value1",
> "option4":"value4",
> "option3":"value3"
> },
> "endTime":1450342262394,
> "inputs":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
>"version":0,
>"typeName":"DataSet"
> }
> ],
> "operation":"select",
> "userName":"sqoop_admin"
> },
> "traitNames":[
> ],
> "traits":{
> }
>}
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-395) UI : In details page maps not displayed
Darshan Kumar created ATLAS-395:
---
Summary: UI : In details page maps not displayed
Key: ATLAS-395
URL: https://issues.apache.org/jira/browse/ATLAS-395
Project: Atlas
Issue Type: Bug
Affects Versions: 0.6-incubating
Reporter: Darshan Kumar
Assignee: Darshan Kumar
commandlineOpts : key,value
{
"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
"definition":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
"version":0,
"typeName":"sqoop_process"
},
"typeName":"sqoop_process",
"values":{
"name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
"startTime":1450342252394,
"description":null,
"outputs":[
{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
"version":0,
"typeName":"DataSet"
}
],
"commandlineOpts":{
"option2":"value2",
"option1":"value1",
"option4":"value4",
"option3":"value3"
},
"endTime":1450342262394,
"inputs":[
{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
"version":0,
"typeName":"DataSet"
}
],
"operation":"select",
"userName":"sqoop_admin"
},
"traitNames":[
],
"traits":{
}
}
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (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 ] Darshan Kumar updated ATLAS-385: Attachment: (was: ATLAS-385-v4.patch) > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, > ATLAS-385-v3.patch, ATLAS-385.patch, 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] [Updated] (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 ] Darshan Kumar updated ATLAS-385: Attachment: ATLAS-385-v3.patch > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, > ATLAS-385-v3.patch, ATLAS-385.patch, 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] [Updated] (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 ] Darshan Kumar updated ATLAS-385: Attachment: ATLAS-385-v4.patch > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, > ATLAS-385-v4.patch, ATLAS-385.patch, 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-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:comment-tabpanel&focusedCommentId=15061640#comment-15061640 ] Darshan Kumar commented on ATLAS-385: - Thanks [~yhemanth] Will update the patch with this fix please let me know if anything. Thanks > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, ATLAS-385.patch, > 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] [Updated] (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 ] Darshan Kumar updated ATLAS-385: Attachment: ATLAS-385-v2.patch > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, ATLAS-385.patch, > 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] [Updated] (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 ] Darshan Kumar updated ATLAS-385: Attachment: ATLAS-385-v1.patch > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385.patch, > 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-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:comment-tabpanel&focusedCommentId=15058427#comment-15058427 ] Darshan Kumar commented on ATLAS-385: - [~rishabhbhardwaj] Please can you send the API response of details, graph and entities. > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385.patch, 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] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15057846#comment-15057846 ] Darshan Kumar edited comment on ATLAS-385 at 12/15/15 6:01 PM: --- The Lineage graph exception handling is fixed and Tested with Hive and Falcon data model used from "feed_enhancements.txt". Please find the patch attached. Thanks was (Author: darshankumar89): The Lineage graph exception handling is fixed and Tested with Hive and Falcon data model. Please find the patch attached. Thanks > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385.patch, 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] [Updated] (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 ] Darshan Kumar updated ATLAS-385: Fix Version/s: 0.6-incubating > 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 > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385.patch, 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] [Assigned] (ATLAS-284) UI not displaying the lineage for complex hive table (CTAS)
[
https://issues.apache.org/jira/browse/ATLAS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar reassigned ATLAS-284:
---
Assignee: Darshan Kumar (was: Rohit)
> UI not displaying the lineage for complex hive table (CTAS)
> ---
>
> Key: ATLAS-284
> URL: https://issues.apache.org/jira/browse/ATLAS-284
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
>Assignee: Darshan Kumar
> Fix For: 0.6-incubating
>
> Attachments: graph_not_shown_application.log
>
>
> UI not displaying the lineage for complex hive table (CTAS).
> 1. On hive cli, create a hive table using CTAS just like below..
> Use this query:
> create table table_1251 as select employee.salary as salary, t2.temp as
> integer, t1.temp as number, nested.propertyid as
> string, nested.propertyName as propname, table_1243.number as num,
> table_1250.number as prism, temp_batting.col_value as
> temp1 from employee, t2, t1, nested, table_1243, table_1250, temp_batting;
> 2. Now try to view the graph on ATLAS UI for the above table. - No Graph is
> displayed where as the backend API request is successful.
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1261/inputs/graph'
> -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
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 38250 38250 0 3813 0 --:--:-- 0:00:01 --:--:-- 3813
> {
> "requestId": "qtp1610708593-415 - fb672eb4-2ce2-4485-8350-ba1f919ece02",
> "results": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "__tempQueryResultStruct65",
> "values": {
> "edges": {
> "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": [
> "ebde1571-2ced-46d6-b65c-558835224764"
> ],
> "ebde1571-2ced-46d6-b65c-558835224764": [
> "364d6dc1-fdcc-4d03-8df7-cf1d835730af",
> "6b52aa8f-134d-4ab7-9389-4568fac87533",
> "7c1af593-b7b1-4838-815b-872b8a163a40",
> "ce01cbb6-ffd5-42c8-8c15-3f72bcef45c1",
> "b040d1e4-dd96-4729-8f55-4da4c958ff8f",
> "f82337ea-1e0c-4c28-a491-4916be594b49",
> "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012"
> ]
> },
> "vertices": {
> "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "__tempQueryResultStruct64",
> "values": {
> "name": "primary.default.employee",
> "vertexId": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "__IdType",
> "values": {
> "guid":
> "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012",
> "typeName": "hive_table"
> }
> }
> }
> },
> "364d6dc1-fdcc-4d03-8df7-cf1d835730af": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "__tempQueryResultStruct64",
> "values": {
> "name": "primary.default.t1",
> "vertexId": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "__IdType",
> "values": {
> "guid":
> "364d6dc1-fdcc-4d03-8df7-cf1d835730af",
> "typeName": "hive_table"
> }
> }
> }
> },
> "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "__tempQueryResultStruct64",
> "values": {
>
[jira] [Updated] (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 ] Darshan Kumar updated ATLAS-385: Attachment: ATLAS-385.patch The Lineage graph exception handling is fixed and Tested with Hive and Falcon data model. Please find the patch attached. Thanks > 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: ATLAS-385.patch, 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-244) UI: Add Tag Tab
[ https://issues.apache.org/jira/browse/ATLAS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052689#comment-15052689 ] Darshan Kumar commented on ATLAS-244: - Thank you [~suma.shivaprasad] and [~yhemanth] > 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, trunk > > Attachments: ATLAS-244-v1.patch > > > 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] [Updated] (ATLAS-244) UI: Add Tag Tab
[ https://issues.apache.org/jira/browse/ATLAS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-244: Attachment: ATLAS-244-v1.patch Please review and let me know. Thanks [~yhemanth] > 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 > > Attachments: ATLAS-244-v1.patch > > > 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-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052231#comment-15052231 ] Darshan Kumar commented on ATLAS-376: - Thank you [~yhemanth] and [~suma.shivaprasad] > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Fix For: 0.6-incubating, trunk > > Attachments: ATLAS-376-ATLAS-314-v1.patch, > ATLAS-376-ATLAS-314-v2.patch, ATLAS-376-ATLAS-314.patch, schema_response.json > > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052075#comment-15052075 ] Darshan Kumar commented on ATLAS-376: - we have addressed the above issues and patch is updated. please review and let us know. Thanks [~yhemanth] > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-376-ATLAS-314-v1.patch, > ATLAS-376-ATLAS-314-v2.patch, ATLAS-376-ATLAS-314.patch, schema_response.json > > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-376: Attachment: ATLAS-376-ATLAS-314-v2.patch > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-376-ATLAS-314-v1.patch, > ATLAS-376-ATLAS-314-v2.patch, ATLAS-376-ATLAS-314.patch, schema_response.json > > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-214) UI : For any hive_table, schema/input/output tabs are not displayed
[ https://issues.apache.org/jira/browse/ATLAS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051151#comment-15051151 ] Darshan Kumar commented on ATLAS-214: - We are working on it and it will be fixed with ATLAS-376 as a part of schema > UI : For any hive_table, schema/input/output tabs are not displayed > --- > > Key: ATLAS-214 > URL: https://issues.apache.org/jira/browse/ATLAS-214 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Darshan Kumar >Priority: Blocker > Labels: ATLAS-UI-BUGS > Attachments: Hive_Table_snapshot.png, Table_snapshot.png > > > In Atlas UI, for any hive_tables schema/input/output tabs are not displayed. > whereas for other tables these tabs are shown. > Please take a look at the UI snapshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-244) UI: Add Tag Tab
[
https://issues.apache.org/jira/browse/ATLAS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051131#comment-15051131
]
Darshan Kumar commented on ATLAS-244:
-
JSON response for hive
the attributes as key=value pairs (comma separated) that would be great
Note that the response does contain these
In this form: "traits": {
"tag1": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
"typeName": "tag1",
"values": {
"tag_attr1": "val1"
}
}
}
You can just pick the “values” map and show them as key=value (comma separated)
> 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] [Updated] (ATLAS-199) webapp build fails (grunt + tests)
[
https://issues.apache.org/jira/browse/ATLAS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-199:
Assignee: Sanjay Patel (was: Darshan Kumar)
> webapp build fails (grunt + tests)
> --
>
> Key: ATLAS-199
> URL: https://issues.apache.org/jira/browse/ATLAS-199
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Sanjay Patel
>Priority: Critical
> Labels: ATLAS-UI-BUGS
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-199-v0.patch
>
>
> When building Atlas webapp, I see the following issues:
> mvn clean install:
> {code}
> [INFO] Running 'grunt bower --no-color' in
> /Users/ebergenholtz/git3/incubator-atlas/dashboard
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 34.282 s
> [INFO] Finished at: 2015-09-30T13:55:30-05:00
> [INFO] Final Memory: 35M/420M
> [INFO]
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (install bower) on
> project atlas-webapp: Failed to run task: 'grunt bower --no-color' failed.
> java.io.IOException: Cannot run program
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard/node/node" (in directory
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard"): error=2, No such file
> or directory -> [Help 1]
> {code}
> Also, if I bypass the grunt task some of the tests fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-376: Attachment: ATLAS-376-ATLAS-314-v1.patch > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-376-ATLAS-314-v1.patch, ATLAS-376-ATLAS-314.patch, > schema_response.json > > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048179#comment-15048179 ] Darshan Kumar edited comment on ATLAS-376 at 12/9/15 9:38 AM: -- Please find the patch and the tested url : http://52.27.169.250:3228/#!/search. Thanks was (Author: darshankumar89): Please fin the patch and the tested url : http://52.27.169.250:3228/#!/search. Thanks > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-376-ATLAS-314.patch, schema_response.json > > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-376: Attachment: ATLAS-376-ATLAS-314.patch > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Attachments: ATLAS-376-ATLAS-314.patch, schema_response.json > > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
