[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=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=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-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=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: 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=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=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] [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=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] [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=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] [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] [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-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=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=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] [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=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] [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] [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-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=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-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=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=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=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] [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=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] [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] [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] [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=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] [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=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-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=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] [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=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] [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] [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-402) UI : Validation of Associating a Tag
[ https://issues.apache.org/jira/browse/ATLAS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [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=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:
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-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=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] [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] [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-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-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] [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=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] [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=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] [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=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] [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-244) UI: Add Tag Tab
[
https://issues.apache.org/jira/browse/ATLAS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [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=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] [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] [Assigned] (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 reassigned ATLAS-376: --- Assignee: Darshan Kumar > 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: 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-314) UI: use schema API exclusively instead of schema from details API.
[ https://issues.apache.org/jira/browse/ATLAS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047366#comment-15047366 ] Darshan Kumar commented on ATLAS-314: - This is a part of ATLAS-376 > UI: use schema API exclusively instead of schema from details API. > -- > > Key: ATLAS-314 > URL: https://issues.apache.org/jira/browse/ATLAS-314 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > use schema API exclusively instead of schema from details api. -- 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)
[jira] [Commented] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044511#comment-15044511
]
Darshan Kumar commented on ATLAS-279:
-
Issues No 4. is fixed and available in same patch. Thanks
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239-ATLAS-345_v8.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v10.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v6.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v7.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v9.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch,
> can_select_empty_line_in_parents.png, hive_table_select_bug.png,
> hive_table_select_bug.txt, tag_addition_missing_attr_name_bug.png,
> tag_addition_missing_attr_name_bug.txt,
> tag_association_missing_child_attrs.png
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [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: Labels: ATLAS-UI-BUGS (was: ) > 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 > > 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] [Created] (ATLAS-364) UI Code standardization
Darshan Kumar created ATLAS-364: --- Summary: 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 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] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-279:
Attachment: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v9.patch
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239-ATLAS-345_v8.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v6.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v7.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v9.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037359#comment-15037359
]
Darshan Kumar commented on ATLAS-279:
-
Sure will verify in internal branch with 0.5 and the patch available here is
for Apache master. Thanks for the findings [~ayubkhan]
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239-ATLAS-345_v8.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v6.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v7.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037360#comment-15037360
]
Darshan Kumar commented on ATLAS-279:
-
Sure will verify in internal branch with 0.5 and the patch available here is
for Apache master. Thanks for the findings [~ayubkhan]
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239-ATLAS-345_v8.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v6.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v7.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-279:
Comment: was deleted
(was: Sure will verify in internal branch with 0.5 and the patch available here
is for Apache master. Thanks for the findings [~ayubkhan])
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239-ATLAS-345_v8.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v6.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v7.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-325) UI: Replace add Attribute button with plus icon.
[ https://issues.apache.org/jira/browse/ATLAS-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034111#comment-15034111 ] Darshan Kumar commented on ATLAS-325: - This patch is a part of ATLAS-279 > UI: Replace add Attribute button with plus icon. > > > Key: ATLAS-325 > URL: https://issues.apache.org/jira/browse/ATLAS-325 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > Replace add Attribute button with plus icon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-325) UI: Replace add Attribute button with plus icon.
[ https://issues.apache.org/jira/browse/ATLAS-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-325: --- Assignee: Darshan Kumar > UI: Replace add Attribute button with plus icon. > > > Key: ATLAS-325 > URL: https://issues.apache.org/jira/browse/ATLAS-325 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > Replace add Attribute button with plus icon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-279:
Attachment: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v3.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v4.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v5.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-307) Help link to be pointed to apache atlas website
[ https://issues.apache.org/jira/browse/ATLAS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-307: --- Assignee: Darshan Kumar > Help link to be pointed to apache atlas website > --- > > Key: ATLAS-307 > URL: https://issues.apache.org/jira/browse/ATLAS-307 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > Help link to be pointed to apache atlas website. > http://atlas.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-314) UI: use schema API exclusively instead of schema from details API.
[ https://issues.apache.org/jira/browse/ATLAS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-314: --- Assignee: Darshan Kumar > UI: use schema API exclusively instead of schema from details API. > -- > > Key: ATLAS-314 > URL: https://issues.apache.org/jira/browse/ATLAS-314 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > use schema API exclusively instead of schema from details api. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-331) UI: Keep UI, Backward compatibility.
[ https://issues.apache.org/jira/browse/ATLAS-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15014038#comment-15014038 ] Darshan Kumar commented on ATLAS-331: - [~bergenholtz] UI should be backward compatible in a sense that after releasing a first version of an application some API response structure is changed. In this case, UI code should be written in a way that it should work with both the version with released and the new one[changed one] For example: We had a release of ATLAS as 0.5-incubating. Now in new release 0.6-incubating backend API [ api/atlas/entity ] response structure is changed. So UI code should work with both the releases 0.5-incubating and 0.6-incubationg. > UI: Keep UI, Backward compatibility. > > > Key: ATLAS-331 > URL: https://issues.apache.org/jira/browse/ATLAS-331 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Priority: Minor > Labels: Atlas-UI > > Keep UI, Backward compatibility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-331) UI: Keep UI, Backward compatibility.
[ https://issues.apache.org/jira/browse/ATLAS-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-331: Description: We had a release of ATLAS as 0.5-incubating. Now in new release 0.6-incubating backend API [ api/atlas/entity ] response structure is changed. So UI code should work with both the releases 0.5-incubating and 0.6-incubating was:Keep UI, Backward compatibility. > UI: Keep UI, Backward compatibility. > > > Key: ATLAS-331 > URL: https://issues.apache.org/jira/browse/ATLAS-331 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Priority: Minor > Labels: Atlas-UI > > We had a release of ATLAS as 0.5-incubating. Now in new release > 0.6-incubating backend API [ api/atlas/entity ] response structure is > changed. > So UI code should work with both the releases 0.5-incubating and > 0.6-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-324) UI: In Create tag add multiplicity,data type attribute.
[ https://issues.apache.org/jira/browse/ATLAS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-324: --- Assignee: Darshan Kumar > UI: In Create tag add multiplicity,data type attribute. > --- > > Key: ATLAS-324 > URL: https://issues.apache.org/jira/browse/ATLAS-324 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > In Create tag add multiplicity,data type attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-279:
Attachment: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments:
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v1.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264-ATLAS-239_v2.patch,
> ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-279:
Attachment: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar reopened ATLAS-279:
-
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Labels: patch-available
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar updated ATLAS-279:
Flags: Patch
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-279) UI not displaying results for certain successful "select" search queries
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darshan Kumar reassigned ATLAS-279:
---
Assignee: Darshan Kumar (was: Anilsg)
> UI not displaying results for certain successful "select" search queries
>
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Darshan Kumar
> Labels: patch-available
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI.
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
> -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive'
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer:
> http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-293) UI Requires Internet Access For UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-293: Attachment: ATLAS-293.patch > UI Requires Internet Access For UI Facelift > > > Key: ATLAS-293 > URL: https://issues.apache.org/jira/browse/ATLAS-293 > Project: Atlas > Issue Type: Bug >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-293.patch > > > This issue is with reference to the ATLAS-198 as a part of UI FaceLift -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-211) UI: UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995233#comment-14995233 ] Darshan Kumar commented on ATLAS-211: - Thank you [~ltfxyz] . The patch for the fix that overwrites is available in ATLAS-293. Thanks > UI: UI Facelift > --- > > Key: ATLAS-211 > URL: https://issues.apache.org/jira/browse/ATLAS-211 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-211-ATLAS-219-ATLAS-214-Atlas-261_v10.patch, > ATLAS-211-ATLAS-219-ATLAS-214_v9.patch, ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, ATLAS-211-ATLAS-224_v4.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v6.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v7.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v8.patch, ATLAS-211-Comments-Fixed-V5.patch, > ATLAS-211_ATLAS-262_ATLAS-268_v2.patch, Apache-ATlas-lenghtly-trait.png, > Apache-Atlas-Avoid-Extra-Get-For-Trait-Creation.png, > Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-Tag-Creation-Dumps-Json.png, Apache-Atlas-long-trait-name.png, > Atlas-Tag-Drop-Down-Listing-only-First-30-entries.png, Screen Shot 2015-10-26 > at 11.29.19 PM.png, Screen Shot 2015-10-26 at 11.34.57 PM.png, Screen Shot > 2015-10-28 at 9.35.53 AM.png, Screen Shot 2015-10-29 at 9.56.34 AM.png, > Search.png, tags.png > > > Adopt new look and feel for all screens as shown here: > http://mprhost.com/hw/atlas/rahul/atlashtml/search.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-293) UI Requires Internet Access For UI Facelift
Darshan Kumar created ATLAS-293: --- Summary: UI Requires Internet Access For UI Facelift Key: ATLAS-293 URL: https://issues.apache.org/jira/browse/ATLAS-293 Project: Atlas Issue Type: Bug Reporter: Darshan Kumar Assignee: Darshan Kumar This issue is with reference to the ATLAS-198 as a part of UI FaceLift -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-265) Tags listed in the dropdown are limited to 30 when tried to add tag to an entity. This will limit the user to use only the first 30 tags even though we have more tags
[ https://issues.apache.org/jira/browse/ATLAS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993905#comment-14993905 ] Darshan Kumar commented on ATLAS-265: - [~suma.shivaprasad] This issue is fixed as a part of ATLAS-211 patch. > Tags listed in the dropdown are limited to 30 when tried to add tag to an > entity. This will limit the user to use only the first 30 tags even though we > have more tags > -- > > Key: ATLAS-265 > URL: https://issues.apache.org/jira/browse/ATLAS-265 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Darshan Kumar > Labels: ATLAS-UI-BUGS, patch-available > > Tags listed in the dropdown are limited to 30 when tried to add tag to an > entity. This will limit the user to use only the first 30 tags even though we > have more tags... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
