[jira] [Commented] (ATLAS-2994) UI - If Hide deleted entity filter is applied then to UI displays deleted entity in lineage
[ https://issues.apache.org/jira/browse/ATLAS-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741866#comment-16741866 ] Tejas Rawool commented on ATLAS-2994: - [~abhib4] - I have verified the patch and it working fine. +1 for the patch. > UI - If Hide deleted entity filter is applied then to UI displays deleted > entity in lineage > --- > > Key: ATLAS-2994 > URL: https://issues.apache.org/jira/browse/ATLAS-2994 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0, trunk >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-2994.patch, SS7.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739490#comment-16739490 ] Tejas Rawool commented on ATLAS-3027: - Hi [~kevalbhatt], Patch looks good +1 for the Patch. > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increase the modal height -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3025) UI - If go to page is more/less then the available page limit then an error appears in the console
[ https://issues.apache.org/jira/browse/ATLAS-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739423#comment-16739423 ] Tejas Rawool commented on ATLAS-3025: - Hi [~kevalbhatt], Patch looks good +1 for the Patch > UI - If go to page is more/less then the available page limit then an error > appears in the console > -- > > Key: ATLAS-3025 > URL: https://issues.apache.org/jira/browse/ATLAS-3025 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3025.patch, Screenshot 2019-01-07 at 6.01.28 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3010) UI - Lineage hide process filter is not working
[ https://issues.apache.org/jira/browse/ATLAS-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739416#comment-16739416 ] Tejas Rawool commented on ATLAS-3010: - Hi [~abhib4], Patch looks good +1 for the Patch. > UI - Lineage hide process filter is not working > --- > > Key: ATLAS-3010 > URL: https://issues.apache.org/jira/browse/ATLAS-3010 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8.4, 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3010.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3026) Column level lineage show the invalid icon for the process
[ https://issues.apache.org/jira/browse/ATLAS-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739418#comment-16739418 ] Tejas Rawool commented on ATLAS-3026: - Hi [~kevalbhatt], Patch looks good +1 for the Patch. > Column level lineage show the invalid icon for the process > -- > > Key: ATLAS-3026 > URL: https://issues.apache.org/jira/browse/ATLAS-3026 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3026.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3028) UI - If a column is deleted then user needs to stop and start the server to see the change in Statistics count
Tejas Rawool created ATLAS-3028: --- Summary: UI - If a column is deleted then user needs to stop and start the server to see the change in Statistics count Key: ATLAS-3028 URL: https://issues.apache.org/jira/browse/ATLAS-3028 Project: Atlas Issue Type: Bug Affects Versions: 1.2.0, 2.0.0 Reporter: Tejas Rawool Fix For: 1.2.0, 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3025) UI - If go to page is more/less then the available page limit then an error appears in the console
Tejas Rawool created ATLAS-3025: --- Summary: UI - If go to page is more/less then the available page limit then an error appears in the console Key: ATLAS-3025 URL: https://issues.apache.org/jira/browse/ATLAS-3025 Project: Atlas Issue Type: Bug Affects Versions: 1.2.0, 2.0.0 Reporter: Tejas Rawool Fix For: 1.2.0, 2.0.0 Attachments: Screenshot 2019-01-07 at 6.01.28 PM.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3023) UI - If any entity is deleted then its record is not displayed in Deleted Entities Statistics model
[ https://issues.apache.org/jira/browse/ATLAS-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735731#comment-16735731 ] Tejas Rawool commented on ATLAS-3023: - [~abhib4], I have verified the patch and it working fine. +1 for the patch. > UI - If any entity is deleted then its record is not displayed in Deleted > Entities Statistics model > --- > > Key: ATLAS-3023 > URL: https://issues.apache.org/jira/browse/ATLAS-3023 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3023.patch, Screenshot 2019-01-07 at 3.29.52 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3023) UI - If any entity is deleted then its record is not displayed in Deleted Entities Statistics model
Tejas Rawool created ATLAS-3023: --- Summary: UI - If any entity is deleted then its record is not displayed in Deleted Entities Statistics model Key: ATLAS-3023 URL: https://issues.apache.org/jira/browse/ATLAS-3023 Project: Atlas Issue Type: Bug Affects Versions: 1.2.0, 2.0.0 Reporter: Tejas Rawool Fix For: 1.2.0, 2.0.0 Attachments: Screenshot 2019-01-07 at 3.29.52 PM.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3018) UI - classification search table shows then Basic search text with loader which is incorrect
[ https://issues.apache.org/jira/browse/ATLAS-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734051#comment-16734051 ] Tejas Rawool commented on ATLAS-3018: - Hi keval, +1 for the Patch, Tested on Branch-0.8 and Master it looks good > UI - classification search table shows then Basic search text with loader > which is incorrect > > > Key: ATLAS-3018 > URL: https://issues.apache.org/jira/browse/ATLAS-3018 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.4, 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3018-branch-0.8.patch, ATLAS-3018.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3007) UI : Add go to page and page limit option for local pagination
[ https://issues.apache.org/jira/browse/ATLAS-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732838#comment-16732838 ] Tejas Rawool commented on ATLAS-3007: - +1 for Master and Branch-0.8 > UI : Add go to page and page limit option for local pagination > -- > > Key: ATLAS-3007 > URL: https://issues.apache.org/jira/browse/ATLAS-3007 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3007-branch-0.8.patch, ATLAS-3007.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3009) UI - Please provide Full screen support for Lineage
[ https://issues.apache.org/jira/browse/ATLAS-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732835#comment-16732835 ] Tejas Rawool commented on ATLAS-3009: - +1 for Master and Branch-0.8 > UI - Please provide Full screen support for Lineage > --- > > Key: ATLAS-3009 > URL: https://issues.apache.org/jira/browse/ATLAS-3009 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8.4, 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3009-branch-0.8.patch, ATLAS-3009.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3018) UI - If any classification is search then Basic search with Loader appears while loading which is incorrect
Tejas Rawool created ATLAS-3018: --- Summary: UI - If any classification is search then Basic search with Loader appears while loading which is incorrect Key: ATLAS-3018 URL: https://issues.apache.org/jira/browse/ATLAS-3018 Project: Atlas Issue Type: Bug Affects Versions: 0.8.4, 1.2.0, 2.0.0 Reporter: Tejas Rawool Fix For: 0.8.4, 1.2.0, 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3016) UI - Lineage needs to be Center Align on Lineage Tab in Entity details page
Tejas Rawool created ATLAS-3016: --- Summary: UI - Lineage needs to be Center Align on Lineage Tab in Entity details page Key: ATLAS-3016 URL: https://issues.apache.org/jira/browse/ATLAS-3016 Project: Atlas Issue Type: Sub-task Affects Versions: 0.8.4, 1.2.0, 2.0.0 Reporter: Tejas Rawool Fix For: 0.8.4, 1.2.0, 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3010) UI - Lineage hide process filter is not working for Branch 0.8
Tejas Rawool created ATLAS-3010: --- Summary: UI - Lineage hide process filter is not working for Branch 0.8 Key: ATLAS-3010 URL: https://issues.apache.org/jira/browse/ATLAS-3010 Project: Atlas Issue Type: Sub-task Affects Versions: 0.8.4, 1.2.0 Reporter: Tejas Rawool Fix For: 0.8.4, 1.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3009) UI - Please provide Full screen support for Lineage and it needs to be center align
Tejas Rawool created ATLAS-3009: --- Summary: UI - Please provide Full screen support for Lineage and it needs to be center align Key: ATLAS-3009 URL: https://issues.apache.org/jira/browse/ATLAS-3009 Project: Atlas Issue Type: Sub-task Affects Versions: 0.8.4, 1.2.0, 2.0.0 Reporter: Tejas Rawool Fix For: 0.8.4, 1.2.0, 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2979) Added service type dropdown to filter entitydef type.
[ https://issues.apache.org/jira/browse/ATLAS-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tejas Rawool updated ATLAS-2979: Attachment: ATLAS-2979_FINAL.patch > Added service type dropdown to filter entitydef type. > - > > Key: ATLAS-2979 > URL: https://issues.apache.org/jira/browse/ATLAS-2979 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 2.0.0 >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-2979.patch, ATLAS-2979_1.patch, > ATLAS-2979_FINAL.patch, ATLAS-2979_FINAL.patch, > ATLAS-2979_UI_Improvement.patch, return-serviceType-in-api-header.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2994) UI - If Hide deleted entity filter is applied then to UI displays deleted entity in lineage
Tejas Rawool created ATLAS-2994: --- Summary: UI - If Hide deleted entity filter is applied then to UI displays deleted entity in lineage Key: ATLAS-2994 URL: https://issues.apache.org/jira/browse/ATLAS-2994 Project: Atlas Issue Type: Bug Affects Versions: 2.0.0, trunk Reporter: Tejas Rawool Fix For: 2.0.0 Attachments: SS7.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2954) Build failed with Rat check on Master Branch
Tejas Rawool created ATLAS-2954: --- Summary: Build failed with Rat check on Master Branch Key: ATLAS-2954 URL: https://issues.apache.org/jira/browse/ATLAS-2954 Project: Atlas Issue Type: Bug Affects Versions: trunk Reporter: Tejas Rawool Fix For: trunk Attachments: Screenshot 2018-11-05 at 12.15.08 PM.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2950) UI - In newer versions of chrome i.e 70 onwards, if a new column is added the instead of right most it appears at the left most
Tejas Rawool created ATLAS-2950: --- Summary: UI - In newer versions of chrome i.e 70 onwards, if a new column is added the instead of right most it appears at the left most Key: ATLAS-2950 URL: https://issues.apache.org/jira/browse/ATLAS-2950 Project: Atlas Issue Type: Bug Affects Versions: 2.0.0 Reporter: Tejas Rawool Fix For: 2.0.0, 1.2.0 Attachments: SS5.png, SS6.png Issue appears in - Version 70.0.3538.77 (Official Build) (64-bit) but doesn't appears in Version 69.0.3497.100 (Official Build) (64-bit) version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2946) UI - Tags tab doesn't renders in Entity Details page if there are 25+ classifications
Tejas Rawool created ATLAS-2946: --- Summary: UI - Tags tab doesn't renders in Entity Details page if there are 25+ classifications Key: ATLAS-2946 URL: https://issues.apache.org/jira/browse/ATLAS-2946 Project: Atlas Issue Type: Bug Affects Versions: 0.8.2 Reporter: Tejas Rawool Attachments: SS3.png, SS4.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2945) UI - If a Term is assigned to an Category then to user is able to assign the same term again
Tejas Rawool created ATLAS-2945: --- Summary: UI - If a Term is assigned to an Category then to user is able to assign the same term again Key: ATLAS-2945 URL: https://issues.apache.org/jira/browse/ATLAS-2945 Project: Atlas Issue Type: Bug Affects Versions: 2.0.0 Reporter: Tejas Rawool Fix For: 2.0.0 Attachments: SS1.png, SS2.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2800) UI - In Advance search an additional API request is fire when any column is drag and droped
Tejas Rawool created ATLAS-2800: --- Summary: UI - In Advance search an additional API request is fire when any column is drag and droped Key: ATLAS-2800 URL: https://issues.apache.org/jira/browse/ATLAS-2800 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0, 0.8.1, 2.0.0 Reporter: Tejas Rawool Fix For: 1.1.0, 2.0.0, 0.8.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2768) UI - If a classification is deleted then to it appears on the UI until the page is not reloaded
Tejas Rawool created ATLAS-2768: --- Summary: UI - If a classification is deleted then to it appears on the UI until the page is not reloaded Key: ATLAS-2768 URL: https://issues.apache.org/jira/browse/ATLAS-2768 Project: Atlas Issue Type: Bug Affects Versions: 2.0.0 Reporter: Tejas Rawool Fix For: 2.0.0 Attachments: SS12.png Steps to reproduce:- Go to Classification tab and create an classification Expected:- Success message would appear and classification would be deleted Error:- Success message appears but the classification is not deleted from UI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2767) UI - The "Create" button is not enabled if any error appears while creating classification
Tejas Rawool created ATLAS-2767: --- Summary: UI - The "Create" button is not enabled if any error appears while creating classification Key: ATLAS-2767 URL: https://issues.apache.org/jira/browse/ATLAS-2767 Project: Atlas Issue Type: Bug Affects Versions: 2.0.0 Reporter: Tejas Rawool Fix For: 2.0.0 Attachments: SS11.png Steps to reproduce:- 1.Go to Classification tab and click on create button 2.Now enter classification name and click on Add Attribute button 3.Now don't enter any attribute name and click on create button - error message will appears as "Please fill the attributes or delete the input box" 4.Now click on "X" button of attribute Expected:- Create button would be enabled Error:- Create button is not enabled which is incorrect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2754) UI - Atlas front end fail to show the input and output entity
Tejas Rawool created ATLAS-2754: --- Summary: UI - Atlas front end fail to show the input and output entity Key: ATLAS-2754 URL: https://issues.apache.org/jira/browse/ATLAS-2754 Project: Atlas Issue Type: Bug Affects Versions: 2.0.0 Reporter: Tejas Rawool Fix For: 2.0.0 Attachments: Screen Shot 2018-06-08 at 4.14.53 PM.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2684) UI - User can not create more than 20 sub-categories within category which is incorrect
Tejas Rawool created ATLAS-2684: --- Summary: UI - User can not create more than 20 sub-categories within category which is incorrect Key: ATLAS-2684 URL: https://issues.apache.org/jira/browse/ATLAS-2684 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Attachments: SS3.png If the sub categories start point reaches till 500 in left menu then this issue occurs. To reproduce this issue keep on creating Sub category within its Sub category and at some point of time user doesn't gets option to add more sub category. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2683) UI - Delete term option appears for glossary which is incorrect
Tejas Rawool created ATLAS-2683: --- Summary: UI - Delete term option appears for glossary which is incorrect Key: ATLAS-2683 URL: https://issues.apache.org/jira/browse/ATLAS-2683 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Attachments: SS4.png Steps to reproduce:- 1.Go to glossary tab 2.Now update any glossary 3.Now click on its options (3 dots) Error:- *Delete Term* option appears instead of *Create Term* and *Delete Glossary* which is incorrect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ATLAS-2676) UI - (IE-11) - If an entity is search through Basic search by Type then it show "undefined: Unknown/invalid glossary term" error
[ https://issues.apache.org/jira/browse/ATLAS-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tejas Rawool reopened ATLAS-2676: - [~madhan.neethiraj], This issue reproducible in IE 11 when basic search is done by selecting particular type, when type is selected and search button is clicked *undefined* is set in "search by term dropdown". Please find attached video with steps [^ATLAS-2676BugVideo.webm] > UI - (IE-11) - If an entity is search through Basic search by Type then it > show "undefined: Unknown/invalid glossary term" error > - > > Key: ATLAS-2676 > URL: https://issues.apache.org/jira/browse/ATLAS-2676 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 1.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2676BugVideo.webm, SS8.jpg > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2676) UI - (IE-11) - If an entity is search through Basic search by Type then it show "undefined: Unknown/invalid glossary term" error
[ https://issues.apache.org/jira/browse/ATLAS-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tejas Rawool updated ATLAS-2676: Attachment: ATLAS-2676BugVideo.webm > UI - (IE-11) - If an entity is search through Basic search by Type then it > show "undefined: Unknown/invalid glossary term" error > - > > Key: ATLAS-2676 > URL: https://issues.apache.org/jira/browse/ATLAS-2676 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 1.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2676BugVideo.webm, SS8.jpg > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2677) UI - (IE-11) - An scrollbar appears even if a single glossary is created which is incorrect
Tejas Rawool created ATLAS-2677: --- Summary: UI - (IE-11) - An scrollbar appears even if a single glossary is created which is incorrect Key: ATLAS-2677 URL: https://issues.apache.org/jira/browse/ATLAS-2677 Project: Atlas Issue Type: Sub-task Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Attachments: SS9.jpg -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2676) UI - (IE-11) - If an entity is search through Basic search by Type then it show "undefined: Unknown/invalid glossary term" error
Tejas Rawool created ATLAS-2676: --- Summary: UI - (IE-11) - If an entity is search through Basic search by Type then it show "undefined: Unknown/invalid glossary term" error Key: ATLAS-2676 URL: https://issues.apache.org/jira/browse/ATLAS-2676 Project: Atlas Issue Type: Sub-task Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Attachments: SS8.jpg -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2675) UI - (IE-11) - Continuous loader appears on details page whenever user creates an entity
Tejas Rawool created ATLAS-2675: --- Summary: UI - (IE-11) - Continuous loader appears on details page whenever user creates an entity Key: ATLAS-2675 URL: https://issues.apache.org/jira/browse/ATLAS-2675 Project: Atlas Issue Type: Sub-task Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Attachments: SS7.jpg Steps to Reproduce:- 1.In search tab click on "create new entity" 2.Now create a new entity e.g:- hbase_table Error:- Continuous loader appears on details page -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2658) UI - gId undefined error appears if user toggles to category when there are no terms and category
Tejas Rawool created ATLAS-2658: --- Summary: UI - gId undefined error appears if user toggles to category when there are no terms and category Key: ATLAS-2658 URL: https://issues.apache.org/jira/browse/ATLAS-2658 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Attachments: SSS21.png Steps to Reproduce:- 1.Go to category tab 2.Now switch to category when the category list is empty Error:- gId undefined error appears in console -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2645) UI - Continuous loader appears if user goes to Sub-Category of glossary and hit refresh button
Tejas Rawool created ATLAS-2645: --- Summary: UI - Continuous loader appears if user goes to Sub-Category of glossary and hit refresh button Key: ATLAS-2645 URL: https://issues.apache.org/jira/browse/ATLAS-2645 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Attachments: SSS20.png Steps to reproduce:- 1.Go to glossary tab and create 1 glossary 2.Now create one category 3.Now create a sub-category under the created category 4.Click on the refresh button Error:- "expected type __AtlasGlossaryCategory; found __AtlasGlossary" error appears and a continuous loader is displayed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2644) UI - Continuous loader appears if a new glossary is created and then deleted
Tejas Rawool created ATLAS-2644: --- Summary: UI - Continuous loader appears if a new glossary is created and then deleted Key: ATLAS-2644 URL: https://issues.apache.org/jira/browse/ATLAS-2644 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Attachments: SSS18.png Steps to reproduce:- 1.Go to glossary tab 2.Create a new glossary 3.Now delete that glossary Note:- Make sure its the first glossary which you are creating and deleting Error:- Given instance guid null is invalid/not found error appears along with loader -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2608) UI - Cache is not cleared if user click on cancel button while editing propagation flow
[ https://issues.apache.org/jira/browse/ATLAS-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tejas Rawool updated ATLAS-2608: Summary: UI - Cache is not cleared if user click on cancel button while editing propagation flow (was: UI - Cached is not cleared if user click on cancel button while editing propagation flow) > UI - Cache is not cleared if user click on cancel button while editing > propagation flow > --- > > Key: ATLAS-2608 > URL: https://issues.apache.org/jira/browse/ATLAS-2608 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Tejas Rawool >Priority: Major > Fix For: 1.0.0 > > > Steps to reproduce:- > > 1.Do a Basic Search for Tables > 2.Now go to Lineage Tab of sales_fact > 3.Click on arrow between sales_fact and loadSalesDaily > 4.Now switch to Block Propagation > 5.Checked any of the entity and click on cancel button > 6.Now again click on that arrow and go to block propagation without > refreshing the page > Error:- > An Duplicate entity is created which is incorrect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2608) UI - Cached is not cleared if user click on cancel button while editing propagation flow
[ https://issues.apache.org/jira/browse/ATLAS-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tejas Rawool updated ATLAS-2608: Summary: UI - Cached is not cleared if user click on cancel button while editing propagation flow (was: UI - Cashed is not cleared if user click on cancel button while editing propagation flow) > UI - Cached is not cleared if user click on cancel button while editing > propagation flow > > > Key: ATLAS-2608 > URL: https://issues.apache.org/jira/browse/ATLAS-2608 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Tejas Rawool >Priority: Major > Fix For: 1.0.0 > > > Steps to reproduce:- > > 1.Do a Basic Search for Tables > 2.Now go to Lineage Tab of sales_fact > 3.Click on arrow between sales_fact and loadSalesDaily > 4.Now switch to Block Propagation > 5.Checked any of the entity and click on cancel button > 6.Now again click on that arrow and go to block propagation without > refreshing the page > Error:- > An Duplicate entity is created which is incorrect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2608) UI - Cashed is not cleared if user click on cancel button while editing propagation flow
Tejas Rawool created ATLAS-2608: --- Summary: UI - Cashed is not cleared if user click on cancel button while editing propagation flow Key: ATLAS-2608 URL: https://issues.apache.org/jira/browse/ATLAS-2608 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Steps to reproduce:- 1.Do a Basic Search for Tables 2.Now go to Lineage Tab of sales_fact 3.Click on arrow between sales_fact and loadSalesDaily 4.Now switch to Block Propagation 5.Checked any of the entity and click on cancel button 6.Now again click on that arrow and go to block propagation without refreshing the page Error:- An Duplicate entity is created which is incorrect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2599) UI - Regression - Lineage is not displayed even it has DataSet as Supertype
Tejas Rawool created ATLAS-2599: --- Summary: UI - Regression - Lineage is not displayed even it has DataSet as Supertype Key: ATLAS-2599 URL: https://issues.apache.org/jira/browse/ATLAS-2599 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 1.0.0 Lineage should be displayed for the entity which has dataset as a supurtype of its own or nested derivatives. Example:- ‘hdfs_path’ has supertype ‘fs_path’ which has supertype as ‘DataSet’. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2539) UI : Entity detail page shows loader when lineage tab is not present
Tejas Rawool created ATLAS-2539: --- Summary: UI : Entity detail page shows loader when lineage tab is not present Key: ATLAS-2539 URL: https://issues.apache.org/jira/browse/ATLAS-2539 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0-alpha Reporter: Tejas Rawool Fix For: 1.0.0 Steps to Reproduce:- 1.Go to entity which has lineage (e.g sales_fact) 2.Go to its lineage tab and double click on entity which doesn't have lineage tab (e.g loadSalesDaily type = LoadProcess) 3.The continuous loader would be seen since lineage tab is not present for type "LoadProcess" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2484) UI - Need validation for Start Date and End Date while applying validity period
Tejas Rawool created ATLAS-2484: --- Summary: UI - Need validation for Start Date and End Date while applying validity period Key: ATLAS-2484 URL: https://issues.apache.org/jira/browse/ATLAS-2484 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0-alpha Reporter: Tejas Rawool Fix For: 1.0.0 While assigning Tags to Entity, If Apply Validity Period is checked then Start Date should not be greater then End Date and Time Zone should not accept empty values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2476) UI - In Audits Tab if Tag is updated then the updated data details is not reflected
Tejas Rawool created ATLAS-2476: --- Summary: UI - In Audits Tab if Tag is updated then the updated data details is not reflected Key: ATLAS-2476 URL: https://issues.apache.org/jira/browse/ATLAS-2476 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0-alpha Reporter: Tejas Rawool Fix For: 1.0.0 Attachments: SS28.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2358) UI - Column state is not preserved when user Searches a Tag for Basic Search
Tejas Rawool created ATLAS-2358: --- Summary: UI - Column state is not preserved when user Searches a Tag for Basic Search Key: ATLAS-2358 URL: https://issues.apache.org/jira/browse/ATLAS-2358 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Tejas Rawool Fix For: 0.8.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2329) Atlas UI Multiple Hovers appears if user click on another tag which is incorrect
Tejas Rawool created ATLAS-2329: --- Summary: Atlas UI Multiple Hovers appears if user click on another tag which is incorrect Key: ATLAS-2329 URL: https://issues.apache.org/jira/browse/ATLAS-2329 Project: Atlas Issue Type: Bug Affects Versions: trunk Reporter: Tejas Rawool Attachments: SS20.png -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2300) UI - Delete Tag is not functioning from Entity Details page
Tejas Rawool created ATLAS-2300: --- Summary: UI - Delete Tag is not functioning from Entity Details page Key: ATLAS-2300 URL: https://issues.apache.org/jira/browse/ATLAS-2300 Project: Atlas Issue Type: Bug Reporter: Tejas Rawool -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2236) UI - Basic Search Post request send attribute filters even after removing Type
[
https://issues.apache.org/jira/browse/ATLAS-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tejas Rawool updated ATLAS-2236:
Description:
Steps to Reproduce:-
# Select a Type and apply a filter for it
# Select a Tag and click on search button
# Now remove Type using "x" button of type dropdown
# After removing type click on Search button, It show error as "EntityFilters
specified without Type name"
Request Payload with type selected:-
{code}
{
"excludeDeletedEntities": true,
"typeName":"Asset",
"entityFilters":
{
"condition": "AND",
"criterion": [
{
"attributeName": "name",
"operator": "eq",
"attributeValue": "Test"
}]
},
"tagFilters": null,
"attributes": null,
"limit": 25,
"offset": 0,
"typeName": null,
"classification": "a1509022126155"
}
{code}
Request Payload without type selected:-
* entityFilters attribute is present without Type which is wrong
{code}
{
"excludeDeletedEntities": true,
"entityFilters":
{
"condition": "AND",
"criterion": [
{
"attributeName": "name",
"operator": "eq",
"attributeValue": "Test"
}]
},
"tagFilters": null,
"attributes": null,
"limit": 25,
"offset": 0,
"typeName": null,
"classification": "a1509022126155"
}
{code}
was:
Steps to Reproduce:-
# Select a Type and apply a filter for it
# Select a Tag and click on search button
# Now remove Type using "x" button of type dropdown
# After removing type click on Search button, It show error as "EntityFilters
specified without Type name"
Request Payload with type selected:-
{code}
{
"excludeDeletedEntities": true,
"typeName":"Asset",
"entityFilters":
{
"condition": "AND",
"criterion": [
{
"attributeName": "name",
"operator": "eq",
"attributeValue": "Test"
}]
},
"tagFilters": null,
"attributes": null,
"limit": 25,
"offset": 0,
"typeName": null,
"classification": "a1509022126155"
}
{code}
Request Payload without type selected:-
* entityFilters attribute is present without Type which is wrong
{code}
{
"excludeDeletedEntities": true,
"entityFilters":
{
"condition": "AND",
"criterion": [
{
"attributeName": "name",
"operator": "eq",
"attributeValue": "sdfsdf"
}]
},
"tagFilters": null,
"attributes": null,
"limit": 25,
"offset": 0,
"typeName": null,
"classification": "a1509022126155"
}
{code}
> UI - Basic Search Post request send attribute filters even after removing Type
> --
>
> Key: ATLAS-2236
> URL: https://issues.apache.org/jira/browse/ATLAS-2236
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
> Fix For: 1.0.0, 0.8.2
>
>
> Steps to Reproduce:-
> # Select a Type and apply a filter for it
> # Select a Tag and click on search button
> # Now remove Type using "x" button of type dropdown
> # After removing type click on Search button, It show error as "EntityFilters
> specified without Type name"
> Request Payload with type selected:-
> {code}
> {
> "excludeDeletedEntities": true,
> "typeName":"Asset",
> "entityFilters":
> {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "name",
> "operator": "eq",
> "attributeValue": "Test"
> }]
> },
> "tagFilters": null,
> "attributes": null,
> "limit": 25,
> "offset": 0,
> "typeName": null,
> "classification": "a1509022126155"
> }
> {code}
> Request Payload without type selected:-
> * entityFilters attribute is present without Type which is wrong
> {code}
> {
> "excludeDeletedEntities": true,
> "entityFilters":
> {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "name",
> "operator": "eq",
> "attributeValue": "Test"
> }]
> },
> "tagFilters": null,
> "attributes": null,
> "limit": 25,
> "offset": 0,
> "typeName": null,
> "classification": "a1509022126155"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2236) UI - Basic Search Post request send attribute filters even after removing Type
[
https://issues.apache.org/jira/browse/ATLAS-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tejas Rawool updated ATLAS-2236:
Description:
Steps to Reproduce:-
# Select a Type and apply a filter for it
# Select a Tag and click on search button
# Now remove Type using "x" button of type dropdown
# After removing type click on Search button, It show error as "EntityFilters
specified without Type name"
Request Payload with type selected:-
{code}
{
"excludeDeletedEntities": true,
"typeName":"Asset",
"entityFilters":
{
"condition": "AND",
"criterion": [
{
"attributeName": "name",
"operator": "eq",
"attributeValue": "Test"
}]
},
"tagFilters": null,
"attributes": null,
"limit": 25,
"offset": 0,
"typeName": null,
"classification": "a1509022126155"
}
{code}
Request Payload without type selected:-
* entityFilters attribute is present without Type which is wrong
{code}
{
"excludeDeletedEntities": true,
"entityFilters":
{
"condition": "AND",
"criterion": [
{
"attributeName": "name",
"operator": "eq",
"attributeValue": "sdfsdf"
}]
},
"tagFilters": null,
"attributes": null,
"limit": 25,
"offset": 0,
"typeName": null,
"classification": "a1509022126155"
}
{code}
was:
Steps to Reproduce:-
# Select a Type and apply a filter for it
# Select a Tag and click on search button
# Now remove Type using "x" button of type dropdown
# After removing type click on Search button, It show error as "EntityFilters
specified without Type name"
Request Payload with type selected:-
{code}
{
"excludeDeletedEntities": true,
"typeName":"Asset",
"entityFilters":
{
"condition": "AND",
"criterion": [
{
"attributeName": "name",
"operator": "eq",
"attributeValue": "sdfsdf"
}]
},
"tagFilters": null,
"attributes": null,
"limit": 25,
"offset": 0,
"typeName": null,
"classification": "a1509022126155"
}
{code}
Request Payload without type selected:-
* entityFilters attribute is present without Type which is wrong
{code}
{
"excludeDeletedEntities": true,
"entityFilters":
{
"condition": "AND",
"criterion": [
{
"attributeName": "name",
"operator": "eq",
"attributeValue": "sdfsdf"
}]
},
"tagFilters": null,
"attributes": null,
"limit": 25,
"offset": 0,
"typeName": null,
"classification": "a1509022126155"
}
{code}
> UI - Basic Search Post request send attribute filters even after removing Type
> --
>
> Key: ATLAS-2236
> URL: https://issues.apache.org/jira/browse/ATLAS-2236
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
> Fix For: 1.0.0, 0.8.2
>
>
> Steps to Reproduce:-
> # Select a Type and apply a filter for it
> # Select a Tag and click on search button
> # Now remove Type using "x" button of type dropdown
> # After removing type click on Search button, It show error as "EntityFilters
> specified without Type name"
> Request Payload with type selected:-
> {code}
> {
> "excludeDeletedEntities": true,
> "typeName":"Asset",
> "entityFilters":
> {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "name",
> "operator": "eq",
> "attributeValue": "Test"
> }]
> },
> "tagFilters": null,
> "attributes": null,
> "limit": 25,
> "offset": 0,
> "typeName": null,
> "classification": "a1509022126155"
> }
> {code}
> Request Payload without type selected:-
> * entityFilters attribute is present without Type which is wrong
> {code}
> {
> "excludeDeletedEntities": true,
> "entityFilters":
> {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "name",
> "operator": "eq",
> "attributeValue": "sdfsdf"
> }]
> },
> "tagFilters": null,
> "attributes": null,
> "limit": 25,
> "offset": 0,
> "typeName": null,
> "classification": "a1509022126155"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2204) UI - Safari Browser Alignment Issues
[ https://issues.apache.org/jira/browse/ATLAS-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tejas Rawool updated ATLAS-2204: Description: List of Safari Issues:- 1.An UI Issue appears If in Basic Search by Type few columns are added and then removed 2.If user is updating any entity by entering its StartTime and EndTime then its not getting saved 3.While assigning Tags to entities the integer datatype field is accepting characters 4.In Safari Browser the Tags Hover is getting merged with the scroller 5.If Tag is assign to any entity then after searching its shows UI issue in the search table > UI - Safari Browser Alignment Issues > > > Key: ATLAS-2204 > URL: https://issues.apache.org/jira/browse/ATLAS-2204 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Tejas Rawool > Fix For: 1.0.0, 0.8.2 > > > List of Safari Issues:- > 1.An UI Issue appears If in Basic Search by Type few columns are added and > then removed > 2.If user is updating any entity by entering its StartTime and EndTime then > its not getting saved > 3.While assigning Tags to entities the integer datatype field is accepting > characters > 4.In Safari Browser the Tags Hover is getting merged with the scroller > 5.If Tag is assign to any entity then after searching its shows UI issue in > the search table -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2194) In Basic Search for Tag if any columns are removed then UI throws exception
[ https://issues.apache.org/jira/browse/ATLAS-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tejas Rawool updated ATLAS-2194: Description: Steps to Reproduce:- 1.Create a new Tag and click on its Search Tag 2.Now remove few columns (e.g:- Tags and Type) 3.In Console Error appears on "SearchResultLayoutView" > In Basic Search for Tag if any columns are removed then UI throws exception > --- > > Key: ATLAS-2194 > URL: https://issues.apache.org/jira/browse/ATLAS-2194 > Project: Atlas > Issue Type: Bug >Reporter: Tejas Rawool >Assignee: Keval Bhatt > > Steps to Reproduce:- > 1.Create a new Tag and click on its Search Tag > 2.Now remove few columns (e.g:- Tags and Type) > 3.In Console Error appears on "SearchResultLayoutView" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2189) IE-9 Alignment Issues
Tejas Rawool created ATLAS-2189: --- Summary: IE-9 Alignment Issues Key: ATLAS-2189 URL: https://issues.apache.org/jira/browse/ATLAS-2189 Project: Atlas Issue Type: Sub-task Reporter: Tejas Rawool List of Issues in IE-9 * In Favorite Search the Save and Save As buttons are getting merged * If a new Tag is created then the Success Icon doesn't appears in the success message * The filter Pop Up needs to be properly aligned * Font inappropriate throughout the application -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2167) UI - Redirection of Pagination gives issue if user enter Page No. which does not exists
[ https://issues.apache.org/jira/browse/ATLAS-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tejas Rawool updated ATLAS-2167: Description: Steps to Reproduce:- 1.In basic search, search for the data having more than 10 records 2.Change the page size to 2, so that only 2 records would be visible on single page 3.Now go to page 3 by clicking on pagination next button 4. Now enter 50 in Go to page input box and click on go, It will display an info message as "No record found at 50th page" 5.Now click on previous button of pagination then it redirects to pagination 1 which is incorrect Expected:- It should be redirected to 2nd page instead of 1st > UI - Redirection of Pagination gives issue if user enter Page No. which does > not exists > --- > > Key: ATLAS-2167 > URL: https://issues.apache.org/jira/browse/ATLAS-2167 > Project: Atlas > Issue Type: Bug >Reporter: Tejas Rawool > > Steps to Reproduce:- > 1.In basic search, search for the data having more than 10 records > 2.Change the page size to 2, so that only 2 records would be visible on > single page > 3.Now go to page 3 by clicking on pagination next button > 4. Now enter 50 in Go to page input box and click on go, It will display an > info message as "No record found at 50th page" > 5.Now click on previous button of pagination then it redirects to pagination > 1 which is incorrect > Expected:- > It should be redirected to 2nd page instead of 1st -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2167) UI - Redirection of Pagination gives issue if user enter Page No. which does not exists
Tejas Rawool created ATLAS-2167: --- Summary: UI - Redirection of Pagination gives issue if user enter Page No. which does not exists Key: ATLAS-2167 URL: https://issues.apache.org/jira/browse/ATLAS-2167 Project: Atlas Issue Type: Bug Reporter: Tejas Rawool -- This message was sent by Atlassian JIRA (v6.4.14#64029)
