Review Request 60240: ATLAS-1888 : UI - While Update Entity the data of type Long is not updating in entity from UI
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60240/ --- Review request for atlas, keval bhatt, Madhan Neethiraj, and Nixon Rodrigues. Bugs: ATLAS-1888 https://issues.apache.org/jira/browse/ATLAS-1888 Repository: atlas Description --- Step to reproduce : * Search for the Table. * Go to sales_fact_monthly_mv, and update CreateTime, LastAccessTime * Click on update button * CreateTime and LastAccessTime are not updating properly. Diffs - dashboardv2/public/js/views/entity/CreateEntityLayoutView.js 704062f Diff: https://reviews.apache.org/r/60240/diff/1/ Testing --- CreateTime and LastAccessTime in sales_fact_monthly_mv of type Table is updating properly and other type entities. Thanks, Kalyani Kashikar
[jira] [Updated] (ATLAS-1888) UI - While Update Entity the data of type Long is not updating in entity from UI.
[ https://issues.apache.org/jira/browse/ATLAS-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1888: Attachment: ATLAS-1888.patch > UI - While Update Entity the data of type Long is not updating in entity from > UI. > - > > Key: ATLAS-1888 > URL: https://issues.apache.org/jira/browse/ATLAS-1888 > Project: Atlas > Issue Type: Bug > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1888.patch > > > Step to reproduce :- > * Search for the Table. > * Go to sales_fact_monthly_mv, and update CreateTime, LastAccessTime > * Click on update button > * CreateTime and LastAccessTime are not updating properly. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1888) UI - While Update Entity the data of type Long is not updating in entity from UI.
Kalyani Kashikar created ATLAS-1888: --- Summary: UI - While Update Entity the data of type Long is not updating in entity from UI. Key: ATLAS-1888 URL: https://issues.apache.org/jira/browse/ATLAS-1888 Project: Atlas Issue Type: Bug Reporter: Kalyani Kashikar Assignee: Kalyani Kashikar Step to reproduce :- * Search for the Table. * Go to sales_fact_monthly_mv, and update CreateTime, LastAccessTime * Click on update button * CreateTime and LastAccessTime are not updating properly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1832) If no attribute is present in tag then showing edit-button for a tag in tags tab on entity page.
[ https://issues.apache.org/jira/browse/ATLAS-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049144#comment-16049144 ] Kalyani Kashikar commented on ATLAS-1832: - Committed patch on following branches * master : https://git1-us-west.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=c2c05d67 * 0.8-incubating : https://git1-us-west.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=8f2df311 > If no attribute is present in tag then showing edit-button for a tag in tags > tab on entity page. > - > > Key: ATLAS-1832 > URL: https://issues.apache.org/jira/browse/ATLAS-1832 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating > Environment: Chrome >Reporter: Nixon Rodrigues >Assignee: Kalyani Kashikar > Attachments: ATLAS-1832.1.patch, ATLAS-1832.patch, edit attribute for > tag bug .png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Review Request 59876: ATLAS-1832 - If no attribute is present in tag then showing edit-button for a tag in tags tab on entity page.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59876/ --- (Updated June 13, 2017, 6:59 a.m.) Review request for atlas, keval bhatt, Madhan Neethiraj, and Nixon Rodrigues. Changes --- Rebase patch for minor change in font size for audit modal. Bugs: ATLAS-1832 https://issues.apache.org/jira/browse/ATLAS-1832 Repository: atlas Description --- Step to reproduce : - Create tag without attribute. Tag detail page shows the edit button whether attribute is present or not. Diffs (updated) - dashboardv2/public/js/templates/audit/CreateAuditTableLayoutView_tmpl.html fc8e6cc dashboardv2/public/js/views/tag/TagDetailTableLayoutView.js cdbd00f Diff: https://reviews.apache.org/r/59876/diff/2/ Changes: https://reviews.apache.org/r/59876/diff/1-2/ Testing --- If no attribute is present in tag then detail page does not show edit button. It only visiable when attribute is present in tag. Thanks, Kalyani Kashikar
[jira] [Updated] (ATLAS-1832) If no attribute is present in tag then showing edit-button for a tag in tags tab on entity page.
[ https://issues.apache.org/jira/browse/ATLAS-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1832: Attachment: ATLAS-1832.1.patch Minor change in font size for audit Modal. > If no attribute is present in tag then showing edit-button for a tag in tags > tab on entity page. > - > > Key: ATLAS-1832 > URL: https://issues.apache.org/jira/browse/ATLAS-1832 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating > Environment: Chrome >Reporter: Nixon Rodrigues >Assignee: Kalyani Kashikar > Attachments: ATLAS-1832.1.patch, ATLAS-1832.patch, edit attribute for > tag bug .png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Review Request 59876: ATLAS-1832 - If no attribute is present in tag then showing edit-button for a tag in tags tab on entity page.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59876/ --- Review request for atlas, keval bhatt, Madhan Neethiraj, and Nixon Rodrigues. Bugs: ATLAS-1832 https://issues.apache.org/jira/browse/ATLAS-1832 Repository: atlas Description --- Step to reproduce : - Create tag without attribute. Tag detail page shows the edit button whether attribute is present or not. Diffs - dashboardv2/public/js/views/tag/TagDetailTableLayoutView.js cdbd00f Diff: https://reviews.apache.org/r/59876/diff/1/ Testing --- If no attribute is present in tag then detail page does not show edit button. It only visiable when attribute is present in tag. Thanks, Kalyani Kashikar
[jira] [Commented] (ATLAS-1817) UI : n+1 pages are created, even though only n*25 instances are retrieved.
[ https://issues.apache.org/jira/browse/ATLAS-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029376#comment-16029376 ] Kalyani Kashikar commented on ATLAS-1817: - Committed patch on following branches * master : https://git1-us-west.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=9d6ad848 * 0.8-incubating : https://git1-us-west.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=08c60a20 > UI : n+1 pages are created, even though only n*25 instances are retrieved. > -- > > Key: ATLAS-1817 > URL: https://issues.apache.org/jira/browse/ATLAS-1817 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk, 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1817.1.patch, ATLAS-1817.patch > > > 1.Created 50 tables. > 2.First page showed 1-25 tables , second page 26 -50 tables . > 3.Clicking Next button navigates to 3rd page with 26-50 as range with empty > response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1848) UI- Remove json2.js library from atlas
[ https://issues.apache.org/jira/browse/ATLAS-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1848: Attachment: ATLAS-1848.patch > UI- Remove json2.js library from atlas > -- > > Key: ATLAS-1848 > URL: https://issues.apache.org/jira/browse/ATLAS-1848 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating, 0.9-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1848.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1817) UI : n+1 pages are created, even though only n*25 instances are retrieved.
[ https://issues.apache.org/jira/browse/ATLAS-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029301#comment-16029301 ] Kalyani Kashikar commented on ATLAS-1817: - Found regression for this issue. TagLayout page shows blank when tag is not associated with any entity. Patch is available for this issue in ATLAS-1817.1.patch attached > UI : n+1 pages are created, even though only n*25 instances are retrieved. > -- > > Key: ATLAS-1817 > URL: https://issues.apache.org/jira/browse/ATLAS-1817 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk, 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1817.1.patch, ATLAS-1817.patch > > > 1.Created 50 tables. > 2.First page showed 1-25 tables , second page 26 -50 tables . > 3.Clicking Next button navigates to 3rd page with 26-50 as range with empty > response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (ATLAS-1817) UI : n+1 pages are created, even though only n*25 instances are retrieved.
[ https://issues.apache.org/jira/browse/ATLAS-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reopened ATLAS-1817: - > UI : n+1 pages are created, even though only n*25 instances are retrieved. > -- > > Key: ATLAS-1817 > URL: https://issues.apache.org/jira/browse/ATLAS-1817 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk, 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1817.1.patch, ATLAS-1817.patch > > > 1.Created 50 tables. > 2.First page showed 1-25 tables , second page 26 -50 tables . > 3.Clicking Next button navigates to 3rd page with 26-50 as range with empty > response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1817) UI : n+1 pages are created, even though only n*25 instances are retrieved.
[ https://issues.apache.org/jira/browse/ATLAS-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1817: Attachment: ATLAS-1817.1.patch > UI : n+1 pages are created, even though only n*25 instances are retrieved. > -- > > Key: ATLAS-1817 > URL: https://issues.apache.org/jira/browse/ATLAS-1817 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk, 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1817.1.patch, ATLAS-1817.patch > > > 1.Created 50 tables. > 2.First page showed 1-25 tables , second page 26 -50 tables . > 3.Clicking Next button navigates to 3rd page with 26-50 as range with empty > response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1848) UI- Remove json2.js library from atlas
Kalyani Kashikar created ATLAS-1848: --- Summary: UI- Remove json2.js library from atlas Key: ATLAS-1848 URL: https://issues.apache.org/jira/browse/ATLAS-1848 Project: Atlas Issue Type: Bug Affects Versions: 0.8-incubating, 0.9-incubating Reporter: Kalyani Kashikar Assignee: Kalyani Kashikar Fix For: 0.8-incubating, 0.9-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1833) (Create Tag) - If a Tag is created without description then in update Description tag name appears.
Kalyani Kashikar created ATLAS-1833:
---
Summary: (Create Tag) - If a Tag is created without description
then in update Description tag name appears.
Key: ATLAS-1833
URL: https://issues.apache.org/jira/browse/ATLAS-1833
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Kalyani Kashikar
Assignee: Nixon Rodrigues
requestJSON -
{code}
{
"classificationDefs": [{
"name": "test2",
"description": "",
"superTypes": [],
"attributeDefs": []
}],
"entityDefs": [],
"enumDefs": [],
"structDefs": []
}
{code}
ResponseJSON :
{code}
{
"enumDefs": [],
"structDefs": [],
"classificationDefs": [{
"category": "CLASSIFICATION",
"guid": "cb2af955-d2de-4754-bcdf-58f76763c293",
"createTime": 1495795905288,
"updateTime": 1495795905288,
"version": 1,
"name": "test2",
"description": "test2",
"typeVersion": "1.0",
"attributeDefs": [],
"superTypes": []
}],
"entityDefs": []
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1811) UI : Audit Events are not shown in sorted order based on time sometimes.
[ https://issues.apache.org/jira/browse/ATLAS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1811: Attachment: ATLAS-1811.patch > UI : Audit Events are not shown in sorted order based on time sometimes. > > > Key: ATLAS-1811 > URL: https://issues.apache.org/jira/browse/ATLAS-1811 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk, 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Attachments: ATLAS-1811.patch, AuditDetailsUnordered.png > > > Created an entity and made did many tag association , dis-association and tag > update to that entity. All audit details are captured but not displayed in > sorted order based on timestamp value present in audit response. A few > entries are missing order. > Attached the screenshot . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1806) Error while redirecting it to Tag tab after doing advance search and creating entity
[ https://issues.apache.org/jira/browse/ATLAS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022725#comment-16022725 ] Kalyani Kashikar commented on ATLAS-1806: - This issue has been fixed in ATLAS-1812. > Error while redirecting it to Tag tab after doing advance search and creating > entity > > > Key: ATLAS-1806 > URL: https://issues.apache.org/jira/browse/ATLAS-1806 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Kalyani Kashikar > Attachments: SS11.png > > > Steps to reproduce:- > 1.Do an Advance Search > 2.Then create an entity > 3.Click on search tab > 4.Now click on Tags Tab > Error:- It would redirect back to Search Tab which is incorrect -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (ATLAS-1806) Error while redirecting it to Tag tab after doing advance search and creating entity
[ https://issues.apache.org/jira/browse/ATLAS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar resolved ATLAS-1806. - Resolution: Fixed > Error while redirecting it to Tag tab after doing advance search and creating > entity > > > Key: ATLAS-1806 > URL: https://issues.apache.org/jira/browse/ATLAS-1806 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Kalyani Kashikar > Attachments: SS11.png > > > Steps to reproduce:- > 1.Do an Advance Search > 2.Then create an entity > 3.Click on search tab > 4.Now click on Tags Tab > Error:- It would redirect back to Search Tab which is incorrect -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1806) Error while redirecting it to Tag tab after doing advance search and creating entity
[ https://issues.apache.org/jira/browse/ATLAS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reassigned ATLAS-1806: --- Assignee: Kalyani Kashikar > Error while redirecting it to Tag tab after doing advance search and creating > entity > > > Key: ATLAS-1806 > URL: https://issues.apache.org/jira/browse/ATLAS-1806 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Kalyani Kashikar > Attachments: SS11.png > > > Steps to reproduce:- > 1.Do an Advance Search > 2.Then create an entity > 3.Click on search tab > 4.Now click on Tags Tab > Error:- It would redirect back to Search Tab which is incorrect -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1817) UI : n+1 pages are created, even though only n*25 instances are retrieved.
[ https://issues.apache.org/jira/browse/ATLAS-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1817: Attachment: ATLAS-1817.patch > UI : n+1 pages are created, even though only n*25 instances are retrieved. > -- > > Key: ATLAS-1817 > URL: https://issues.apache.org/jira/browse/ATLAS-1817 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk, 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Attachments: ATLAS-1817.patch > > > 1.Created 50 tables. > 2.First page showed 1-25 tables , second page 26 -50 tables . > 3.Clicking Next button navigates to 3rd page with 26-50 as range with empty > response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1817) UI : n+1 pages are created, even though only n*25 instances are retrieved.
[ https://issues.apache.org/jira/browse/ATLAS-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reassigned ATLAS-1817: --- Assignee: Kalyani Kashikar > UI : n+1 pages are created, even though only n*25 instances are retrieved. > -- > > Key: ATLAS-1817 > URL: https://issues.apache.org/jira/browse/ATLAS-1817 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk, 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > > 1.Created 50 tables. > 2.First page showed 1-25 tables , second page 26 -50 tables . > 3.Clicking Next button navigates to 3rd page with 26-50 as range with empty > response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1810) UI : Audit details of any tag event (Added,Updated) has only tag name and event.
[ https://issues.apache.org/jira/browse/ATLAS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1810: Attachment: ATLAS-1810.patch > UI : Audit details of any tag event (Added,Updated) has only tag name and > event. > > > Key: ATLAS-1810 > URL: https://issues.apache.org/jira/browse/ATLAS-1810 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar >Priority: Minor > Attachments: ATLAS-1810.patch > > > On clicking Details of Audit events like "Tag Added" , "Tag updated" in Audit > tab , Details window shows only the Audit event and tag name. Tag attributes > are not displayed. Since "Edit Attribute of Tag" feature is introduced, it > would be good to display the attributes of tag like it does for Entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1809) UI : Update button in Edit tag attributes window should be enabled only when any update is done
[ https://issues.apache.org/jira/browse/ATLAS-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1809: Attachment: ATLAS-1809.patch > UI : Update button in Edit tag attributes window should be enabled only when > any update is done > --- > > Key: ATLAS-1809 > URL: https://issues.apache.org/jira/browse/ATLAS-1809 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar >Priority: Minor > Attachments: ATLAS-1809.patch > > > Even though no update is made to any of the attributes of tag associated to > entity, "Update" button is enabled in Edit Tag window . Audit is also > generated with event 'Tag Updated'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1809) UI : Update button in Edit tag attributes window should be enabled only when any update is done
[ https://issues.apache.org/jira/browse/ATLAS-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reassigned ATLAS-1809: --- Assignee: Kalyani Kashikar > UI : Update button in Edit tag attributes window should be enabled only when > any update is done > --- > > Key: ATLAS-1809 > URL: https://issues.apache.org/jira/browse/ATLAS-1809 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar >Priority: Minor > > Even though no update is made to any of the attributes of tag associated to > entity, "Update" button is enabled in Edit Tag window . Audit is also > generated with event 'Tag Updated'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (ATLAS-1152) # Character in Tag is ignored by URL.
[ https://issues.apache.org/jira/browse/ATLAS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar resolved ATLAS-1152. - Resolution: Fixed [~ssainath] In v2 api server is not allowed to create tag using special character, however for searching entity or tag using special character is handled in ATLAS-1813. > # Character in Tag is ignored by URL. > -- > > Key: ATLAS-1152 > URL: https://issues.apache.org/jira/browse/ATLAS-1152 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt > Assignee: Kalyani Kashikar > > Steps to reproduce:- > * Create tag with *#* character in it. > * Search for the same tag. > Because of single page application, uI is not loaded completly due to # > character in browser URL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1813) UI to escape special characters in URL.
[ https://issues.apache.org/jira/browse/ATLAS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1813: Attachment: ATLAS-1813.patch > UI to escape special characters in URL. > --- > > Key: ATLAS-1813 > URL: https://issues.apache.org/jira/browse/ATLAS-1813 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Kalyani Kashikar > Assignee: Kalyani Kashikar > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1813.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1813) UI to escape special characters in URL.
Kalyani Kashikar created ATLAS-1813: --- Summary: UI to escape special characters in URL. Key: ATLAS-1813 URL: https://issues.apache.org/jira/browse/ATLAS-1813 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.8-incubating, 0.9-incubating Reporter: Kalyani Kashikar Assignee: Kalyani Kashikar Fix For: 0.8-incubating, 0.9-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (ATLAS-1759) UI - Add checkbox to exclude/include deleted entities in schema table.
[ https://issues.apache.org/jira/browse/ATLAS-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reopened ATLAS-1759: - > UI - Add checkbox to exclude/include deleted entities in schema table. > -- > > Key: ATLAS-1759 > URL: https://issues.apache.org/jira/browse/ATLAS-1759 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1759.1.patch, ATLAS-1759.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1759) UI - Add checkbox to exclude/include deleted entities in schema table.
[ https://issues.apache.org/jira/browse/ATLAS-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1759: Attachment: ATLAS-1759.1.patch > UI - Add checkbox to exclude/include deleted entities in schema table. > -- > > Key: ATLAS-1759 > URL: https://issues.apache.org/jira/browse/ATLAS-1759 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1759.1.patch, ATLAS-1759.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1771) Atlas UI - While deleting Tag the Confirmation Popup appears incorrectly in IE-9
[ https://issues.apache.org/jira/browse/ATLAS-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1771: Attachment: ATLAS-1771.patch > Atlas UI - While deleting Tag the Confirmation Popup appears incorrectly in > IE-9 > > > Key: ATLAS-1771 > URL: https://issues.apache.org/jira/browse/ATLAS-1771 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating > Environment: Browser - IE-9 >Reporter: Nixon Rodrigues >Assignee: Kalyani Kashikar > Attachments: ATLAS-1771.patch, SS3.jpg > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1777) UI : Include historical entities check box is not shown when searching a type with all DELETED entities, hence no entities are retrieved by search.
[ https://issues.apache.org/jira/browse/ATLAS-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006283#comment-16006283 ] Kalyani Kashikar commented on ATLAS-1777: - This issue is fixed in ATLAS-1776. > UI : Include historical entities check box is not shown when searching a type > with all DELETED entities, hence no entities are retrieved by search. > --- > > Key: ATLAS-1777 > URL: https://issues.apache.org/jira/browse/ATLAS-1777 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Attachments: all_DELETED_entities.png, one_ACTIVE_entity.png > > > 1. Created a type and 10 entities of that type. > 2. Deleted 9 entities out of 10 . > 3. In basic search , searched for the type which listed only one ACTIVE > entity. > 4. Checked the "Include historical entities" check box. It listed the 9 > DELETED entities and 1 ACTIVE entity. (Attached the screenshot) > 5. Now , deleted the last one ACTIVE entity of the type.(all entities of the > type are now DELETED) > 6. Searched for the same type again. Results were empty since > excludeDeletedEntities=True is set by default. > 7. Since there were no results, "Include historical entities" check box is > not shown at all.(Attached the screenshot) . Hence , there is now no way of > retrieving entities of the type in Basic search. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1776) Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification
[ https://issues.apache.org/jira/browse/ATLAS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006281#comment-16006281 ] Kalyani Kashikar commented on ATLAS-1776: - [~nixonrodrigues] Thanks for review. committed to master ( http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/b2bee2cc) committed to 0.8-incubating (http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/9570d3f7) > Include historical entities in UI : A query is made and cancelled every time > the check box is checked/unchecked showing "Invalid expression:null" > notification > -- > > Key: ATLAS-1776 > URL: https://issues.apache.org/jira/browse/ATLAS-1776 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1776.1.patch, ATLAS-1776.2.patch > > > Steps to replicate : > 1.In basic search , searched for type "hive_table". > 2.Checked "Include historical entities" > 3. Unchecked it. At this time the following query is made twice : > http://localhost:21000/api/atlas/v2/search/basic?limit=25=true=table > first of the 2 queries is cancelled and Invalid Expression : null > notification pops up. > Note : This happens only when clicking on the "Include historical entities" > text . On checking / unchecking the check box itself, no such extra queries > are made. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1776) Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification
[ https://issues.apache.org/jira/browse/ATLAS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1776: Attachment: ATLAS-1776.2.patch > Include historical entities in UI : A query is made and cancelled every time > the check box is checked/unchecked showing "Invalid expression:null" > notification > -- > > Key: ATLAS-1776 > URL: https://issues.apache.org/jira/browse/ATLAS-1776 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1776.1.patch, ATLAS-1776.2.patch > > > Steps to replicate : > 1.In basic search , searched for type "hive_table". > 2.Checked "Include historical entities" > 3. Unchecked it. At this time the following query is made twice : > http://localhost:21000/api/atlas/v2/search/basic?limit=25=true=table > first of the 2 queries is cancelled and Invalid Expression : null > notification pops up. > Note : This happens only when clicking on the "Include historical entities" > text . On checking / unchecking the check box itself, no such extra queries > are made. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1776) Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification
[ https://issues.apache.org/jira/browse/ATLAS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1776: Attachment: ATLAS-1776.1.patch > Include historical entities in UI : A query is made and cancelled every time > the check box is checked/unchecked showing "Invalid expression:null" > notification > -- > > Key: ATLAS-1776 > URL: https://issues.apache.org/jira/browse/ATLAS-1776 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1776.1.patch > > > Steps to replicate : > 1.In basic search , searched for type "hive_table". > 2.Checked "Include historical entities" > 3. Unchecked it. At this time the following query is made twice : > http://localhost:21000/api/atlas/v2/search/basic?limit=25=true=table > first of the 2 queries is cancelled and Invalid Expression : null > notification pops up. > Note : This happens only when clicking on the "Include historical entities" > text . On checking / unchecking the check box itself, no such extra queries > are made. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1776) Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification
[ https://issues.apache.org/jira/browse/ATLAS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1776: Attachment: (was: ATLAS-1776.patch) > Include historical entities in UI : A query is made and cancelled every time > the check box is checked/unchecked showing "Invalid expression:null" > notification > -- > > Key: ATLAS-1776 > URL: https://issues.apache.org/jira/browse/ATLAS-1776 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating, 0.9-incubating > > > Steps to replicate : > 1.In basic search , searched for type "hive_table". > 2.Checked "Include historical entities" > 3. Unchecked it. At this time the following query is made twice : > http://localhost:21000/api/atlas/v2/search/basic?limit=25=true=table > first of the 2 queries is cancelled and Invalid Expression : null > notification pops up. > Note : This happens only when clicking on the "Include historical entities" > text . On checking / unchecking the check box itself, no such extra queries > are made. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1777) UI : Include historical entities check box is not shown when searching a type with all DELETED entities, hence no entities are retrieved by search.
[ https://issues.apache.org/jira/browse/ATLAS-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reassigned ATLAS-1777: --- Assignee: Kalyani Kashikar > UI : Include historical entities check box is not shown when searching a type > with all DELETED entities, hence no entities are retrieved by search. > --- > > Key: ATLAS-1777 > URL: https://issues.apache.org/jira/browse/ATLAS-1777 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Attachments: all_DELETED_entities.png, one_ACTIVE_entity.png > > > 1. Created a type and 10 entities of that type. > 2. Deleted 9 entities out of 10 . > 3. In basic search , searched for the type which listed only one ACTIVE > entity. > 4. Checked the "Include historical entities" check box. It listed the 9 > DELETED entities and 1 ACTIVE entity. (Attached the screenshot) > 5. Now , deleted the last one ACTIVE entity of the type.(all entities of the > type are now DELETED) > 6. Searched for the same type again. Results were empty since > excludeDeletedEntities=True is set by default. > 7. Since there were no results, "Include historical entities" check box is > not shown at all.(Attached the screenshot) . Hence , there is now no way of > retrieving entities of the type in Basic search. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1776) Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification
[ https://issues.apache.org/jira/browse/ATLAS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1776: Description: Steps to replicate : 1.In basic search , searched for type "hive_table". 2.Checked "Include historical entities" 3. Unchecked it. At this time the following query is made twice : http://localhost:21000/api/atlas/v2/search/basic?limit=25=true=table first of the 2 queries is cancelled and Invalid Expression : null notification pops up. Note : This happens only when clicking on the "Include historical entities" text . On checking / unchecking the check box itself, no such extra queries are made. > Include historical entities in UI : A query is made and cancelled every time > the check box is checked/unchecked showing "Invalid expression:null" > notification > -- > > Key: ATLAS-1776 > URL: https://issues.apache.org/jira/browse/ATLAS-1776 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Affects Versions: 0.8-incubating, 0.9-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1776.patch > > > Steps to replicate : > 1.In basic search , searched for type "hive_table". > 2.Checked "Include historical entities" > 3. Unchecked it. At this time the following query is made twice : > http://localhost:21000/api/atlas/v2/search/basic?limit=25=true=table > first of the 2 queries is cancelled and Invalid Expression : null > notification pops up. > Note : This happens only when clicking on the "Include historical entities" > text . On checking / unchecking the check box itself, no such extra queries > are made. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1776) Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification
[ https://issues.apache.org/jira/browse/ATLAS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1776: Attachment: ATLAS-1776.patch > Include historical entities in UI : A query is made and cancelled every time > the check box is checked/unchecked showing "Invalid expression:null" > notification > -- > > Key: ATLAS-1776 > URL: https://issues.apache.org/jira/browse/ATLAS-1776 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1776.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1776) Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification
Kalyani Kashikar created ATLAS-1776: --- Summary: Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification Key: ATLAS-1776 URL: https://issues.apache.org/jira/browse/ATLAS-1776 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.8-incubating, 0.9-incubating Reporter: Kalyani Kashikar Assignee: Kalyani Kashikar Fix For: 0.8-incubating, 0.9-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and fulltext search
[ https://issues.apache.org/jira/browse/ATLAS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1755: Fix Version/s: 0.9-incubating > UI - Add checkbox to exclude deleted entities in basic and fulltext search > -- > > Key: ATLAS-1755 > URL: https://issues.apache.org/jira/browse/ATLAS-1755 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Kalyani Kashikar > Assignee: Kalyani Kashikar > Fix For: 0.9-incubating > > Attachments: ATLAS-1755.1.patch, ATLAS-1755.2.patch, ATLAS-1755.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and fulltext search
[ https://issues.apache.org/jira/browse/ATLAS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002188#comment-16002188 ] Kalyani Kashikar commented on ATLAS-1755: - Thanks [~madhan.neethiraj] for review and commit.( http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/c3b1bcb1) > UI - Add checkbox to exclude deleted entities in basic and fulltext search > -- > > Key: ATLAS-1755 > URL: https://issues.apache.org/jira/browse/ATLAS-1755 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Kalyani Kashikar > Assignee: Kalyani Kashikar > Fix For: 0.9-incubating > > Attachments: ATLAS-1755.1.patch, ATLAS-1755.2.patch, ATLAS-1755.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Review Request 58988: ATLAS-1759 : UI - Add checkbox to exclude/include deleted entities in schema table.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58988/ --- Review request for atlas, keval bhatt and Madhan Neethiraj. Bugs: ATLAS-1759 https://issues.apache.org/jira/browse/ATLAS-1759 Repository: atlas Description --- Add checkbox for schema table to exclude/include deleted entities. Diffs - dashboardv2/public/js/templates/schema/SchemaTableLayoutView_tmpl.html c133d1f dashboardv2/public/js/views/schema/SchemaLayoutView.js 75714f0 Diff: https://reviews.apache.org/r/58988/diff/1/ Testing --- Verified added checkbox in schema table to include deleted entities. Thanks, Kalyani Kashikar
[jira] [Updated] (ATLAS-1759) UI - Add checkbox to exclude/include deleted entities in schema table.
[ https://issues.apache.org/jira/browse/ATLAS-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1759: Summary: UI - Add checkbox to exclude/include deleted entities in schema table. (was: UI - Add checkbox to exclude deleted entities in schema table.) > UI - Add checkbox to exclude/include deleted entities in schema table. > -- > > Key: ATLAS-1759 > URL: https://issues.apache.org/jira/browse/ATLAS-1759 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1759.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1759) UI - Add checkbox to exclude deleted entities in schema table.
[ https://issues.apache.org/jira/browse/ATLAS-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1759: Attachment: ATLAS-1759.patch > UI - Add checkbox to exclude deleted entities in schema table. > -- > > Key: ATLAS-1759 > URL: https://issues.apache.org/jira/browse/ATLAS-1759 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1759.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1763) UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS tab
[ https://issues.apache.org/jira/browse/ATLAS-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15994376#comment-15994376 ] Kalyani Kashikar commented on ATLAS-1763: - [~ssainath] If you delete the tag from REST end at that time UI is not aware of tag state. This issue cannot be fixed. user need to refresh browser or click refresh button on tag tab. We notice one issue that is while clicking on refresh button of tag tab if tag which is deleted from REST point and its is active from UI side, then the browser URL should update with first tag if available, will fix this issue in this jira. CC [~madhan.neethiraj] , [~kevalbhatt] > UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS > tab > > > Key: ATLAS-1763 > URL: https://issues.apache.org/jira/browse/ATLAS-1763 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Trivial > > 1. Created tag tag1 > 2. Clicked on TAGS tab which landed in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 > 3. Deleted the tag through REST. > 4. Clicked on the TAGS tab. The TAGS tab listed tag1 . But on disabling cache > , tag1 is removed. > 5.But Atlas lands in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 which throws 404 > exception while clicking Tags tab . > On opening Atlas in another incognito window , this issue is not seen . Atlas > possibly caches tag1 which lands in /tag/tagAttribute/tag1 and causes issue. > When there are 1 or more ACTIVE tags , this issue is not seen as it lands in > /tag/tagAttribute/. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1759) UI - Add checkbox to exclude deleted entities in schema table.
Kalyani Kashikar created ATLAS-1759: --- Summary: UI - Add checkbox to exclude deleted entities in schema table. Key: ATLAS-1759 URL: https://issues.apache.org/jira/browse/ATLAS-1759 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Kalyani Kashikar Assignee: Kalyani Kashikar -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1737) UI - Delete tag(classification) from UI.
[ https://issues.apache.org/jira/browse/ATLAS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15988725#comment-15988725 ] Kalyani Kashikar edited comment on ATLAS-1737 at 4/28/17 12:17 PM: --- [~nixonrodrigues] Thanks for review. ATLAS-1737.3.patch has fix for the above issue. was (Author: kalyanikashikar): [~nixonrodrigues] Thanks for review. ATLAS-1737.3.patch has fix for above issue. > UI - Delete tag(classification) from UI. > > > Key: ATLAS-1737 > URL: https://issues.apache.org/jira/browse/ATLAS-1737 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1737.1.patch, ATLAS-1737.2.patch, > ATLAS-1737.3.patch, Atlas-1737 issue.png, ATLAS-1737.patch > > > Ability to delete tag from UI using API > (api/atlas/v2/types/typedefs?type=classification) DELETE method. > _Tags which are not assigned to any entity can be only deleted._ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1737) UI - Delete tag(classification) from UI.
[ https://issues.apache.org/jira/browse/ATLAS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15988725#comment-15988725 ] Kalyani Kashikar commented on ATLAS-1737: - [~nixonrodrigues] Thanks for review. ATLAS-1737.3.patch has fix for above issue. > UI - Delete tag(classification) from UI. > > > Key: ATLAS-1737 > URL: https://issues.apache.org/jira/browse/ATLAS-1737 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1737.1.patch, ATLAS-1737.2.patch, > ATLAS-1737.3.patch, Atlas-1737 issue.png, ATLAS-1737.patch > > > Ability to delete tag from UI using API > (api/atlas/v2/types/typedefs?type=classification) DELETE method. > _Tags which are not assigned to any entity can be only deleted._ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Review Request 58570: ATLAS-1737 : UI - Delete tag(classification) from UI.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58570/ --- (Updated April 28, 2017, 12:09 p.m.) Review request for atlas, keval bhatt, Madhan Neethiraj, and Mehul Parikh. Changes --- Nixon's review comment handled. Bugs: ATLAS-1737 https://issues.apache.org/jira/browse/ATLAS-1737 Repository: atlas Description --- Ability to delete tag from UI using API (api/atlas/v2/types/typedefs?type=classification) DELETE method. Tags which are not assigned to any entity can be only deleted. Diffs (updated) - dashboardv2/public/js/models/VTag.js 046af3f dashboardv2/public/js/utils/CommonViewFunction.js 1890ce3 dashboardv2/public/js/utils/Utils.js d62a726 dashboardv2/public/js/views/business_catalog/SideNavLayoutView.js 9bd1bbf dashboardv2/public/js/views/tag/TagLayoutView.js d8ee351 Diff: https://reviews.apache.org/r/58570/diff/2/ Changes: https://reviews.apache.org/r/58570/diff/1-2/ Testing --- Verified tags which are not assigned to any entity can be deleted. Verified confirmation alert is displayed before deleting the tag. Thanks, Kalyani Kashikar
[jira] [Updated] (ATLAS-1737) UI - Delete tag(classification) from UI.
[ https://issues.apache.org/jira/browse/ATLAS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1737: Attachment: ATLAS-1737.3.patch > UI - Delete tag(classification) from UI. > > > Key: ATLAS-1737 > URL: https://issues.apache.org/jira/browse/ATLAS-1737 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1737.1.patch, ATLAS-1737.2.patch, > ATLAS-1737.3.patch, Atlas-1737 issue.png, ATLAS-1737.patch > > > Ability to delete tag from UI using API > (api/atlas/v2/types/typedefs?type=classification) DELETE method. > _Tags which are not assigned to any entity can be only deleted._ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Review Request 58839: ATLAS-1755 : UI - Add checkbox to exclude deleted entities in basic and fulltext search
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58839/ --- Review request for atlas, keval bhatt and Madhan Neethiraj. Bugs: ATLAS-1755 https://issues.apache.org/jira/browse/ATLAS-1755 Repository: atlas Description --- Add checkbox for basic search to include deleted entities. Diffs - dashboardv2/public/js/templates/search/SearchResultLayoutView_tmpl.html af984f5 dashboardv2/public/js/views/search/SearchResultLayoutView.js cad4bec Diff: https://reviews.apache.org/r/58839/diff/1/ Testing --- Verified added checkbox for basic search to include deleted entities. Verified checkbox is removed for Advance search to show deleted entities . Thanks, Kalyani Kashikar
[jira] [Commented] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and fulltext search
[ https://issues.apache.org/jira/browse/ATLAS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15988607#comment-15988607 ] Kalyani Kashikar commented on ATLAS-1755: - [~davidrad] Thank for Review. Its done in same way you are referring to, by default only active entities are shown and if user needs to see the all entities with deleted entities, for this user need to check the *Show Deleted Entities* checkbox. As per your suggestion "Include historical entities" make sense because output shown is all entities including deleted ones when checked. > UI - Add checkbox to exclude deleted entities in basic and fulltext search > -- > > Key: ATLAS-1755 > URL: https://issues.apache.org/jira/browse/ATLAS-1755 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1755.1.patch, ATLAS-1755.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and fulltext search
[ https://issues.apache.org/jira/browse/ATLAS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1755: Summary: UI - Add checkbox to exclude deleted entities in basic and fulltext search (was: UI - Add checkbox to exclude deleted entities in basic and Advance search) > UI - Add checkbox to exclude deleted entities in basic and fulltext search > -- > > Key: ATLAS-1755 > URL: https://issues.apache.org/jira/browse/ATLAS-1755 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1755.1.patch, ATLAS-1755.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and Advance search
[ https://issues.apache.org/jira/browse/ATLAS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15988336#comment-15988336 ] Kalyani Kashikar commented on ATLAS-1755: - [~sarath.ku...@gmail.com] As per your comment, checkbox to show deleted entities is removed from advanced search and its applicable for basic search only. > UI - Add checkbox to exclude deleted entities in basic and Advance search > - > > Key: ATLAS-1755 > URL: https://issues.apache.org/jira/browse/ATLAS-1755 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1755.1.patch, ATLAS-1755.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and Advance search
[ https://issues.apache.org/jira/browse/ATLAS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1755: Attachment: ATLAS-1755.1.patch > UI - Add checkbox to exclude deleted entities in basic and Advance search > - > > Key: ATLAS-1755 > URL: https://issues.apache.org/jira/browse/ATLAS-1755 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1755.1.patch, ATLAS-1755.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1737) UI - Delete tag(classification) from UI.
[ https://issues.apache.org/jira/browse/ATLAS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1737: Attachment: ATLAS-1737.2.patch > UI - Delete tag(classification) from UI. > > > Key: ATLAS-1737 > URL: https://issues.apache.org/jira/browse/ATLAS-1737 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1737.1.patch, ATLAS-1737.2.patch, ATLAS-1737.patch > > > Ability to delete tag from UI using API > (api/atlas/v2/types/typedefs?type=classification) DELETE method. > _Tags which are not assigned to any entity can be only deleted._ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and Advance search
[
https://issues.apache.org/jira/browse/ATLAS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15986593#comment-15986593
]
Kalyani Kashikar commented on ATLAS-1755:
-
[~sarath.ku...@gmail.com] In Advance search return deleted entity and active
entity even after passing the *excludeDeletedEntities* query param.
{code}
API :
http://localhost:21000/api/atlas/v2/search/dsl?limit=25=true=hive_columnn
Response: {
"queryType": "DSL",
"queryText": "hive_column ",
"entities": [{
"typeName": "hive_column",
"attributes": {
"owner": null,
"qualifiedName": "test_col",
"name": "test_col",
"description": null
},
"guid": "e5c27034-bc70-4cb8-99cf-d02242e26619",
"status": "DELETED",
"displayText": "test_col",
"classificationNames": []
}, {
"typeName": "hive_column",
"attributes": {
"owner": null,
"qualifiedName": "hive_colC",
"name": "hive_colC",
"description": null
},
"guid": "6dfa18f3-463c-40de-b0aa-e4c3335f8ae5",
"status": "ACTIVE",
"displayText": "hive_colC",
"classificationNames": []
}, {
"typeName": "hive_column",
"attributes": {
"owner": null,
"qualifiedName": "TEST_COLQ",
"name": "TEST_COL",
"description": null
},
"guid": "26b5041a-5b89-4928-a550-60e48ff38a3d",
"status": "ACTIVE",
"displayText": "TEST_COL",
"classificationNames": []
}, {
"typeName": "hive_column",
"attributes": {
"owner": null,
"qualifiedName": "hive_colA",
"name": "hive_colA",
"description": null
},
"guid": "9bb79e0c-c35c-4957-8bc2-09e293d55883",
"status": "DELETED",
"displayText": "hive_colA",
"classificationNames": []
}, {
"typeName": "hive_column",
"attributes": {
"owner": null,
"qualifiedName": "test3_hive_col",
"name": "test3_hive_col",
"description": null
},
"guid": "ef6b71a9-1d87-47df-ac18-f5c9ee5e00c4",
"status": "DELETED",
"displayText": "test3_hive_col",
"classificationNames": []
}, {
"typeName": "hive_column",
"attributes": {
"owner": null,
"qualifiedName": "hive_colB",
"name": "hive_colB",
"description": null
},
"guid": "11951d77-eb85-4621-94ed-14813e474c53",
"status": "DELETED",
"displayText": "hive_colB",
"classificationNames": []
}, {
"typeName": "hive_column",
"attributes": {
"owner": null,
"qualifiedName": "TEST_colA",
"name": "TEST_colA",
"description": null
},
"guid": "90ebcddc-411d-4d06-9a8d-8d4e59c6d4a3",
"status": "ACTIVE",
"displayText": "TEST_colA",
"classificationNames": []
}]
}
{code}
Please check.
> UI - Add checkbox to exclude deleted entities in basic and Advance search
> -
>
> Key: ATLAS-1755
> URL: https://issues.apache.org/jira/browse/ATLAS-1755
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1755.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and Advance search
[ https://issues.apache.org/jira/browse/ATLAS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1755: Summary: UI - Add checkbox to exclude deleted entities in basic and Advance search (was: UI - Add checkbox to exclude deleted entities in basic and fulltext search) > UI - Add checkbox to exclude deleted entities in basic and Advance search > - > > Key: ATLAS-1755 > URL: https://issues.apache.org/jira/browse/ATLAS-1755 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1755.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and fulltext search
[ https://issues.apache.org/jira/browse/ATLAS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1755: Attachment: ATLAS-1755.patch > UI - Add checkbox to exclude deleted entities in basic and fulltext search > -- > > Key: ATLAS-1755 > URL: https://issues.apache.org/jira/browse/ATLAS-1755 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1755.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and fulltext search
Kalyani Kashikar created ATLAS-1755: --- Summary: UI - Add checkbox to exclude deleted entities in basic and fulltext search Key: ATLAS-1755 URL: https://issues.apache.org/jira/browse/ATLAS-1755 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Kalyani Kashikar Assignee: Kalyani Kashikar -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Review Request 58570: ATLAS-1737 : UI - Delete tag(classification) from UI.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58570/ --- Review request for atlas, keval bhatt, Madhan Neethiraj, and Mehul Parikh. Bugs: ATLAS-1737 https://issues.apache.org/jira/browse/ATLAS-1737 Repository: atlas Description --- Ability to delete tag from UI using API (api/atlas/v2/types/typedefs?type=classification) DELETE method. Tags which are not assigned to any entity can be only deleted. Diffs - dashboardv2/public/js/models/VTag.js 046af3f dashboardv2/public/js/utils/CommonViewFunction.js 1890ce3 dashboardv2/public/js/utils/Utils.js d62a726 dashboardv2/public/js/views/tag/TagLayoutView.js d8ee351 Diff: https://reviews.apache.org/r/58570/diff/1/ Testing --- Verified tags which are not assigned to any entity can be deleted. Verified confirmation alert is displayed before deleting the tag. Thanks, Kalyani Kashikar
[jira] [Updated] (ATLAS-1737) UI - Delete tag(classification) from UI.
[ https://issues.apache.org/jira/browse/ATLAS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1737: Attachment: ATLAS-1737.1.patch > UI - Delete tag(classification) from UI. > > > Key: ATLAS-1737 > URL: https://issues.apache.org/jira/browse/ATLAS-1737 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1737.1.patch, ATLAS-1737.patch > > > Ability to delete tag from UI using API > (api/atlas/v2/types/typedefs?type=classification) DELETE method. > _Tags which are not assigned to any entity can be only deleted._ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1737) UI - Delete tag(classification) from UI.
[ https://issues.apache.org/jira/browse/ATLAS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1737: Attachment: ATLAS-1737.patch > UI - Delete tag(classification) from UI. > > > Key: ATLAS-1737 > URL: https://issues.apache.org/jira/browse/ATLAS-1737 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1737.patch > > > Ability to delete tag from UI using API > (api/atlas/v2/types/typedefs?type=classification) DELETE method. > _Tags which are not assigned to any entity can be only deleted._ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1737) UI - Delete tag(classification) from UI.
Kalyani Kashikar created ATLAS-1737: --- Summary: UI - Delete tag(classification) from UI. Key: ATLAS-1737 URL: https://issues.apache.org/jira/browse/ATLAS-1737 Project: Atlas Issue Type: Improvement Components: atlas-webui Reporter: Kalyani Kashikar Assignee: Kalyani Kashikar Ability to delete tag from UI using API (api/atlas/v2/types/typedefs?type=classification) DELETE method. _Tags which are not assigned to any entity can be only deleted._ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Review Request 58340: ATLAS-1718 : In Create tag UI, attribute datatype should provide enum-types in drop-down along with built-in types
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58340/ --- (Updated April 12, 2017, 1:45 p.m.) Review request for atlas, keval bhatt and Madhan Neethiraj. Changes --- Displayed the loader when popup initialize and hide loader after ENUM API complete. Bugs: ATLAS-1718 https://issues.apache.org/jira/browse/ATLAS-1718 Repository: atlas Description --- In Create/update tag UI, attribute datatype should provide enum-types in drop-down along with built-in types. ( like hive_principal_type, file_action). Diffs (updated) - dashboardv2/public/js/templates/tag/AddTagAttributeView_tmpl.html f6e1aac dashboardv2/public/js/templates/tag/createTagLayoutView_tmpl.html 256209b dashboardv2/public/js/views/tag/AddTagAttributeView.js 3108279 dashboardv2/public/js/views/tag/CreateTagLayoutView.js 34fa114 dashboardv2/public/js/views/tag/TagAttributeItemView.js 2482543 Diff: https://reviews.apache.org/r/58340/diff/2/ Changes: https://reviews.apache.org/r/58340/diff/1-2/ Testing --- Verified when creating the tag, attribute datatype drop-down contains the enum type. Thanks, Kalyani Kashikar
[jira] [Commented] (ATLAS-1718) In Create tag UI, attribute datatype should provide enum-types in drop-down along with built-in types
[ https://issues.apache.org/jira/browse/ATLAS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965876#comment-15965876 ] Kalyani Kashikar commented on ATLAS-1718: - [~kevalbhatt] ATLAS-1718.1.patch addresses the review comment. > In Create tag UI, attribute datatype should provide enum-types in drop-down > along with built-in types > - > > Key: ATLAS-1718 > URL: https://issues.apache.org/jira/browse/ATLAS-1718 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating > Reporter: Kalyani Kashikar > Assignee: Kalyani Kashikar > Fix For: 0.9-incubating > > Attachments: ATLAS-1718.1.patch, ATLAS-1718.patch > > > In Create/update tag UI, attribute datatype should provide enum-types in > drop-down along with built-in types. ( like hive_principal_type, file_action) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1719) Tag association UI should allow users to input value for enum type attributes from a drop-down
[
https://issues.apache.org/jira/browse/ATLAS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965862#comment-15965862
]
Kalyani Kashikar commented on ATLAS-1719:
-
This patch is dependent on ATLAS-1718.
> Tag association UI should allow users to input value for enum type
> attributes from a drop-down
> ---
>
> Key: ATLAS-1719
> URL: https://issues.apache.org/jira/browse/ATLAS-1719
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
> Reporter: Kalyani Kashikar
> Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1719.1.patch, ATLAS-1719.patch
>
>
> Tag association UI should allow users to input value for enum type attributes
> from a drop-down.
> Ex. For hive_principal_type enum type drop-down should shown { USER, ROLE,
> GROUP }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1718) In Create tag UI, attribute datatype should provide enum-types in drop-down along with built-in types
[ https://issues.apache.org/jira/browse/ATLAS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1718: Attachment: ATLAS-1718.1.patch > In Create tag UI, attribute datatype should provide enum-types in drop-down > along with built-in types > - > > Key: ATLAS-1718 > URL: https://issues.apache.org/jira/browse/ATLAS-1718 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating > Reporter: Kalyani Kashikar > Assignee: Kalyani Kashikar > Fix For: 0.9-incubating > > Attachments: ATLAS-1718.1.patch, ATLAS-1718.patch > > > In Create/update tag UI, attribute datatype should provide enum-types in > drop-down along with built-in types. ( like hive_principal_type, file_action) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Review Request 58336: ATLAS-1433: Atlas allows creation of tag with attributes' name same as that of its parent tags.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58336/ --- (Updated April 11, 2017, 1:30 p.m.) Review request for atlas, keval bhatt and Madhan Neethiraj. Changes --- Removed commomViewFunction.js file from patch. Bugs: ATLAS-1433 https://issues.apache.org/jira/browse/ATLAS-1433 Repository: atlas Description --- Patch contains following features: * While adding attributes to the tag, duplicate attributes has been restricted, and its prompted accordingly. * If tag contain supertype, it displays on detail page under 'Derived From:' label. If superType is empty, label gets hidden. Diffs (updated) - dashboardv2/public/css/scss/graph.scss feb9c10 dashboardv2/public/css/scss/tag.scss 6c2d29a dashboardv2/public/js/models/VTag.js 51b53d1 dashboardv2/public/js/templates/tag/TagAttributeDetailLayoutView_tmpl.html 2cb0fc9 dashboardv2/public/js/views/tag/TagAttributeDetailLayoutView.js ecf32f2 dashboardv2/public/js/views/tag/TagLayoutView.js 8591100 Diff: https://reviews.apache.org/r/58336/diff/2/ Changes: https://reviews.apache.org/r/58336/diff/1-2/ Testing --- Test following scenarios: * Verified while adding attributes to the tag, duplicate attributes are restricted. * Verified when adding the attribute to the tag and if its already present in the parent tag then attributes are restricted. * Verified when tag contain supertype, it displayed on detail page under 'Derived From:' label. If superType is empty, label gets hidden. Thanks, Kalyani Kashikar
Review Request 58343: ATLAS-1719 : Tag association UI should allow users to input value for enum type attributes from a drop-down.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58343/
---
Review request for atlas, keval bhatt and Madhan Neethiraj.
Bugs: ATLAS-1719
https://issues.apache.org/jira/browse/ATLAS-1719
Repository: atlas
Description
---
Tag association UI should allow users to input value for enum type attributes
from a drop-down.
Ex. For hive_principal_type enum type drop-down should shown
{ USER, ROLE, GROUP }
Diffs
-
dashboardv2/public/js/templates/tag/addTagModalView_tmpl.html 3b6b429
dashboardv2/public/js/views/tag/addTagModalView.js 8beec4b
Diff: https://reviews.apache.org/r/58343/diff/1/
Testing
---
Verified while Tag associating to entity, UI should allow users to input value
for enum type attributes from a drop-down.
Thanks,
Kalyani Kashikar
[jira] [Updated] (ATLAS-1719) Tag association UI should allow users to input value for enum type attributes from a drop-down
[
https://issues.apache.org/jira/browse/ATLAS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kalyani Kashikar updated ATLAS-1719:
Attachment: ATLAS-1719.1.patch
> Tag association UI should allow users to input value for enum type
> attributes from a drop-down
> ---
>
> Key: ATLAS-1719
> URL: https://issues.apache.org/jira/browse/ATLAS-1719
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
> Reporter: Kalyani Kashikar
> Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1719.1.patch, ATLAS-1719.patch
>
>
> Tag association UI should allow users to input value for enum type attributes
> from a drop-down.
> Ex. For hive_principal_type enum type drop-down should shown { USER, ROLE,
> GROUP }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Review Request 58340: ATLAS-1718 : In Create tag UI, attribute datatype should provide enum-types in drop-down along with built-in types
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58340/ --- Review request for atlas, keval bhatt and Madhan Neethiraj. Bugs: ATLAS-1718 https://issues.apache.org/jira/browse/ATLAS-1718 Repository: atlas Description --- In Create/update tag UI, attribute datatype should provide enum-types in drop-down along with built-in types. ( like hive_principal_type, file_action). Diffs - dashboardv2/public/js/views/tag/TagAttributeItemView.js 2482543 Diff: https://reviews.apache.org/r/58340/diff/1/ Testing --- Verified when creating the tag, attribute datatype drop-down contains the enum type. Thanks, Kalyani Kashikar
Review Request 58336: ATLAS-1433: Atlas allows creation of tag with attributes' name same as that of its parent tags.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58336/ --- Review request for atlas, keval bhatt and Madhan Neethiraj. Bugs: ATLAS-1433 https://issues.apache.org/jira/browse/ATLAS-1433 Repository: atlas Description --- Patch contains following features: * While adding attributes to the tag, duplicate attributes has been restricted, and its prompted accordingly. * If tag contain supertype, it displays on detail page under 'Derived From:' label. If superType is empty, label gets hidden. Diffs - dashboardv2/public/css/scss/tag.scss 6c2d29a dashboardv2/public/js/models/VTag.js 51b53d1 dashboardv2/public/js/templates/tag/TagAttributeDetailLayoutView_tmpl.html 2cb0fc9 dashboardv2/public/js/utils/CommonViewFunction.js 615bef4 dashboardv2/public/js/views/tag/TagAttributeDetailLayoutView.js ecf32f2 dashboardv2/public/js/views/tag/TagLayoutView.js 8591100 Diff: https://reviews.apache.org/r/58336/diff/1/ Testing --- Test following scenarios: * Verified while adding attributes to the tag, duplicate attributes are restricted. * Verified when adding the attribute to the tag and if its already present in the parent tag then attributes are restricted. * Verified when tag contain supertype, it displayed on detail page under 'Derived From:' label. If superType is empty, label gets hidden. Thanks, Kalyani Kashikar
[jira] [Updated] (ATLAS-1719) Tag association UI should allow users to input value for enum type attributes from a drop-down
[
https://issues.apache.org/jira/browse/ATLAS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kalyani Kashikar updated ATLAS-1719:
Attachment: ATLAS-1719.patch
> Tag association UI should allow users to input value for enum type
> attributes from a drop-down
> ---
>
> Key: ATLAS-1719
> URL: https://issues.apache.org/jira/browse/ATLAS-1719
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
> Reporter: Kalyani Kashikar
> Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1719.patch
>
>
> Tag association UI should allow users to input value for enum type attributes
> from a drop-down.
> Ex. For hive_principal_type enum type drop-down should shown { USER, ROLE,
> GROUP }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1718) In Create tag UI, attribute datatype should provide enum-types in drop-down along with built-in types
[ https://issues.apache.org/jira/browse/ATLAS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1718: Attachment: ATLAS-1718.patch > In Create tag UI, attribute datatype should provide enum-types in drop-down > along with built-in types > - > > Key: ATLAS-1718 > URL: https://issues.apache.org/jira/browse/ATLAS-1718 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating > Reporter: Kalyani Kashikar > Assignee: Kalyani Kashikar > Fix For: 0.9-incubating > > Attachments: ATLAS-1718.patch > > > In Create/update tag UI, attribute datatype should provide enum-types in > drop-down along with built-in types. ( like hive_principal_type, file_action) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1433) Atlas allows creation of tag with attributes' name same as that of its parent tags.
[ https://issues.apache.org/jira/browse/ATLAS-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1433: Attachment: ATLAS-1433.patch > Atlas allows creation of tag with attributes' name same as that of its parent > tags. > --- > > Key: ATLAS-1433 > URL: https://issues.apache.org/jira/browse/ATLAS-1433 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Attachments: ATLAS-1433.patch > > > Created a tag parent_tag with attributes name and id. Created an other tag > child_tag inheriting from parent_tag . And gave attribute names for > child_tag same as that of parent_tag. child_tag is successfully created. > Associated child_tag to an entity. Atlas UI prompts values for 4 attributes > as : > name : > id: > name: > id: > Values provided for last set of name ,id are finally assigned to the tag > associated for the entity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1719) Tag association UI should allow users to input value for enum type attributes from a drop-down
Kalyani Kashikar created ATLAS-1719:
---
Summary: Tag association UI should allow users to input value for
enum type attributes from a drop-down
Key: ATLAS-1719
URL: https://issues.apache.org/jira/browse/ATLAS-1719
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Kalyani Kashikar
Assignee: Kalyani Kashikar
Fix For: 0.9-incubating
Tag association UI should allow users to input value for enum type attributes
from a drop-down.
Ex. For hive_principal_type enum type drop-down should shown { USER, ROLE,
GROUP }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1718) In Create tag UI, attribute datatype should provide enum-types in drop-down along with built-in types
Kalyani Kashikar created ATLAS-1718: --- Summary: In Create tag UI, attribute datatype should provide enum-types in drop-down along with built-in types Key: ATLAS-1718 URL: https://issues.apache.org/jira/browse/ATLAS-1718 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating Reporter: Kalyani Kashikar Assignee: Kalyani Kashikar Fix For: 0.9-incubating In Create/update tag UI, attribute datatype should provide enum-types in drop-down along with built-in types. ( like hive_principal_type, file_action) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1433) Atlas allows creation of tag with attributes' name same as that of its parent tags.
[ https://issues.apache.org/jira/browse/ATLAS-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reassigned ATLAS-1433: --- Assignee: Kalyani Kashikar > Atlas allows creation of tag with attributes' name same as that of its parent > tags. > --- > > Key: ATLAS-1433 > URL: https://issues.apache.org/jira/browse/ATLAS-1433 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > > Created a tag parent_tag with attributes name and id. Created an other tag > child_tag inheriting from parent_tag . And gave attribute names for > child_tag same as that of parent_tag. child_tag is successfully created. > Associated child_tag to an entity. Atlas UI prompts values for 4 attributes > as : > name : > id: > name: > id: > Values provided for last set of name ,id are finally assigned to the tag > associated for the entity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1674) Create Entity via UI : Values are not getting set while updating node attribute of storm_topology entity.
Kalyani Kashikar created ATLAS-1674: --- Summary: Create Entity via UI : Values are not getting set while updating node attribute of storm_topology entity. Key: ATLAS-1674 URL: https://issues.apache.org/jira/browse/ATLAS-1674 Project: Atlas Issue Type: Bug Affects Versions: 0.9-incubating Reporter: Kalyani Kashikar Assignee: Keval Bhatt Fix For: 0.9-incubating Steps to reproduces : # Click on create entity button . # Select storm_topology from list of entities # Add all required values and click on create button. # Go to that newly created entity and click on update button. # Node values are not getting set. If User clicks on update entity button of popup all nodes will be removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: New committer to Apache Atlas: Apoorv Naik
Congratulations Apoorv On Fri, Mar 17, 2017 at 11:25 AM, Vimal Sharma <visha...@hortonworks.com> wrote: > Congrats Apoorv! > > -Vimal > > > > > On 3/17/17, 12:07 AM, "Ayub Khan Pathan" <apat...@hortonworks.com> wrote: > > >Congratulations, Apoorv! > > > >On 3/16/17, 11:29 PM, "Suma Shivaprasad" <sumasai.shivapra...@gmail.com> > wrote: > > > >Congrats, Apoorv! > > > >On Wed, Mar 15, 2017 at 11:37 PM, Keval Bhatt <kevalbhat...@gmail.com > > > >wrote: > > > >> Congratulation, Apoorv! > >> > >> On Wed, Mar 15, 2017 at 11:23 AM, Apoorv Naik < > an...@hortonworks.com> > >> wrote: > >> > >> > Thanks Hemanth. I’m very happy and proud to be a part of the > Apache Atlas > >> > community. Looking forward to grow and help the community. > >> > > >> > > >> > > >> > > >> > On 3/14/17, 9:47 PM, "Hemanth Yamijala" <yhema...@apache.org> > wrote: > >> > > >> > >Atlas dev community, > >> > > > >> > >The Project Management Committee (PMC) for Apache Atlas > >> > >has invited Apoorv Naik to become a committer and we are pleased > >> > >to announce that he has accepted. > >> > > > >> > >Congratulations, Apoorv! > >> > > > >> > >thanks, > >> > >Hemanth > >> > > > >> > > >> > >> > >> > >> -- > >> > >> *From:* > >> > >> *Keval P. Bhatt* > >> > >> *Mumbai* > >> > > > > > -- *Thanks and Regards,* *Kalyani Kashikar*
Re: New PPMC member to Apache Atlas: Madhan Neethiraj
Congratulations Madhan !!! On Fri, Mar 17, 2017 at 11:08 AM, Sharmadha Sainath < ssain...@hortonworks.com> wrote: > > Congrats Madhan !! :) > > > > On 3/17/17, 11:07 AM, "Apoorv Naik" <an...@hortonworks.com> wrote: > > >Congratulations Madhan!!! > > > >Sent from Nine<http://www.9folders.com/> > > > >From: Nixon Rodrigues <nixon.rodrig...@freestoneinfotech.com> > >Sent: Mar 16, 2017 10:07 PM > >To: dev@atlas.incubator.apache.org > >Subject: Re: New PPMC member to Apache Atlas: Madhan Neethiraj > > > >Congratulations Madhan!, Thanks for all your hard work and guidance to > take > >Atlas to new orbit. > > > >Best wishes, > >Nixon > > > > > >On Fri, Mar 17, 2017 at 9:27 AM, Hemanth Yamijala <yhema...@apache.org> > >wrote: > > > >> Atlas dev community, > >> > >> Atlas PPMC has invited Madhan Neethiraj to join us as a PPMC member > >> and we are glad that he has accepted. > >> > >> Congratulations, Madhan! Thanks for all your hard work on Atlas. > >> > >> Hemanth > >> > -- *Thanks and Regards,* *Kalyani Kashikar*
Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release candidate 1 (dev group vote)
+1(non binding) for the 0.8-incubating release - Verified Build, It was successful with source code from tar. - Ran Quick Start. - Verified basic functionality of Tag, Entities, Search etc - UI is loading fine in Chrome,Firefox browsers. Thanks Kalyani On Thu, Mar 9, 2017 at 1:28 PM, Hemanth Yamijala <hyamij...@hortonworks.com> wrote: > Hi Vimal, > > Your vote should be binding. > > Thanks > Hemanth > > From: Vimal Sharma <visha...@hortonworks.com> > Sent: Thursday, March 09, 2017 1:26 PM > To: dev@atlas.incubator.apache.org > Subject: Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release > candidate 1 (dev group vote) > > +1(non binding) for the release > > - Verified checksum and signature > - Build successful and all tests are passing (One IT in webapp failed but > succeeded in rerun) > - Built with external Hbase and Solr > - Verified basic functionality using QuickStart > > > Thanks > Vimal > > > > > On 3/9/17, 11:53 AM, "Sarath Kumar Subramanian" < > sarath.hortonwo...@gmail.com> wrote: > > > - Verified md5 checksum and signature. > > - No binaries in source > > - Build successful with embedded hbase-solr > > - Verified Quickstart, lineage, tags and search > > - Basic Sanity test > > > >+1 (non-binding) for the release. > > > > > >Thanks, > >Sarath Subramanian > > > > > >On Wed, Mar 8, 2017 at 9:10 PM, Ayub Khan Pathan <apat...@hortonworks.com > > > >wrote: > > > >> +1 (non-binding vote) for the release. > >> > >> - Verified “incubating” tag existence > >> - Verified for successful build > >> - Sanity tests are successful. > >> > >> Thanks > >> Ayub Khan > >> > >> On 3/8/17, 1:30 PM, "Madhan Neethiraj" <mad...@apache.org> wrote: > >> > >> Atlas team, > >> > >> > >> > >> Apache Atlas 0.8 (incubating) release candidate #1 is now available > >> for a vote within dev community. Links to the release artifacts are > given > >> below. Can you please review and vote? > >> > >> > >> > >> This update includes fix for the following JIRAS: ATLAS-1648, > >> ATLAS-1655, ATLAS-1656, ATLAS-1657, ATLAS-1658 > >> > >> > >> > >> The vote will be open for at least 72 hours or until necessary votes > >> are reached. > >> > >> [ ] +1 approve > >> > >> [ ] +0 no opinion > >> > >> [ ] -1 disapprove (and reason why) > >> > >> > >> > >> Here is my +1 > >> > >> > >> > >> Thanks, > >> > >> Madhan > >> > >> > >> > >> > >> > >> List of improvements and issues addressed in this release: > >> https://issues.apache.org/jira/issues/?jql=project%20% > >> 3D%20Atlas%20AND%20status%20%3D%20Resolved%20AND% > >> 20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200. > >> 8-incubating%20ORDER%20BY%20key%20DESC > >> > >> > >> > >> Git tag for the release: https://github.com/apache/ > >> incubator-atlas/tree/release-0.8-rc1 > >> > >> > >> > >> Sources for the release: https://dist.apache.org/repos/ > >> dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0. > >> 8-incubating-sources.tar.gz > >> > >> > >> > >> Source release verification: > >> > >> PGP Signature: https://dist.apache.org/repos/ > >> dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0. > >> 8-incubating-sources.tar.gz.asc > >> > >> MD5 Hash: https://dist.apache.org/repos/ > >> dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0. > >> 8-incubating-sources.tar.gz.md5 > >> > >> > >> > >> Keys to verify the signature of the release artifacts are available > >> at: https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > -- *Thanks and Regards,* *Kalyani Kashikar*
[jira] [Updated] (ATLAS-1595) Create Entity in UI : All attributes are not listed for hdfs_path.
[ https://issues.apache.org/jira/browse/ATLAS-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1595: Attachment: ATLAS-1595.patch > Create Entity in UI : All attributes are not listed for hdfs_path. > -- > > Key: ATLAS-1595 > URL: https://issues.apache.org/jira/browse/ATLAS-1595 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1595.patch, fieldset Not displayed.png > > > 1.Clicked "Create Entity" button. > 2.Toggled to "All" from required. > 3. Selected the type "hdfs_path" > 4. Attributes ClusterName,NumberOfReplicas, ExtendedAttributes which come > under fieldset "hdfs_path" are not displayed. Tried to scroll down but it is > the end of scroll. > This doesn't happen when type is first selected and then toggled to "All". > Attached the screenshot when toggled to "All" first and type "hdfs_path" is > selected next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1605) Edit Entity in UI : Update button is not enabled when updating attribute of type date
[ https://issues.apache.org/jira/browse/ATLAS-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1605: Attachment: ATLAS-1605.patch > Edit Entity in UI : Update button is not enabled when updating attribute of > type date > - > > Key: ATLAS-1605 > URL: https://issues.apache.org/jira/browse/ATLAS-1605 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath > Assignee: Kalyani Kashikar > Attachments: ATLAS-1605.patch > > > On editing attributes of hdfs_path like CreateTime , ModifiedTime which are > of type date , Update button is not enabled. This happens for all entity > types which have attributes of type date. Editing other types enables the > Update button. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1488) Create Entity in UI : FileSize attribute of hdfs_path and fs_path is long. Opens a calendar when clicked.(UI bug)
[ https://issues.apache.org/jira/browse/ATLAS-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reassigned ATLAS-1488: --- Assignee: Keval Bhatt (was: Kalyani Kashikar) > Create Entity in UI : FileSize attribute of hdfs_path and fs_path is long. > Opens a calendar when clicked.(UI bug) > - > > Key: ATLAS-1488 > URL: https://issues.apache.org/jira/browse/ATLAS-1488 > Project: Atlas > Issue Type: Bug >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Minor > > hdfs_path and fs_path have FileSize (long type) as one of its attributes . > Clicking on the field when creating /editing hdfs_path/fs_path , opens up a > calendar. Providing a long number (valid input) or date for the same field , > it is always updated as 0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1487) Create Entity in UI : types list doesn't list fs_permissions (struct type) hence no entity could be created for it.
[ https://issues.apache.org/jira/browse/ATLAS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reassigned ATLAS-1487: --- Assignee: Keval Bhatt (was: Kalyani Kashikar) > Create Entity in UI : types list doesn't list fs_permissions (struct type) > hence no entity could be created for it. > --- > > Key: ATLAS-1487 > URL: https://issues.apache.org/jira/browse/ATLAS-1487 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Minor > > hdfs_path and fs_path have PosixPermissions as one of the (optional) > attributes which is of type fs_permissions (struct) . When creating entity > in UI , the types list (/api/atlas/v2/types/entitydef) doesn't return > fs_permissions hence no entity could be created for it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1492) Create Entity in UI : Inputs and Outputs field of types takes forever to list the entities (UI issue)
[
https://issues.apache.org/jira/browse/ATLAS-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kalyani Kashikar reassigned ATLAS-1492:
---
Assignee: Keval Bhatt (was: Kalyani Kashikar)
> Create Entity in UI : Inputs and Outputs field of types takes forever to list
> the entities (UI issue)
> -
>
> Key: ATLAS-1492
> URL: https://issues.apache.org/jira/browse/ATLAS-1492
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
>
> Types with Process as supertype have Inputs and Outputs field which are of
> type array . DSL Query :
> {code}
> /api/atlas/discovery/search/dsl?query=DataSet
> {code}
> returns response soon . But in the Edit Entity window, Inputs and Outputs
> doesn't return the entities in the drop down list box.
> Example :
> In my cluster setup , the above DSL query returned 100 results in less than 3
> seconds but the UI doesn't list down the entities.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Review Request 56119: ATLAS-1502 : UI to create/update entities - configuration to restrict entity-types editable via UI
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56119/ --- Review request for atlas, keval bhatt and Madhan Neethiraj. Bugs: ATLAS-1485 and ATLAS-1502 https://issues.apache.org/jira/browse/ATLAS-1485 https://issues.apache.org/jira/browse/ATLAS-1502 Repository: atlas Description --- This patch includes changes to configure list of entity type via configuration in atlas-application properties atlas.ui.edit.supported.entity-types="type-1,type-2,type3" * If the configuration is set to an empty value (or not set): UI should not support create/edit of any entity * If the configuration is set to is set to '*', then UI should allow create/edit of any type of entity Patch also includes - * Change the create entity button place (ATLAS-1485) * After creating new entity redirect to detail page of that newly created entity (ATLAS-1485) Handled following bugs in patch :- * FileSize attribute of hdfs_path and fs_path is long and its opens a calendar when clicked. * DSL query "array" made when creating/editing an hive_table in UI * Message changed From "entities selected have already been associated with tag testTag, Do you want to associate the tag with other entities?" To "1 of 2 entities selected have already been associated with testTag tag, Do you want to associate the tag with other entities ?" Diffs - dashboardv2/public/css/scss/tag.scss 1f9561d dashboardv2/public/js/main.js 2ddf1aa dashboardv2/public/js/router/Router.js fa4a08a dashboardv2/public/js/templates/detail_page/DetailPageLayoutView_tmpl.html 1de3608 dashboardv2/public/js/templates/search/SearchLayoutView_tmpl.html 7301ebc dashboardv2/public/js/templates/search/SearchResultLayoutView_tmpl.html 32a0083 dashboardv2/public/js/utils/Overrides.js d6d9b6c dashboardv2/public/js/views/audit/AuditTableLayoutView.js dd4adda dashboardv2/public/js/views/audit/CreateAuditTableLayoutView.js 2b43b59 dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js c959229 dashboardv2/public/js/views/entity/CreateEntityLayoutView.js 9f4e1d7 dashboardv2/public/js/views/search/SearchDetailLayoutView.js 0ed1c38 dashboardv2/public/js/views/search/SearchLayoutView.js bdb71a6 dashboardv2/public/js/views/search/SearchResultLayoutView.js cbfe08e dashboardv2/public/js/views/tag/addTagModalView.js 7317a95 webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 54c46a8 Diff: https://reviews.apache.org/r/56119/diff/ Testing --- Verified following scenario for ATLAS-1502: * If the configuration is set to an empty value (or not set): UI should not support create/edit of any entity * If the configuration is set to is set to "*", then UI should allow create/edit of any type of entity. * If the configuration is set to is set to "type-1,type-2,type3", then UI should allow create/edit for "type-1,type-2,type3". Verified following scenario for ATLAS-1485: * Verified the create entity link. * After entity creation, it redirects to entity detail page of that newly created entity. Also Verified following scenario:- * Validation for long data-type for create/edit entity. * Unwated api call for "array" has been handled. Thanks, Kalyani Kashikar
[jira] [Assigned] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI
[
https://issues.apache.org/jira/browse/ATLAS-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kalyani Kashikar reassigned ATLAS-1502:
---
Assignee: Kalyani Kashikar
> UI to create/update entities - configuration to restrict entity-types
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
> Assignee: Kalyani Kashikar
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI
> allows an user to create entity of any entity-type - including the superTypes
> like Referenceable, Asset, Process, etc. It may not be useful to support
> entity creation of many such entity-types via UI. Restricting the UI to
> support only a subset of entities would make the UI more usable and avoid
> potential confusion.
> It should be possible to configure the list of entity-types supported via a
> configuration, to enable deployments to satisfy specific needs. I would
> suggest to use a configuration like:
> {code}
> atlas.ui.edit.supported.entity-types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow
> create/edit of any type of entity
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1437) UI to support v2 api changes to show deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837789#comment-15837789 ] Kalyani Kashikar commented on ATLAS-1437: - This issue handle in ATLAS-1482. > UI to support v2 api changes to show deleted entities. > -- > > Key: ATLAS-1437 > URL: https://issues.apache.org/jira/browse/ATLAS-1437 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1437.3.patch, ATLAS-1437.4.patch > > > Based on v2 api response UI will should show deleted entities. > Not allowed to add Tag to deleted entity when multiple entities are selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 55880: ATLAS-1485 : Create entity UX changes
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55880/ --- Review request for atlas, keval bhatt and Madhan Neethiraj. Bugs: ATLAS-1485 https://issues.apache.org/jira/browse/ATLAS-1485 Repository: atlas Description --- Change the create entity button place After creating new entity redirect to detail page of that newly created entity Diffs - dashboardv2/public/js/router/Router.js fa4a08a dashboardv2/public/js/templates/search/SearchLayoutView_tmpl.html 7301ebc dashboardv2/public/js/templates/search/SearchResultLayoutView_tmpl.html 32a0083 dashboardv2/public/js/views/audit/CreateAuditTableLayoutView.js 2b43b59 dashboardv2/public/js/views/entity/CreateEntityLayoutView.js c98ea18 dashboardv2/public/js/views/schema/SchemaLayoutView.js 8d7dfe4 dashboardv2/public/js/views/search/SearchDetailLayoutView.js 0ed1c38 dashboardv2/public/js/views/search/SearchLayoutView.js bdb71a6 dashboardv2/public/js/views/search/SearchResultLayoutView.js 8d0720e Diff: https://reviews.apache.org/r/55880/diff/ Testing --- Verified the create entity link. After entity creation, it redirects to entity detail page of that newly created entity. Thanks, Kalyani Kashikar
[jira] [Commented] (ATLAS-1437) UI to support v2 api changes to show deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834651#comment-15834651 ] Kalyani Kashikar commented on ATLAS-1437: - ATLAS-1437.4.patch is updated patch. The full-text search results page does not show deleted status because in full-text search uses v2 api and for DSL search uses v1 api. To fix the full text search results page issue, for now using the v1 api. In ATLAS-1425 Jira both the search type results will be ported to V2 api. > UI to support v2 api changes to show deleted entities. > -- > > Key: ATLAS-1437 > URL: https://issues.apache.org/jira/browse/ATLAS-1437 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1437.3.patch, ATLAS-1437.4.patch > > > Based on v2 api response UI will should show deleted entities. > Not allowed to add Tag to deleted entity when multiple entities are selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 55497: ATLAS-1437 : UI to support v2 api changes to show deleted entities
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55497/ --- (Updated Jan. 23, 2017, 2:20 p.m.) Review request for atlas, keval bhatt and Madhan Neethiraj. Changes --- The full-text search results page does not show deleted status because in full-text v2 api is used and for DSL search v1 api is used. To fix full text search results page issue for now, using the v1 api. In ATLAS-1425 Jira both the search type results will be ported to V2 api. Bugs: ATLAS-1437 https://issues.apache.org/jira/browse/ATLAS-1437 Repository: atlas Description --- This patch consist changes for showing deleted entities based on v2 api response. Diffs (updated) - dashboardv2/public/js/utils/Messages.js d6acc32 dashboardv2/public/js/views/search/SearchResultLayoutView.js 8d0720e dashboardv2/public/js/views/tag/addTagModalView.js 9c82d5c Diff: https://reviews.apache.org/r/55497/diff/ Testing --- Following scenarios are tested: * Deleted entites shows in entity detail page. * Assign restriction to add tag on deleted entity. Thanks, Kalyani Kashikar
[jira] [Updated] (ATLAS-1437) UI to support v2 api changes to show deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1437: Attachment: (was: ATLAS-1437.4.patch) > UI to support v2 api changes to show deleted entities. > -- > > Key: ATLAS-1437 > URL: https://issues.apache.org/jira/browse/ATLAS-1437 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1437.3.patch, ATLAS-1437.4.patch > > > Based on v2 api response UI will should show deleted entities. > Not allowed to add Tag to deleted entity when multiple entities are selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1437) UI to support v2 api changes to show deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1437: Attachment: ATLAS-1437.4.patch > UI to support v2 api changes to show deleted entities. > -- > > Key: ATLAS-1437 > URL: https://issues.apache.org/jira/browse/ATLAS-1437 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1437.3.patch, ATLAS-1437.4.patch > > > Based on v2 api response UI will should show deleted entities. > Not allowed to add Tag to deleted entity when multiple entities are selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1437) UI to support v2 api changes to show deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1437: Attachment: (was: ATLAS-1437.1.patch) > UI to support v2 api changes to show deleted entities. > -- > > Key: ATLAS-1437 > URL: https://issues.apache.org/jira/browse/ATLAS-1437 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1437.3.patch, ATLAS-1437.4.patch > > > Based on v2 api response UI will should show deleted entities. > Not allowed to add Tag to deleted entity when multiple entities are selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1437) UI to support v2 api changes to show deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1437: Attachment: (was: ATLAS-1437.patch) > UI to support v2 api changes to show deleted entities. > -- > > Key: ATLAS-1437 > URL: https://issues.apache.org/jira/browse/ATLAS-1437 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1437.3.patch, ATLAS-1437.4.patch > > > Based on v2 api response UI will should show deleted entities. > Not allowed to add Tag to deleted entity when multiple entities are selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1437) UI to support v2 api changes to show deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1437: Attachment: (was: ATLAS-1437.2.patch) > UI to support v2 api changes to show deleted entities. > -- > > Key: ATLAS-1437 > URL: https://issues.apache.org/jira/browse/ATLAS-1437 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1437.3.patch, ATLAS-1437.4.patch > > > Based on v2 api response UI will should show deleted entities. > Not allowed to add Tag to deleted entity when multiple entities are selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1437) UI to support v2 api changes to show deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar updated ATLAS-1437: Attachment: ATLAS-1437.4.patch > UI to support v2 api changes to show deleted entities. > -- > > Key: ATLAS-1437 > URL: https://issues.apache.org/jira/browse/ATLAS-1437 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1437.3.patch, ATLAS-1437.4.patch > > > Based on v2 api response UI will should show deleted entities. > Not allowed to add Tag to deleted entity when multiple entities are selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (ATLAS-1437) UI to support v2 api changes to show deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalyani Kashikar reopened ATLAS-1437: - > UI to support v2 api changes to show deleted entities. > -- > > Key: ATLAS-1437 > URL: https://issues.apache.org/jira/browse/ATLAS-1437 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-1437.1.patch, ATLAS-1437.2.patch, > ATLAS-1437.3.patch, ATLAS-1437.patch > > > Based on v2 api response UI will should show deleted entities. > Not allowed to add Tag to deleted entity when multiple entities are selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
