[jira] [Assigned] (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 ] pratik pandey reassigned ATLAS-2608: Assignee: pratik pandey > 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 >Assignee: pratik pandey >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-2594) UI, Tag propagation : Propagated classifications list on UI is not refreshed after propagateTags value is modified.
[ https://issues.apache.org/jira/browse/ATLAS-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2594: - Attachment: ATLAS-2594.patch > UI, Tag propagation : Propagated classifications list on UI is not refreshed > after propagateTags value is modified. > --- > > Key: ATLAS-2594 > URL: https://issues.apache.org/jira/browse/ATLAS-2594 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2594.patch > > > For the following lineage : > table1 - edge1 > process1 - edge2 -> table2 > Added tag1 from table1 with propagate set to True . On detailPage of table2 , > Propagated classifications list shows tag1. > Now , on detailPage of table2 , edited edge1 and set propagateTags to > ONE_TO_TWO (process1 to table1). Relationship update is done and tag1 is > removed from process1 and table2 in the backend. > But , UI needs a refresh to remove tag1 from Propagated Classifications list > shown on detailsPage of table2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2594) UI, Tag propagation : Propagated classifications list on UI is not refreshed after propagateTags value is modified.
pratik pandey created ATLAS-2594: Summary: UI, Tag propagation : Propagated classifications list on UI is not refreshed after propagateTags value is modified. Key: ATLAS-2594 URL: https://issues.apache.org/jira/browse/ATLAS-2594 Project: Atlas Issue Type: Bug Reporter: pratik pandey Assignee: pratik pandey For the following lineage : table1 - edge1 > process1 - edge2 -> table2 Added tag1 from table1 with propagate set to True . On detailPage of table2 , Propagated classifications list shows tag1. Now , on detailPage of table2 , edited edge1 and set propagateTags to ONE_TO_TWO (process1 to table1). Relationship update is done and tag1 is removed from process1 and table2 in the backend. But , UI needs a refresh to remove tag1 from Propagated Classifications list shown on detailsPage of table2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2584) UI , Tag propagation : Unable to modify Tag propagation at an edge to BOTH or NONE
[ https://issues.apache.org/jira/browse/ATLAS-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2584: - Attachment: ATLAS-2584.patch > UI , Tag propagation : Unable to modify Tag propagation at an edge to BOTH or > NONE > --- > > Key: ATLAS-2584 > URL: https://issues.apache.org/jira/browse/ATLAS-2584 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2584.patch > > > When an edge is selected and propagation is changed to BOTH or NONE , PUT > request is sent with default propagation (ONE_TO_TWO or TWO_TO_ONE). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2584) UI , Tag propagation : Unable to modify Tag propagation at an edge to BOTH or NONE
[ https://issues.apache.org/jira/browse/ATLAS-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2584: - Attachment: (was: ATLAS-2584.patch) > UI , Tag propagation : Unable to modify Tag propagation at an edge to BOTH or > NONE > --- > > Key: ATLAS-2584 > URL: https://issues.apache.org/jira/browse/ATLAS-2584 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > > When an edge is selected and propagation is changed to BOTH or NONE , PUT > request is sent with default propagation (ONE_TO_TWO or TWO_TO_ONE). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2584) UI , Tag propagation : Unable to modify Tag propagation at an edge to BOTH or NONE
[ https://issues.apache.org/jira/browse/ATLAS-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2584: - Attachment: ATLAS-2584.patch > UI , Tag propagation : Unable to modify Tag propagation at an edge to BOTH or > NONE > --- > > Key: ATLAS-2584 > URL: https://issues.apache.org/jira/browse/ATLAS-2584 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2584.patch > > > When an edge is selected and propagation is changed to BOTH or NONE , PUT > request is sent with default propagation (ONE_TO_TWO or TWO_TO_ONE). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2584) UI , Tag propagation : Unable to modify Tag propagation at an edge to BOTH or NONE
pratik pandey created ATLAS-2584: Summary: UI , Tag propagation : Unable to modify Tag propagation at an edge to BOTH or NONE Key: ATLAS-2584 URL: https://issues.apache.org/jira/browse/ATLAS-2584 Project: Atlas Issue Type: Bug Reporter: pratik pandey Assignee: pratik pandey When an edge is selected and propagation is changed to BOTH or NONE , PUT request is sent with default propagation (ONE_TO_TWO or TWO_TO_ONE). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2583) UI : DSL search doesn't list the associated classification list like basic search lists.
[ https://issues.apache.org/jira/browse/ATLAS-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey resolved ATLAS-2583. -- Resolution: Fixed Closing this issue because fix it needed on the server side. (ATLAS-2567) > UI : DSL search doesn't list the associated classification list like basic > search lists. > > > Key: ATLAS-2583 > URL: https://issues.apache.org/jira/browse/ATLAS-2583 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > > UI of DSL search results doesn't list the classifications associated to the > entities though the response of the DSL query returns the correct > classifications list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (ATLAS-2583) UI : DSL search doesn't list the associated classification list like basic search lists.
[ https://issues.apache.org/jira/browse/ATLAS-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2583: - Comment: was deleted (was: Closing this issue because fix it needed on the server side. (ATLAS-2567)) > UI : DSL search doesn't list the associated classification list like basic > search lists. > > > Key: ATLAS-2583 > URL: https://issues.apache.org/jira/browse/ATLAS-2583 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > > UI of DSL search results doesn't list the classifications associated to the > entities though the response of the DSL query returns the correct > classifications list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2583) UI : DSL search doesn't list the associated classification list like basic search lists.
[ https://issues.apache.org/jira/browse/ATLAS-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2583: - Closing this issue because fix it needed on the server side. (ATLAS-2567) > UI : DSL search doesn't list the associated classification list like basic > search lists. > > > Key: ATLAS-2583 > URL: https://issues.apache.org/jira/browse/ATLAS-2583 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > > UI of DSL search results doesn't list the classifications associated to the > entities though the response of the DSL query returns the correct > classifications list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2583) UI : DSL search doesn't list the associated classification list like basic search lists.
[ https://issues.apache.org/jira/browse/ATLAS-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2583: Assignee: pratik pandey > UI : DSL search doesn't list the associated classification list like basic > search lists. > > > Key: ATLAS-2583 > URL: https://issues.apache.org/jira/browse/ATLAS-2583 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > > UI of DSL search results doesn't list the classifications associated to the > entities though the response of the DSL query returns the correct > classifications list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2583) UI : DSL search doesn't list the associated classification list like basic search lists.
pratik pandey created ATLAS-2583: Summary: UI : DSL search doesn't list the associated classification list like basic search lists. Key: ATLAS-2583 URL: https://issues.apache.org/jira/browse/ATLAS-2583 Project: Atlas Issue Type: Bug Reporter: pratik pandey UI of DSL search results doesn't list the classifications associated to the entities though the response of the DSL query returns the correct classifications list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2579) UI : Block Propagation at classification level in edit propagation flow.
[ https://issues.apache.org/jira/browse/ATLAS-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2579: - Attachment: ATLAS-2579.patch > UI : Block Propagation at classification level in edit propagation flow. > > > Key: ATLAS-2579 > URL: https://issues.apache.org/jira/browse/ATLAS-2579 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2579.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2579) UI : Block Propagation at classification level in edit propagation flow.
pratik pandey created ATLAS-2579: Summary: UI : Block Propagation at classification level in edit propagation flow. Key: ATLAS-2579 URL: https://issues.apache.org/jira/browse/ATLAS-2579 Project: Atlas Issue Type: Bug Reporter: pratik pandey Assignee: pratik pandey -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2567) Classification list missing in DSL search result.
[ https://issues.apache.org/jira/browse/ATLAS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2567: Assignee: (was: Madhan Neethiraj) > Classification list missing in DSL search result. > - > > Key: ATLAS-2567 > URL: https://issues.apache.org/jira/browse/ATLAS-2567 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: pratik pandey >Priority: Major > > DSL search result doesn't have classifications list which is needed for UI to > differentiate between the propagated tag and self-associated tag. > Please find API response for DSL & BASIC search. > DSL: > > {code:java} > { > "queryType": "DSL", > "queryText": "`Table` ", > "entities": [ > { > "typeName": "Table", > "attributes": > { > "owner": "John Doe", > "createTime": 1522060403813, > "qualifiedName": "product_dim", > "name": "product_dim", > "description": "product dimension table" > }, > "guid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", > "status": "ACTIVE", > "displayText": "product_dim", > "classificationNames": ["Dimension"] > }] > } > {code} > BASIC > {code:java} > { > "queryType": "BASIC", > "searchParameters": > { > "typeName": "Table", > "excludeDeletedEntities": true, > "includeClassificationAttributes": true, > "includeSubTypes": true, > "includeSubClassifications": true, > "limit": 25, > "offset": 0, > "attributes": [] > }, > "entities": [ > { > "typeName": "Table", > "attributes": > { > "owner": "John Doe", > "createTime": 1522060403813, > "qualifiedName": "product_dim", > "name": "product_dim", > "description": "product dimension table" > }, > "guid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", > "status": "ACTIVE", > "displayText": "product_dim", > "classificationNames": ["Dimension"], > "classifications": [ > { > "typeName": "Dimension", > "entityGuid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", > "propagate": true > }] > }] > } > {code} > > As we can see basic search result have classifications list with *entityGuid* > whereas DSL search doesn't have it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2567) Classification list missing in DSL search result.
[ https://issues.apache.org/jira/browse/ATLAS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440555#comment-16440555 ] pratik pandey commented on ATLAS-2567: -- [~grahamwallis] I have updated the description and title. sorry for the ambiguity. > Classification list missing in DSL search result. > - > > Key: ATLAS-2567 > URL: https://issues.apache.org/jira/browse/ATLAS-2567 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: pratik pandey >Assignee: Madhan Neethiraj >Priority: Major > > DSL search result doesn't have classifications list which is needed for UI to > differentiate between the propagated tag and self-associated tag. > Please find API response for DSL & BASIC search. > DSL: > > {code:java} > { > "queryType": "DSL", > "queryText": "`Table` ", > "entities": [ > { > "typeName": "Table", > "attributes": > { > "owner": "John Doe", > "createTime": 1522060403813, > "qualifiedName": "product_dim", > "name": "product_dim", > "description": "product dimension table" > }, > "guid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", > "status": "ACTIVE", > "displayText": "product_dim", > "classificationNames": ["Dimension"] > }] > } > {code} > BASIC > {code:java} > { > "queryType": "BASIC", > "searchParameters": > { > "typeName": "Table", > "excludeDeletedEntities": true, > "includeClassificationAttributes": true, > "includeSubTypes": true, > "includeSubClassifications": true, > "limit": 25, > "offset": 0, > "attributes": [] > }, > "entities": [ > { > "typeName": "Table", > "attributes": > { > "owner": "John Doe", > "createTime": 1522060403813, > "qualifiedName": "product_dim", > "name": "product_dim", > "description": "product dimension table" > }, > "guid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", > "status": "ACTIVE", > "displayText": "product_dim", > "classificationNames": ["Dimension"], > "classifications": [ > { > "typeName": "Dimension", > "entityGuid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", > "propagate": true > }] > }] > } > {code} > > As we can see basic search result have classifications list with *entityGuid* > whereas DSL search doesn't have it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2567) Classification list missing in DSL search result.
[ https://issues.apache.org/jira/browse/ATLAS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2567: - Description: DSL search result doesn't have classifications list which is needed for UI to differentiate between the propagated tag and self-associated tag. Please find API response for DSL & BASIC search. DSL: {code:java} { "queryType": "DSL", "queryText": "`Table` ", "entities": [ { "typeName": "Table", "attributes": { "owner": "John Doe", "createTime": 1522060403813, "qualifiedName": "product_dim", "name": "product_dim", "description": "product dimension table" }, "guid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", "status": "ACTIVE", "displayText": "product_dim", "classificationNames": ["Dimension"] }] } {code} BASIC {code:java} { "queryType": "BASIC", "searchParameters": { "typeName": "Table", "excludeDeletedEntities": true, "includeClassificationAttributes": true, "includeSubTypes": true, "includeSubClassifications": true, "limit": 25, "offset": 0, "attributes": [] }, "entities": [ { "typeName": "Table", "attributes": { "owner": "John Doe", "createTime": 1522060403813, "qualifiedName": "product_dim", "name": "product_dim", "description": "product dimension table" }, "guid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", "status": "ACTIVE", "displayText": "product_dim", "classificationNames": ["Dimension"], "classifications": [ { "typeName": "Dimension", "entityGuid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", "propagate": true }] }] } {code} As we can see basic search result have classifications list with *entityGuid* whereas DSL search doesn't have it. Summary: Classification list missing in DSL search result. (was: DSL search API doesn't have GUID for classifications.) > Classification list missing in DSL search result. > - > > Key: ATLAS-2567 > URL: https://issues.apache.org/jira/browse/ATLAS-2567 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: pratik pandey >Assignee: Madhan Neethiraj >Priority: Major > > DSL search result doesn't have classifications list which is needed for UI to > differentiate between the propagated tag and self-associated tag. > Please find API response for DSL & BASIC search. > DSL: > > {code:java} > { > "queryType": "DSL", > "queryText": "`Table` ", > "entities": [ > { > "typeName": "Table", > "attributes": > { > "owner": "John Doe", > "createTime": 1522060403813, > "qualifiedName": "product_dim", > "name": "product_dim", > "description": "product dimension table" > }, > "guid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", > "status": "ACTIVE", > "displayText": "product_dim", > "classificationNames": ["Dimension"] > }] > } > {code} > BASIC > {code:java} > { > "queryType": "BASIC", > "searchParameters": > { > "typeName": "Table", > "excludeDeletedEntities": true, > "includeClassificationAttributes": true, > "includeSubTypes": true, > "includeSubClassifications": true, > "limit": 25, > "offset": 0, > "attributes": [] > }, > "entities": [ > { > "typeName": "Table", > "attributes": > { > "owner": "John Doe", > "createTime": 1522060403813, > "qualifiedName": "product_dim", > "name": "product_dim", > "description": "product dimension table" > }, > "guid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", > "status": "ACTIVE", > "displayText": "product_dim", > "classificationNames": ["Dimension"], > "classifications": [ > { > "typeName": "Dimension", > "entityGuid": "a31fe16a-3592-4b82-aeec-71db0f1fa85c", > "propagate": true > }] > }] > } > {code} > > As we can see basic search result have classifications list with *entityGuid* > whereas DSL search doesn't have it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2567) DSL search API doesn't have GUID for classifications.
pratik pandey created ATLAS-2567: Summary: DSL search API doesn't have GUID for classifications. Key: ATLAS-2567 URL: https://issues.apache.org/jira/browse/ATLAS-2567 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: pratik pandey Assignee: Madhan Neethiraj -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2512) UI : Set propagateTags attribute to relationship on lineage page
[ https://issues.apache.org/jira/browse/ATLAS-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2512: - Attachment: (was: ATLAS-2512.patch) > UI : Set propagateTags attribute to relationship on lineage page > > > Key: ATLAS-2512 > URL: https://issues.apache.org/jira/browse/ATLAS-2512 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2512.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2543) UI : In Edit classification window , Update button is not enabled when a validity period is removed.
[ https://issues.apache.org/jira/browse/ATLAS-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2543: - Attachment: ATLAS-2543.patch > UI : In Edit classification window , Update button is not enabled when a > validity period is removed. > > > Key: ATLAS-2543 > URL: https://issues.apache.org/jira/browse/ATLAS-2543 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2543.patch > > > 1. Create a tag and associate the tag to an entity and provide 2 validity > periods. > 2.Edit the same tag associated to the entity and remove any validity period. > 3.Update button is not enabled. > For other updates like adding new validity period, editing propagate flag , > editing tag attribute values , Update button is enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2538) UI : Searching classification by navigating to "Classifications" tab has "Exclude sub-types" check box in the search layout.
[ https://issues.apache.org/jira/browse/ATLAS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2538: - Attachment: ATLAS-2538.patch > UI : Searching classification by navigating to "Classifications" tab has > "Exclude sub-types" check box in the search layout. > > > Key: ATLAS-2538 > URL: https://issues.apache.org/jira/browse/ATLAS-2538 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2538.patch > > > When classifications are searched from "Classifications" Tab , the result > layout has "Exclude sub-types" check box which is not required . Only > "Exclude sub-classifications" and "Show historical entities" check boxes > should be good enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2539) UI : Entity detail page shows loader when lineage tab is not present
[ https://issues.apache.org/jira/browse/ATLAS-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2539: Assignee: pratik pandey > 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 >Assignee: pratik pandey >Priority: Major > 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] [Assigned] (ATLAS-2538) UI : Searching classification by navigating to "Classifications" tab has "Exclude sub-types" check box in the search layout.
[ https://issues.apache.org/jira/browse/ATLAS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2538: Assignee: pratik pandey > UI : Searching classification by navigating to "Classifications" tab has > "Exclude sub-types" check box in the search layout. > > > Key: ATLAS-2538 > URL: https://issues.apache.org/jira/browse/ATLAS-2538 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > > When classifications are searched from "Classifications" Tab , the result > layout has "Exclude sub-types" check box which is not required . Only > "Exclude sub-classifications" and "Show historical entities" check boxes > should be good enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2538) UI : Searching classification by navigating to "Classifications" tab has "Exclude sub-types" check box in the search layout.
pratik pandey created ATLAS-2538: Summary: UI : Searching classification by navigating to "Classifications" tab has "Exclude sub-types" check box in the search layout. Key: ATLAS-2538 URL: https://issues.apache.org/jira/browse/ATLAS-2538 Project: Atlas Issue Type: Bug Reporter: pratik pandey When classifications are searched from "Classifications" Tab , the result layout has "Exclude sub-types" check box which is not required . Only "Exclude sub-classifications" and "Show historical entities" check boxes should be good enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2512) UI : Set propagateTags attribute to relationship on lineage page
[ https://issues.apache.org/jira/browse/ATLAS-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2512: - Attachment: (was: ATLAS-2512.patch) > UI : Set propagateTags attribute to relationship on lineage page > > > Key: ATLAS-2512 > URL: https://issues.apache.org/jira/browse/ATLAS-2512 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2512.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2512) UI : Set propagateTags attribute to relationship on lineage page
[ https://issues.apache.org/jira/browse/ATLAS-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2512: - Attachment: ATLAS-2512.patch > UI : Set propagateTags attribute to relationship on lineage page > > > Key: ATLAS-2512 > URL: https://issues.apache.org/jira/browse/ATLAS-2512 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2512.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2528) UI : Allow user to empty date for validity period.
[ https://issues.apache.org/jira/browse/ATLAS-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2528: - Attachment: ATLAS-2528.patch > UI : Allow user to empty date for validity period. > -- > > Key: ATLAS-2528 > URL: https://issues.apache.org/jira/browse/ATLAS-2528 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2528.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2529) UI Regression : Timezone list is not displayed when adding validity period.
[ https://issues.apache.org/jira/browse/ATLAS-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2529: Assignee: pratik pandey > UI Regression : Timezone list is not displayed when adding validity period. > --- > > Key: ATLAS-2529 > URL: https://issues.apache.org/jira/browse/ATLAS-2529 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: Atlas_UI_timezones_for_validity_period.png > > > On HDP-3.0.0.0-1121 , On selecting validity period , list of timezones is not > displayed. > Attached the screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2529) UI Regression : Timezone list is not displayed when adding validity period.
pratik pandey created ATLAS-2529: Summary: UI Regression : Timezone list is not displayed when adding validity period. Key: ATLAS-2529 URL: https://issues.apache.org/jira/browse/ATLAS-2529 Project: Atlas Issue Type: Bug Reporter: pratik pandey Attachments: Atlas_UI_timezones_for_validity_period.png On HDP-3.0.0.0-1121 , On selecting validity period , list of timezones is not displayed. Attached the screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2528) UI : Allow user to empty date for validity period.
pratik pandey created ATLAS-2528: Summary: UI : Allow user to empty date for validity period. Key: ATLAS-2528 URL: https://issues.apache.org/jira/browse/ATLAS-2528 Project: Atlas Issue Type: Bug Reporter: pratik pandey Assignee: pratik pandey -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2512) UI : Set propagateTags attribute to relationship on lineage page
pratik pandey created ATLAS-2512: Summary: UI : Set propagateTags attribute to relationship on lineage page Key: ATLAS-2512 URL: https://issues.apache.org/jira/browse/ATLAS-2512 Project: Atlas Issue Type: Bug Reporter: pratik pandey Assignee: pratik pandey -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2509) updated frontend-maven-plugin to 1.4
[ https://issues.apache.org/jira/browse/ATLAS-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408045#comment-16408045 ] pratik pandey commented on ATLAS-2509: -- +1 for the patch > updated frontend-maven-plugin to 1.4 > > > Key: ATLAS-2509 > URL: https://issues.apache.org/jira/browse/ATLAS-2509 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-2509.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2508) When adding validityPeriod , default value shown in UI is not taken by the POST request.
[ https://issues.apache.org/jira/browse/ATLAS-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2508: - Attachment: ATLAS-2508.patch > When adding validityPeriod , default value shown in UI is not taken by the > POST request. > > > Key: ATLAS-2508 > URL: https://issues.apache.org/jira/browse/ATLAS-2508 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2508.patch > > > When Apply Validity Period check box is checked , default value for start > time and end time is applied > Example : 2018/03/20 2:18 PM - 2018/03/20 11:59 PM (i.e) > Start time : Today's Date Current time > End time : Todays's Date 11:59 PM > and no timezone is selected by default. > But the POST request is sent as > "validityPeriods":[ > {"startTime":"","endTime":"","timeZone":""} > ]} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2508) When adding validityPeriod , default value shown in UI is not taken by the POST request.
[ https://issues.apache.org/jira/browse/ATLAS-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2508: - Attachment: (was: ATLAS-2508.patch) > When adding validityPeriod , default value shown in UI is not taken by the > POST request. > > > Key: ATLAS-2508 > URL: https://issues.apache.org/jira/browse/ATLAS-2508 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 1.0.0 > > > When Apply Validity Period check box is checked , default value for start > time and end time is applied > Example : 2018/03/20 2:18 PM - 2018/03/20 11:59 PM (i.e) > Start time : Today's Date Current time > End time : Todays's Date 11:59 PM > and no timezone is selected by default. > But the POST request is sent as > "validityPeriods":[ > {"startTime":"","endTime":"","timeZone":""} > ]} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2508) When adding validityPeriod , default value shown in UI is not taken by the POST request.
[ https://issues.apache.org/jira/browse/ATLAS-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2508: - Attachment: ATLAS-2508.patch > When adding validityPeriod , default value shown in UI is not taken by the > POST request. > > > Key: ATLAS-2508 > URL: https://issues.apache.org/jira/browse/ATLAS-2508 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2508.patch > > > When Apply Validity Period check box is checked , default value for start > time and end time is applied > Example : 2018/03/20 2:18 PM - 2018/03/20 11:59 PM (i.e) > Start time : Today's Date Current time > End time : Todays's Date 11:59 PM > and no timezone is selected by default. > But the POST request is sent as > "validityPeriods":[ > {"startTime":"","endTime":"","timeZone":""} > ]} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2508) When adding validityPeriod , default value shown in UI is not taken by the POST request.
[ https://issues.apache.org/jira/browse/ATLAS-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2508: - Attachment: (was: ATLAS-2508.patch) > When adding validityPeriod , default value shown in UI is not taken by the > POST request. > > > Key: ATLAS-2508 > URL: https://issues.apache.org/jira/browse/ATLAS-2508 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2508.patch > > > When Apply Validity Period check box is checked , default value for start > time and end time is applied > Example : 2018/03/20 2:18 PM - 2018/03/20 11:59 PM (i.e) > Start time : Today's Date Current time > End time : Todays's Date 11:59 PM > and no timezone is selected by default. > But the POST request is sent as > "validityPeriods":[ > {"startTime":"","endTime":"","timeZone":""} > ]} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2508) When adding validityPeriod , default value shown in UI is not taken by the POST request.
[ https://issues.apache.org/jira/browse/ATLAS-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2508: - Attachment: ATLAS-2508.patch > When adding validityPeriod , default value shown in UI is not taken by the > POST request. > > > Key: ATLAS-2508 > URL: https://issues.apache.org/jira/browse/ATLAS-2508 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2508.patch > > > When Apply Validity Period check box is checked , default value for start > time and end time is applied > Example : 2018/03/20 2:18 PM - 2018/03/20 11:59 PM (i.e) > Start time : Today's Date Current time > End time : Todays's Date 11:59 PM > and no timezone is selected by default. > But the POST request is sent as > "validityPeriods":[ > {"startTime":"","endTime":"","timeZone":""} > ]} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2508) When adding validityPeriod , default value shown in UI is not taken by the POST request.
pratik pandey created ATLAS-2508: Summary: When adding validityPeriod , default value shown in UI is not taken by the POST request. Key: ATLAS-2508 URL: https://issues.apache.org/jira/browse/ATLAS-2508 Project: Atlas Issue Type: Bug Reporter: pratik pandey When Apply Validity Period check box is checked , default value for start time and end time is applied Example : 2018/03/20 2:18 PM - 2018/03/20 11:59 PM (i.e) Start time : Today's Date Current time End time : Todays's Date 11:59 PM and no timezone is selected by default. But the POST request is sent as "validityPeriods":[ {"startTime":"","endTime":"","timeZone":""} ]} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2508) When adding validityPeriod , default value shown in UI is not taken by the POST request.
[ https://issues.apache.org/jira/browse/ATLAS-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2508: Assignee: pratik pandey > When adding validityPeriod , default value shown in UI is not taken by the > POST request. > > > Key: ATLAS-2508 > URL: https://issues.apache.org/jira/browse/ATLAS-2508 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > > When Apply Validity Period check box is checked , default value for start > time and end time is applied > Example : 2018/03/20 2:18 PM - 2018/03/20 11:59 PM (i.e) > Start time : Today's Date Current time > End time : Todays's Date 11:59 PM > and no timezone is selected by default. > But the POST request is sent as > "validityPeriods":[ > {"startTime":"","endTime":"","timeZone":""} > ]} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2506) Attributes of filters in the inner filter group are not added to "attributes" JSON array of the Basic POST request body
[ https://issues.apache.org/jira/browse/ATLAS-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2506: - Attachment: ATLAS-2506.patch > Attributes of filters in the inner filter group are not added to "attributes" > JSON array of the Basic POST request body > --- > > Key: ATLAS-2506 > URL: https://issues.apache.org/jira/browse/ATLAS-2506 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2506.patch, Faceted_search.png > > > Attributes of the filters added in the inner filter group are not added in > the "attributes" parameter of the POST body. > Hence "attributes" in the POST body has only createTime , retention and not > temporary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2504) UI , Tag propagation : When an entity has the same tag propagated and directly associated , update window shows the values of propagated tags.
[ https://issues.apache.org/jira/browse/ATLAS-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2504: - Attachment: ATLAS-2504.patch > UI , Tag propagation : When an entity has the same tag propagated and > directly associated , update window shows the values of propagated tags. > -- > > Key: ATLAS-2504 > URL: https://issues.apache.org/jira/browse/ATLAS-2504 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2504.patch, tag_propagation_UI.mov > > > 1. Created 2 tables employee and employee_ctas as CTAS of employee. > 2. Created tag PII with attributes(a - float) > 3. Associated PII to employee with attribute values (a =0.5). Now tag is > propagated to employee_ctas also. > 4. Associated PII to employee_ctas with attribute values (a = 0.7). > 5. On clicking the Edit classification of employee_ctas , values of PII > associated to employee table was shown instead of employee_ctas table. > Attached the video clip . [^tag_propagation_UI.mov] > 6.But on updating the values , correctly updated the employee_ctas table > only. (For example , in the video clip , updated a to 0.8 and it updated PII > of employee_ctas) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2506) Attributes of filters in the inner filter group are not added to "attributes" JSON array of the Basic POST request body
pratik pandey created ATLAS-2506: Summary: Attributes of filters in the inner filter group are not added to "attributes" JSON array of the Basic POST request body Key: ATLAS-2506 URL: https://issues.apache.org/jira/browse/ATLAS-2506 Project: Atlas Issue Type: Bug Reporter: pratik pandey Assignee: pratik pandey Attachments: Faceted_search.png Attributes of the filters added in the inner filter group are not added in the "attributes" parameter of the POST body. Hence "attributes" in the POST body has only createTime , retention and not temporary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2504) UI , Tag propagation : When an entity has the same tag propagated and directly associated , update window shows the values of propagated tags.
pratik pandey created ATLAS-2504: Summary: UI , Tag propagation : When an entity has the same tag propagated and directly associated , update window shows the values of propagated tags. Key: ATLAS-2504 URL: https://issues.apache.org/jira/browse/ATLAS-2504 Project: Atlas Issue Type: Bug Reporter: pratik pandey Assignee: pratik pandey Attachments: tag_propagation_UI.mov 1. Created 2 tables employee and employee_ctas as CTAS of employee. 2. Created tag PII with attributes(a - float) 3. Associated PII to employee with attribute values (a =0.5). Now tag is propagated to employee_ctas also. 4. Associated PII to employee_ctas with attribute values (a = 0.7). 5. On clicking the Edit classification of employee_ctas , values of PII associated to employee table was shown instead of employee_ctas table. Attached the video clip . [^tag_propagation_UI.mov] 6.But on updating the values , correctly updated the employee_ctas table only. (For example , in the video clip , updated a to 0.8 and it updated PII of employee_ctas) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2483) UI : Display of faceted query
[ https://issues.apache.org/jira/browse/ATLAS-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401521#comment-16401521 ] pratik pandey commented on ATLAS-2483: -- [~kevalbhatt] I have attached the patch for branch-0.8 please take a look. > UI : Display of faceted query > - > > Key: ATLAS-2483 > URL: https://issues.apache.org/jira/browse/ATLAS-2483 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Minor > Attachments: ATLAS-2483-branch0.8.patch, ATLAS-2483.patch > > > On searching using basic search : > {code:java} > type = hive_column > filter = position != 1 > {code} > the applied search is displayed as Type: hive_column AND (AND (position != 1)) > In earlier versions , when OR support wasn't there in UI , same query would > display Type: hive_table AND retention = 1 > "hive_column AND (AND (position != 1))" is confusing to user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2483) UI : Display of faceted query
[ https://issues.apache.org/jira/browse/ATLAS-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2483: - Attachment: ATLAS-2483-branch0.8.patch > UI : Display of faceted query > - > > Key: ATLAS-2483 > URL: https://issues.apache.org/jira/browse/ATLAS-2483 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Minor > Attachments: ATLAS-2483-branch0.8.patch, ATLAS-2483.patch > > > On searching using basic search : > {code:java} > type = hive_column > filter = position != 1 > {code} > the applied search is displayed as Type: hive_column AND (AND (position != 1)) > In earlier versions , when OR support wasn't there in UI , same query would > display Type: hive_table AND retention = 1 > "hive_column AND (AND (position != 1))" is confusing to user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2501) UI , Tag propagation : On Search results page , entities with propagated tags have "Tag Remove button"
[ https://issues.apache.org/jira/browse/ATLAS-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2501: - Attachment: ATLAS-2501.patch > UI , Tag propagation : On Search results page , entities with propagated tags > have "Tag Remove button" > -- > > Key: ATLAS-2501 > URL: https://issues.apache.org/jira/browse/ATLAS-2501 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2501.patch, DeleteIconShownInSearchForCTAS.png > > > 1. Created 2 Hive tables > a.test_table > b.test_table_ctas (CTAS of test_table) > 2. Created a tag and associated the tag to test_table with propagate set to > True. > 3. Basic search for the tables listed test_table_ctas with PII tag and remove > button. On the detailsPage of test_table_ctas , remove button is not present. > Attached the screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2484) UI - Need validation for Start Date and End Date while applying validity period
[ https://issues.apache.org/jira/browse/ATLAS-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2484: Assignee: pratik pandey > 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 >Assignee: pratik pandey >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2484.patch > > > 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] [Updated] (ATLAS-2484) UI - Need validation for Start Date and End Date while applying validity period
[ https://issues.apache.org/jira/browse/ATLAS-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2484: - Attachment: ATLAS-2484.patch > 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 >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2484.patch > > > 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] [Assigned] (ATLAS-2501) UI , Tag propagation : On Search results page , entities with propagated tags have "Tag Remove button"
[ https://issues.apache.org/jira/browse/ATLAS-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2501: Assignee: pratik pandey > UI , Tag propagation : On Search results page , entities with propagated tags > have "Tag Remove button" > -- > > Key: ATLAS-2501 > URL: https://issues.apache.org/jira/browse/ATLAS-2501 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: DeleteIconShownInSearchForCTAS.png > > > 1. Created 2 Hive tables > a.test_table > b.test_table_ctas (CTAS of test_table) > 2. Created a tag and associated the tag to test_table with propagate set to > True. > 3. Basic search for the tables listed test_table_ctas with PII tag and remove > button. On the detailsPage of test_table_ctas , remove button is not present. > Attached the screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2501) UI , Tag propagation : On Search results page , entities with propagated tags have "Tag Remove button"
pratik pandey created ATLAS-2501: Summary: UI , Tag propagation : On Search results page , entities with propagated tags have "Tag Remove button" Key: ATLAS-2501 URL: https://issues.apache.org/jira/browse/ATLAS-2501 Project: Atlas Issue Type: Bug Reporter: pratik pandey Attachments: DeleteIconShownInSearchForCTAS.png 1. Created 2 Hive tables a.test_table b.test_table_ctas (CTAS of test_table) 2. Created a tag and associated the tag to test_table with propagate set to True. 3. Basic search for the tables listed test_table_ctas with PII tag and remove button. On the detailsPage of test_table_ctas , remove button is not present. Attached the screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2485) UI : Unable to add tag to entity from Tags Search Page
[ https://issues.apache.org/jira/browse/ATLAS-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2485: - Attachment: ATLAS-2485.patch > UI : Unable to add tag to entity from Tags Search Page > -- > > Key: ATLAS-2485 > URL: https://issues.apache.org/jira/browse/ATLAS-2485 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2485.patch > > > Tag Association window doesn't open when tag is attempted to be added by > clicking the + Button shown corresponding to the entities shown in the Tags > Search Page. > On clicking the + Button , following stack trace is seen in Console tab of > browser. > {code} > TypeError: undefined is not an object (evaluating > 'this.tagCollection.fullCollection') > tagsCollectionAddTagModalView.js:138 > onRenderAddTagModalView.js:116 > (anonymous function)backbone.marionette.min.js:1:7823 > triggerMethodbackbone.marionette.min.js:1:20699 > renderbackbone.marionette.min.js:1:28711 > (anonymous function) > renderModal.js:35:97 > openModal.js:43 > initializeAddTagModalView.js:54 > Viewbackbone-min.js:1:13838 > constructorbackbone.marionette.min.js:1:17255 > constructorbackbone.marionette.min.js:1:22359 > constructorbackbone.marionette.min.js:1:27981 > (anonymous function)backbone-min.js:1:21782 > (anonymous function)SearchResultLayoutView.js:506 > execCbrequire.js:1:12902 > checkrequire.js:1:6639 > (anonymous function)require.js:1:9059 > (anonymous function)require.js:1:819 > (anonymous function)require.js:1:9516 > eachrequire.js:1:290 > emitrequire.js:1:9487 > checkrequire.js:1:7196 > (anonymous function)require.js:1:9059 > (anonymous function)require.js:1:819 > (anonymous function)require.js:1:9516 > eachrequire.js:1:290 > emitrequire.js:1:9487 > checkrequire.js:1:7196 > (anonymous function)require.js:1:9059 > (anonymous function)require.js:1:819 > (anonymous function)require.js:1:9516 > eachrequire.js:1:290 > emitrequire.js:1:9487 > checkrequire.js:1:7196 > enablerequire.js:1:9386 > initrequire.js:1:5744 > (anonymous function)require.js:1:8052 > (anonymous function)require.js:1:819 > execCbrequire.js:1:12902 > checkrequire.js:1:6639 > enablerequire.js:1:9386 > initrequire.js:1:5744 > (anonymous function)require.js:1:11266 > {code} > CC : [~kbhatt] [~ppandey] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2485) UI : Unable to add tag to entity from Tags Search Page
pratik pandey created ATLAS-2485: Summary: UI : Unable to add tag to entity from Tags Search Page Key: ATLAS-2485 URL: https://issues.apache.org/jira/browse/ATLAS-2485 Project: Atlas Issue Type: Bug Reporter: pratik pandey Assignee: pratik pandey Tag Association window doesn't open when tag is attempted to be added by clicking the + Button shown corresponding to the entities shown in the Tags Search Page. On clicking the + Button , following stack trace is seen in Console tab of browser. {code} TypeError: undefined is not an object (evaluating 'this.tagCollection.fullCollection') tagsCollectionAddTagModalView.js:138 onRenderAddTagModalView.js:116 (anonymous function)backbone.marionette.min.js:1:7823 triggerMethodbackbone.marionette.min.js:1:20699 renderbackbone.marionette.min.js:1:28711 (anonymous function) renderModal.js:35:97 openModal.js:43 initializeAddTagModalView.js:54 Viewbackbone-min.js:1:13838 constructorbackbone.marionette.min.js:1:17255 constructorbackbone.marionette.min.js:1:22359 constructorbackbone.marionette.min.js:1:27981 (anonymous function)backbone-min.js:1:21782 (anonymous function)SearchResultLayoutView.js:506 execCbrequire.js:1:12902 checkrequire.js:1:6639 (anonymous function)require.js:1:9059 (anonymous function)require.js:1:819 (anonymous function)require.js:1:9516 eachrequire.js:1:290 emitrequire.js:1:9487 checkrequire.js:1:7196 (anonymous function)require.js:1:9059 (anonymous function)require.js:1:819 (anonymous function)require.js:1:9516 eachrequire.js:1:290 emitrequire.js:1:9487 checkrequire.js:1:7196 (anonymous function)require.js:1:9059 (anonymous function)require.js:1:819 (anonymous function)require.js:1:9516 eachrequire.js:1:290 emitrequire.js:1:9487 checkrequire.js:1:7196 enablerequire.js:1:9386 initrequire.js:1:5744 (anonymous function)require.js:1:8052 (anonymous function)require.js:1:819 execCbrequire.js:1:12902 checkrequire.js:1:6639 enablerequire.js:1:9386 initrequire.js:1:5744 (anonymous function)require.js:1:11266 {code} CC : [~kbhatt] [~ppandey] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2483) UI : Display of faceted query
[ https://issues.apache.org/jira/browse/ATLAS-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2483: - Attachment: ATLAS-2483.patch > UI : Display of faceted query > - > > Key: ATLAS-2483 > URL: https://issues.apache.org/jira/browse/ATLAS-2483 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Minor > Attachments: ATLAS-2483.patch > > > On searching using basic search : > {code:java} > type = hive_column > filter = position != 1 > {code} > the applied search is displayed as Type: hive_column AND (AND (position != 1)) > In earlier versions , when OR support wasn't there in UI , same query would > display Type: hive_table AND retention = 1 > "hive_column AND (AND (position != 1))" is confusing to user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2483) UI : Display of faceted query
[ https://issues.apache.org/jira/browse/ATLAS-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2483: Assignee: pratik pandey > UI : Display of faceted query > - > > Key: ATLAS-2483 > URL: https://issues.apache.org/jira/browse/ATLAS-2483 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Minor > Attachments: ATLAS-2483.patch > > > On searching using basic search : > {code:java} > type = hive_column > filter = position != 1 > {code} > the applied search is displayed as Type: hive_column AND (AND (position != 1)) > In earlier versions , when OR support wasn't there in UI , same query would > display Type: hive_table AND retention = 1 > "hive_column AND (AND (position != 1))" is confusing to user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2483) UI : Display of faceted query
pratik pandey created ATLAS-2483: Summary: UI : Display of faceted query Key: ATLAS-2483 URL: https://issues.apache.org/jira/browse/ATLAS-2483 Project: Atlas Issue Type: Bug Reporter: pratik pandey On searching using basic search : {code:java} type = hive_column filter = position != 1 {code} the applied search is displayed as Type: hive_column AND (AND (position != 1)) In earlier versions , when OR support wasn't there in UI , same query would display Type: hive_table AND retention = 1 "hive_column AND (AND (position != 1))" is confusing to user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2482) UI , Tag Propagation : propagate value not set correctly when editing attributes if the value is False when association
[ https://issues.apache.org/jira/browse/ATLAS-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2482: - Attachment: ATLAS-2482.patch > UI , Tag Propagation : propagate value not set correctly when editing > attributes if the value is False when association > --- > > Key: ATLAS-2482 > URL: https://issues.apache.org/jira/browse/ATLAS-2482 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2482.patch > > > 1. Created a table and a view from the table. > 2.Associated a tag to table with propagate set to False. > 3.Edited the tag attribute associated to table. Since propagate is set to > False initially , propagate check box was unchecked. But request is sent with > default value True. > 4. If check box value is toggled from > unchecked to checked and then checked to unchecked , propagate is set to > False correctly. > 5. Thus , If no action is done on propagate check box , though it is > unchecked , the request is sent as "propagate" : True. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2482) UI , Tag Propagation : propagate value not set correctly when editing attributes if the value is False when association
pratik pandey created ATLAS-2482: Summary: UI , Tag Propagation : propagate value not set correctly when editing attributes if the value is False when association Key: ATLAS-2482 URL: https://issues.apache.org/jira/browse/ATLAS-2482 Project: Atlas Issue Type: Bug Reporter: pratik pandey 1. Created a table and a view from the table. 2.Associated a tag to table with propagate set to False. 3.Edited the tag attribute associated to table. Since propagate is set to False initially , propagate check box was unchecked. But request is sent with default value True. 4. If check box value is toggled from unchecked to checked and then checked to unchecked , propagate is set to False correctly. 5. Thus , If no action is done on propagate check box , though it is unchecked , the request is sent as "propagate" : True. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2482) UI , Tag Propagation : propagate value not set correctly when editing attributes if the value is False when association
[ https://issues.apache.org/jira/browse/ATLAS-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2482: Assignee: pratik pandey > UI , Tag Propagation : propagate value not set correctly when editing > attributes if the value is False when association > --- > > Key: ATLAS-2482 > URL: https://issues.apache.org/jira/browse/ATLAS-2482 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > > 1. Created a table and a view from the table. > 2.Associated a tag to table with propagate set to False. > 3.Edited the tag attribute associated to table. Since propagate is set to > False initially , propagate check box was unchecked. But request is sent with > default value True. > 4. If check box value is toggled from > unchecked to checked and then checked to unchecked , propagate is set to > False correctly. > 5. Thus , If no action is done on propagate check box , though it is > unchecked , the request is sent as "propagate" : True. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2469) Tag propagation from object to child object or derivative asset
[ https://issues.apache.org/jira/browse/ATLAS-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2469: - Attachment: ATLAS-2469.patch > Tag propagation from object to child object or derivative asset > --- > > Key: ATLAS-2469 > URL: https://issues.apache.org/jira/browse/ATLAS-2469 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Blocker > Fix For: 1.0.0 > > Attachments: ATLAS-2469.patch > > > User Story: > As a data steward i need a scalable way to quickly and efficiently propagate > tags for efficient searches and tag based security. Likewise tags for > derivative dataset should be inherited from the parent. For example, if an > entity is tagged "Secret" then resulting entity created from a CTAS operation > should also be tagged "secret" to maintain the classification of the parent. > In the case where 2 or more datasets are aggregated the derivative dataset > should be a union of all parent tags. > Terms: > * Child business terms should inherit the tags associated with the parent > term. > * the option to propagate tags to child business terms in a hierarchy should > be provided > * Ability to update the propagated tags manually via UI or through the API > * Tagging a term should propagate to data assets that are already attached to > that business term as well > Data assets > * For supported components in HDP 2.6,if a derivative asset is created it > should inherit the tags and attributes from the original asset. > * the option to propagate tags to child entities should be provided (e.g. if > you tag a hdfs folder optionally tag all the files within it) > * Ability to update the propagated tags manually via UI or through the API > * Tagging a parent object should be inherited even after child creation > dynamically (unless a flag is set not to do this) > * Derived data assets should have the tags of the original data asset. > conflict resolution - if the different values for attributes then a UX dialog > that prompts user for action needs to be provided. Once resolved, the > resolved value will be carry forth to derivative dataset. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2469) Tag propagation from object to child object or derivative asset
[ https://issues.apache.org/jira/browse/ATLAS-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2469: - Attachment: ATLAS-2469.patch > Tag propagation from object to child object or derivative asset > --- > > Key: ATLAS-2469 > URL: https://issues.apache.org/jira/browse/ATLAS-2469 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Blocker > Fix For: 1.0.0 > > Attachments: ATLAS-2469.patch > > > User Story: > As a data steward i need a scalable way to quickly and efficiently propagate > tags for efficient searches and tag based security. Likewise tags for > derivative dataset should be inherited from the parent. For example, if an > entity is tagged "Secret" then resulting entity created from a CTAS operation > should also be tagged "secret" to maintain the classification of the parent. > In the case where 2 or more datasets are aggregated the derivative dataset > should be a union of all parent tags. > Terms: > * Child business terms should inherit the tags associated with the parent > term. > * the option to propagate tags to child business terms in a hierarchy should > be provided > * Ability to update the propagated tags manually via UI or through the API > * Tagging a term should propagate to data assets that are already attached to > that business term as well > Data assets > * For supported components in HDP 2.6,if a derivative asset is created it > should inherit the tags and attributes from the original asset. > * the option to propagate tags to child entities should be provided (e.g. if > you tag a hdfs folder optionally tag all the files within it) > * Ability to update the propagated tags manually via UI or through the API > * Tagging a parent object should be inherited even after child creation > dynamically (unless a flag is set not to do this) > * Derived data assets should have the tags of the original data asset. > conflict resolution - if the different values for attributes then a UX dialog > that prompts user for action needs to be provided. Once resolved, the > resolved value will be carry forth to derivative dataset. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2469) Tag propagation from object to child object or derivative asset
[ https://issues.apache.org/jira/browse/ATLAS-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2469: - Attachment: TagPropagation.patch > Tag propagation from object to child object or derivative asset > --- > > Key: ATLAS-2469 > URL: https://issues.apache.org/jira/browse/ATLAS-2469 > Project: Atlas > Issue Type: New Feature >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Blocker > Attachments: TagPropagation.patch > > > User Story: > As a data steward i need a scalable way to quickly and efficiently propagate > tags for efficient searches and tag based security. Likewise tags for > derivative dataset should be inherited from the parent. For example, if an > entity is tagged "Secret" then resulting entity created from a CTAS operation > should also be tagged "secret" to maintain the classification of the parent. > In the case where 2 or more datasets are aggregated the derivative dataset > should be a union of all parent tags. > Terms: > * Child business terms should inherit the tags associated with the parent > term. > * the option to propagate tags to child business terms in a hierarchy should > be provided > * Ability to update the propagated tags manually via UI or through the API > * Tagging a term should propagate to data assets that are already attached to > that business term as well > Data assets > * For supported components in HDP 2.6,if a derivative asset is created it > should inherit the tags and attributes from the original asset. > * the option to propagate tags to child entities should be provided (e.g. if > you tag a hdfs folder optionally tag all the files within it) > * Ability to update the propagated tags manually via UI or through the API > * Tagging a parent object should be inherited even after child creation > dynamically (unless a flag is set not to do this) > * Derived data assets should have the tags of the original data asset. > conflict resolution - if the different values for attributes then a UX dialog > that prompts user for action needs to be provided. Once resolved, the > resolved value will be carry forth to derivative dataset. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2469) Tag propagation from object to child object or derivative asset
[ https://issues.apache.org/jira/browse/ATLAS-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2469: - Priority: Blocker (was: Major) > Tag propagation from object to child object or derivative asset > --- > > Key: ATLAS-2469 > URL: https://issues.apache.org/jira/browse/ATLAS-2469 > Project: Atlas > Issue Type: New Feature >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Blocker > > User Story: > As a data steward i need a scalable way to quickly and efficiently propagate > tags for efficient searches and tag based security. Likewise tags for > derivative dataset should be inherited from the parent. For example, if an > entity is tagged "Secret" then resulting entity created from a CTAS operation > should also be tagged "secret" to maintain the classification of the parent. > In the case where 2 or more datasets are aggregated the derivative dataset > should be a union of all parent tags. > Terms: > * Child business terms should inherit the tags associated with the parent > term. > * the option to propagate tags to child business terms in a hierarchy should > be provided > * Ability to update the propagated tags manually via UI or through the API > * Tagging a term should propagate to data assets that are already attached to > that business term as well > Data assets > * For supported components in HDP 2.6,if a derivative asset is created it > should inherit the tags and attributes from the original asset. > * the option to propagate tags to child entities should be provided (e.g. if > you tag a hdfs folder optionally tag all the files within it) > * Ability to update the propagated tags manually via UI or through the API > * Tagging a parent object should be inherited even after child creation > dynamically (unless a flag is set not to do this) > * Derived data assets should have the tags of the original data asset. > conflict resolution - if the different values for attributes then a UX dialog > that prompts user for action needs to be provided. Once resolved, the > resolved value will be carry forth to derivative dataset. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2469) Tag propagation from object to child object or derivative asset
pratik pandey created ATLAS-2469: Summary: Tag propagation from object to child object or derivative asset Key: ATLAS-2469 URL: https://issues.apache.org/jira/browse/ATLAS-2469 Project: Atlas Issue Type: New Feature Reporter: pratik pandey Assignee: pratik pandey User Story: As a data steward i need a scalable way to quickly and efficiently propagate tags for efficient searches and tag based security. Likewise tags for derivative dataset should be inherited from the parent. For example, if an entity is tagged "Secret" then resulting entity created from a CTAS operation should also be tagged "secret" to maintain the classification of the parent. In the case where 2 or more datasets are aggregated the derivative dataset should be a union of all parent tags. Terms: * Child business terms should inherit the tags associated with the parent term. * the option to propagate tags to child business terms in a hierarchy should be provided * Ability to update the propagated tags manually via UI or through the API * Tagging a term should propagate to data assets that are already attached to that business term as well Data assets * For supported components in HDP 2.6,if a derivative asset is created it should inherit the tags and attributes from the original asset. * the option to propagate tags to child entities should be provided (e.g. if you tag a hdfs folder optionally tag all the files within it) * Ability to update the propagated tags manually via UI or through the API * Tagging a parent object should be inherited even after child creation dynamically (unless a flag is set not to do this) * Derived data assets should have the tags of the original data asset. conflict resolution - if the different values for attributes then a UX dialog that prompts user for action needs to be provided. Once resolved, the resolved value will be carry forth to derivative dataset. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2451) UI support to list tables in a namespace similar to listing tables in a db in the detailsPage of hive_db entity.
[ https://issues.apache.org/jira/browse/ATLAS-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2451: - Fix Version/s: (was: 0.8.2) 0.8.3 > UI support to list tables in a namespace similar to listing tables in a db in > the detailsPage of hive_db entity. > > > Key: ATLAS-2451 > URL: https://issues.apache.org/jira/browse/ATLAS-2451 > Project: Atlas > Issue Type: Improvement >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 1.0.0, 0.8.3 > > Attachments: ATLAS-2451.branch-0.8.patch, ATLAS-2451.master.patch > > > Following API fetches the HBase tables in a namespace. > {code:java} > /api/atlas/v2/search/relationship?limit=25=0==__hbase_table.namespace > {code} > UI support could be added to list the hbase_table entities in the > hbase_namespace entity's detailsPage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2451) UI support to list tables in a namespace similar to listing tables in a db in the detailsPage of hive_db entity.
[ https://issues.apache.org/jira/browse/ATLAS-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2451: - Attachment: ATLAS-2451.master.patch ATLAS-2451.branch-0.8.patch > UI support to list tables in a namespace similar to listing tables in a db in > the detailsPage of hive_db entity. > > > Key: ATLAS-2451 > URL: https://issues.apache.org/jira/browse/ATLAS-2451 > Project: Atlas > Issue Type: Improvement >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2451.branch-0.8.patch, ATLAS-2451.master.patch > > > Following API fetches the HBase tables in a namespace. > {code:java} > /api/atlas/v2/search/relationship?limit=25=0==__hbase_table.namespace > {code} > UI support could be added to list the hbase_table entities in the > hbase_namespace entity's detailsPage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2451) UI support to list tables in a namespace similar to listing tables in a db in the detailsPage of hive_db entity.
pratik pandey created ATLAS-2451: Summary: UI support to list tables in a namespace similar to listing tables in a db in the detailsPage of hive_db entity. Key: ATLAS-2451 URL: https://issues.apache.org/jira/browse/ATLAS-2451 Project: Atlas Issue Type: Improvement Reporter: pratik pandey Assignee: pratik pandey Following API fetches the HBase tables in a namespace. {code:java} /api/atlas/v2/search/relationship?limit=25=0==__hbase_table.namespace {code} UI support could be added to list the hbase_table entities in the hbase_namespace entity's detailsPage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2440) UI : select on "date" attribute results value in long format instead of formatted date.
[ https://issues.apache.org/jira/browse/ATLAS-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2440: - Attachment: ATLAS-2440.1.patch > UI : select on "date" attribute results value in long format instead of > formatted date. > --- > > Key: ATLAS-2440 > URL: https://issues.apache.org/jira/browse/ATLAS-2440 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 0.8.2, 1.0.0 > > Attachments: ATLAS-2440.1.patch, ATLAS-2440.patch > > > hive_table select createTime > lists the createTime in long format. > On detailsPage or results page of basic search , the value is formatted date > and not long value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2441) UI : DSL Search : type select __guid doesn't display result though the result has GUID response
[ https://issues.apache.org/jira/browse/ATLAS-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2441: - Attachment: ATLAS-2441.1.patch > UI : DSL Search : type select __guid doesn't display result though the result > has GUID response > --- > > Key: ATLAS-2441 > URL: https://issues.apache.org/jira/browse/ATLAS-2441 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 0.8.2, 1.0.0 > > Attachments: ATLAS-2441.1.patch, ATLAS-2441.patch > > > DSL query > hive_table select __guid > results all the guids. But the UI doesn't display them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2440) UI : select on "date" attribute results value in long format instead of formatted date.
[ https://issues.apache.org/jira/browse/ATLAS-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2440: Assignee: pratik pandey > UI : select on "date" attribute results value in long format instead of > formatted date. > --- > > Key: ATLAS-2440 > URL: https://issues.apache.org/jira/browse/ATLAS-2440 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Fix For: 0.8.2, 1.0.0 > > Attachments: ATLAS-2440.patch > > > hive_table select createTime > lists the createTime in long format. > On detailsPage or results page of basic search , the value is formatted date > and not long value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2440) UI : select on "date" attribute results value in long format instead of formatted date.
[ https://issues.apache.org/jira/browse/ATLAS-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2440: - Attachment: ATLAS-2440.patch > UI : select on "date" attribute results value in long format instead of > formatted date. > --- > > Key: ATLAS-2440 > URL: https://issues.apache.org/jira/browse/ATLAS-2440 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Priority: Major > Fix For: 0.8.2, 1.0.0 > > Attachments: ATLAS-2440.patch > > > hive_table select createTime > lists the createTime in long format. > On detailsPage or results page of basic search , the value is formatted date > and not long value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2441) UI : DSL Search : type select __guid doesn't display result though the result has GUID response
[ https://issues.apache.org/jira/browse/ATLAS-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2441: - Attachment: ATLAS-2441.patch > UI : DSL Search : type select __guid doesn't display result though the result > has GUID response > --- > > Key: ATLAS-2441 > URL: https://issues.apache.org/jira/browse/ATLAS-2441 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2441.patch > > > DSL query > hive_table select __guid > results all the guids. But the UI doesn't display them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2441) UI : DSL Search : type select __guid doesn't display result though the result has GUID response
[ https://issues.apache.org/jira/browse/ATLAS-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2441: Assignee: pratik pandey > UI : DSL Search : type select __guid doesn't display result though the result > has GUID response > --- > > Key: ATLAS-2441 > URL: https://issues.apache.org/jira/browse/ATLAS-2441 > Project: Atlas > Issue Type: Bug >Reporter: pratik pandey >Assignee: pratik pandey >Priority: Major > Attachments: ATLAS-2441.patch > > > DSL query > hive_table select __guid > results all the guids. But the UI doesn't display them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2441) UI : DSL Search : type select __guid doesn't display result though the result has GUID response
pratik pandey created ATLAS-2441: Summary: UI : DSL Search : type select __guid doesn't display result though the result has GUID response Key: ATLAS-2441 URL: https://issues.apache.org/jira/browse/ATLAS-2441 Project: Atlas Issue Type: Bug Reporter: pratik pandey DSL query hive_table select __guid results all the guids. But the UI doesn't display them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2440) UI : select on "date" attribute results value in long format instead of formatted date.
pratik pandey created ATLAS-2440: Summary: UI : select on "date" attribute results value in long format instead of formatted date. Key: ATLAS-2440 URL: https://issues.apache.org/jira/browse/ATLAS-2440 Project: Atlas Issue Type: Bug Reporter: pratik pandey hive_table select createTime lists the createTime in long format. On detailsPage or results page of basic search , the value is formatted date and not long value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2152) Saved Search: UI: Atlas UI not able to load the saved search
[ https://issues.apache.org/jira/browse/ATLAS-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2152: - Attachment: ATLAS-2152.patch > Saved Search: UI: Atlas UI not able to load the saved search > > > Key: ATLAS-2152 > URL: https://issues.apache.org/jira/browse/ATLAS-2152 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Ayub Pathan >Assignee: pratik pandey >Priority: Critical > Attachments: ATLAS-2152.branch0.8.patch, ATLAS-2152.patch, > SavedSearchSample.json > > > After saving the search query, Atlas UI unable to load the saved search. > Below exception is observed on the browser console > {noformat} > CommonViewFunction.js:487 Uncaught TypeError: Cannot read property 'toJSON' > of undefined > at CommonViewFunction.js:487 > at Function.s.each.s.forEach (underscore-min.js:5) > at Object.g.generateUrlFromSaveSearchObject (CommonViewFunction.js:476) > at L.d.applyValue (SearchLayoutView.js:155) > at L.d.stateChange (SaveSearchItemView.js:60) > at HTMLLIElement.dispatch (jquery.min.js:3) > at HTMLLIElement.q.handle (jquery.min.js:3) > {noformat} > Tested on master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2152) Saved Search: UI: Atlas UI not able to load the saved search
[ https://issues.apache.org/jira/browse/ATLAS-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2152: - Attachment: ATLAS-2152.branch0.8.patch > Saved Search: UI: Atlas UI not able to load the saved search > > > Key: ATLAS-2152 > URL: https://issues.apache.org/jira/browse/ATLAS-2152 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Ayub Pathan >Assignee: pratik pandey >Priority: Critical > Attachments: ATLAS-2152.branch0.8.patch, ATLAS-2152.patch, > SavedSearchSample.json > > > After saving the search query, Atlas UI unable to load the saved search. > Below exception is observed on the browser console > {noformat} > CommonViewFunction.js:487 Uncaught TypeError: Cannot read property 'toJSON' > of undefined > at CommonViewFunction.js:487 > at Function.s.each.s.forEach (underscore-min.js:5) > at Object.g.generateUrlFromSaveSearchObject (CommonViewFunction.js:476) > at L.d.applyValue (SearchLayoutView.js:155) > at L.d.stateChange (SaveSearchItemView.js:60) > at HTMLLIElement.dispatch (jquery.min.js:3) > at HTMLLIElement.q.handle (jquery.min.js:3) > {noformat} > Tested on master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2152) Saved Search: UI: Atlas UI not able to load the saved search
[ https://issues.apache.org/jira/browse/ATLAS-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2152: - Attachment: (was: ATLAS-2152.branch0.8.patch) > Saved Search: UI: Atlas UI not able to load the saved search > > > Key: ATLAS-2152 > URL: https://issues.apache.org/jira/browse/ATLAS-2152 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Ayub Pathan >Assignee: pratik pandey >Priority: Critical > Attachments: SavedSearchSample.json > > > After saving the search query, Atlas UI unable to load the saved search. > Below exception is observed on the browser console > {noformat} > CommonViewFunction.js:487 Uncaught TypeError: Cannot read property 'toJSON' > of undefined > at CommonViewFunction.js:487 > at Function.s.each.s.forEach (underscore-min.js:5) > at Object.g.generateUrlFromSaveSearchObject (CommonViewFunction.js:476) > at L.d.applyValue (SearchLayoutView.js:155) > at L.d.stateChange (SaveSearchItemView.js:60) > at HTMLLIElement.dispatch (jquery.min.js:3) > at HTMLLIElement.q.handle (jquery.min.js:3) > {noformat} > Tested on master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2152) Saved Search: UI: Atlas UI not able to load the saved search
[ https://issues.apache.org/jira/browse/ATLAS-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2152: - Attachment: (was: ATLAS-2152.patch) > Saved Search: UI: Atlas UI not able to load the saved search > > > Key: ATLAS-2152 > URL: https://issues.apache.org/jira/browse/ATLAS-2152 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Ayub Pathan >Assignee: pratik pandey >Priority: Critical > Attachments: SavedSearchSample.json > > > After saving the search query, Atlas UI unable to load the saved search. > Below exception is observed on the browser console > {noformat} > CommonViewFunction.js:487 Uncaught TypeError: Cannot read property 'toJSON' > of undefined > at CommonViewFunction.js:487 > at Function.s.each.s.forEach (underscore-min.js:5) > at Object.g.generateUrlFromSaveSearchObject (CommonViewFunction.js:476) > at L.d.applyValue (SearchLayoutView.js:155) > at L.d.stateChange (SaveSearchItemView.js:60) > at HTMLLIElement.dispatch (jquery.min.js:3) > at HTMLLIElement.q.handle (jquery.min.js:3) > {noformat} > Tested on master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2152) Saved Search: UI: Atlas UI not able to load the saved search
[ https://issues.apache.org/jira/browse/ATLAS-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2152: - Attachment: ATLAS-2152.patch > Saved Search: UI: Atlas UI not able to load the saved search > > > Key: ATLAS-2152 > URL: https://issues.apache.org/jira/browse/ATLAS-2152 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Ayub Pathan >Assignee: pratik pandey >Priority: Critical > Attachments: ATLAS-2152.branch0.8.patch, ATLAS-2152.patch, > SavedSearchSample.json > > > After saving the search query, Atlas UI unable to load the saved search. > Below exception is observed on the browser console > {noformat} > CommonViewFunction.js:487 Uncaught TypeError: Cannot read property 'toJSON' > of undefined > at CommonViewFunction.js:487 > at Function.s.each.s.forEach (underscore-min.js:5) > at Object.g.generateUrlFromSaveSearchObject (CommonViewFunction.js:476) > at L.d.applyValue (SearchLayoutView.js:155) > at L.d.stateChange (SaveSearchItemView.js:60) > at HTMLLIElement.dispatch (jquery.min.js:3) > at HTMLLIElement.q.handle (jquery.min.js:3) > {noformat} > Tested on master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2152) Saved Search: UI: Atlas UI not able to load the saved search
[ https://issues.apache.org/jira/browse/ATLAS-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2152: - Attachment: ATLAS-2152.branch0.8.patch > Saved Search: UI: Atlas UI not able to load the saved search > > > Key: ATLAS-2152 > URL: https://issues.apache.org/jira/browse/ATLAS-2152 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Ayub Pathan >Assignee: pratik pandey >Priority: Critical > Attachments: ATLAS-2152.branch0.8.patch, ATLAS-2152.patch, > SavedSearchSample.json > > > After saving the search query, Atlas UI unable to load the saved search. > Below exception is observed on the browser console > {noformat} > CommonViewFunction.js:487 Uncaught TypeError: Cannot read property 'toJSON' > of undefined > at CommonViewFunction.js:487 > at Function.s.each.s.forEach (underscore-min.js:5) > at Object.g.generateUrlFromSaveSearchObject (CommonViewFunction.js:476) > at L.d.applyValue (SearchLayoutView.js:155) > at L.d.stateChange (SaveSearchItemView.js:60) > at HTMLLIElement.dispatch (jquery.min.js:3) > at HTMLLIElement.q.handle (jquery.min.js:3) > {noformat} > Tested on master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1921) UI : Search using entity and trait attributes : UI doesn't perform range check and allows providing out of bounds values for integral and float data types.
[ https://issues.apache.org/jira/browse/ATLAS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-1921: - Fix Version/s: 0.8.2 1.0.0 > UI : Search using entity and trait attributes : UI doesn't perform range > check and allows providing out of bounds values for integral and float data > types. > --- > > Key: ATLAS-1921 > URL: https://issues.apache.org/jira/browse/ATLAS-1921 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: pratik pandey >Priority: Minor > Fix For: 1.0.0, 0.8.2 > > Attachments: ATLAS-1921.patch > > > When applying filter for integral/float data types , Number picker (the up > and down button) doesn't do range check according to the data type and lets > user go up and down and set any value.Hence when filter is applied and search > is made , 500 Internal server error is thrown. > Ex : Maximum value for an integer data type is 2 ^31^ -1 > Number picker for integer allows user go to 2147483648 and throws Invalid > number exception when searched. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1921) UI : Search using entity and trait attributes : UI doesn't perform range check and allows providing out of bounds values for integral and float data types.
[ https://issues.apache.org/jira/browse/ATLAS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-1921: - Attachment: ATLAS-1921.patch > UI : Search using entity and trait attributes : UI doesn't perform range > check and allows providing out of bounds values for integral and float data > types. > --- > > Key: ATLAS-1921 > URL: https://issues.apache.org/jira/browse/ATLAS-1921 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: pratik pandey >Priority: Minor > Fix For: 1.0.0, 0.8.2 > > Attachments: ATLAS-1921.patch > > > When applying filter for integral/float data types , Number picker (the up > and down button) doesn't do range check according to the data type and lets > user go up and down and set any value.Hence when filter is applied and search > is made , 500 Internal server error is thrown. > Ex : Maximum value for an integer data type is 2 ^31^ -1 > Number picker for integer allows user go to 2147483648 and throws Invalid > number exception when searched. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2350) UI : After Notification pops up with some error notification for search , there is an icon buffering forever.
pratik pandey created ATLAS-2350: Summary: UI : After Notification pops up with some error notification for search , there is an icon buffering forever. Key: ATLAS-2350 URL: https://issues.apache.org/jira/browse/ATLAS-2350 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: pratik pandey Assignee: pratik pandey Fired an invalid DSL query : typename = hdfs_path query = where invalid_attribute = "h1" Error notification "Invalid expression " pops up. After that , there is an icon which is buffering forever. No requests are fired after the search. But still there is a buffer icon. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2339) UI : Modifications in "columns" in Basic search result view affects DSL also.
[ https://issues.apache.org/jira/browse/ATLAS-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2339: - Attachment: ATLAS-2339.patch > UI : Modifications in "columns" in Basic search result view affects DSL also. > - > > Key: ATLAS-2339 > URL: https://issues.apache.org/jira/browse/ATLAS-2339 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk >Reporter: pratik pandey >Assignee: pratik pandey > Fix For: 1.0.0, 0.8.2 > > Attachments: ATLAS-2339.patch > > > 1.Fire a basic query , ex : type = hive_table . > 2.Switch to DSL , fire the same type=hive_table. > 3.Switch back to basic. Deselect "Type" from columns. > 4.Switch to DSL. DSL query is fired again. This time "Type" column is not > found in UI of DSL search results. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2339) UI : Modifications in "columns" in Basic search result view affects DSL also.
pratik pandey created ATLAS-2339: Summary: UI : Modifications in "columns" in Basic search result view affects DSL also. Key: ATLAS-2339 URL: https://issues.apache.org/jira/browse/ATLAS-2339 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: trunk Reporter: pratik pandey Assignee: pratik pandey Fix For: 1.0.0, 0.8.2 1.Fire a basic query , ex : type = hive_table . 2.Switch to DSL , fire the same type=hive_table. 3.Switch back to basic. Deselect "Type" from columns. 4.Switch to DSL. DSL query is fired again. This time "Type" column is not found in UI of DSL search results. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2329) Atlas UI Multiple Hovers appears if user click on another tag which is incorrect
[ https://issues.apache.org/jira/browse/ATLAS-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2329: - Attachment: ATLAS-2329.patch > 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 >Assignee: pratik pandey > Fix For: 1.0.0, 0.8.2 > > Attachments: ATLAS-2329.patch, SS20.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-2329) Atlas UI Multiple Hovers appears if user click on another tag which is incorrect
[ https://issues.apache.org/jira/browse/ATLAS-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2329: Assignee: pratik pandey (was: Keval Bhatt) > 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 >Assignee: pratik pandey > Attachments: SS20.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2272) Save the state of dragged columns using save search API.
[ https://issues.apache.org/jira/browse/ATLAS-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2272: - Fix Version/s: (was: trunk) 0.8.2 1.0.0 > Save the state of dragged columns using save search API. > > > Key: ATLAS-2272 > URL: https://issues.apache.org/jira/browse/ATLAS-2272 > Project: Atlas > Issue Type: Improvement >Reporter: pratik pandey >Assignee: Nixon Rodrigues > Fix For: 1.0.0, 0.8.2 > > Attachments: ATLAS-2272-branch0.8-ui.patch, > ATLAS-2272-master-ui.patch, ATLAS-2272.master.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2272) Save the state of dragged columns using save search API.
[ https://issues.apache.org/jira/browse/ATLAS-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2272: - Attachment: ATLAS-2272-branch0.8-ui.patch > Save the state of dragged columns using save search API. > > > Key: ATLAS-2272 > URL: https://issues.apache.org/jira/browse/ATLAS-2272 > Project: Atlas > Issue Type: Improvement >Reporter: pratik pandey >Assignee: Nixon Rodrigues > Fix For: trunk > > Attachments: ATLAS-2272-branch0.8-ui.patch, > ATLAS-2272-master-ui.patch, ATLAS-2272.master.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2272) Save the state of dragged columns using save search API.
[ https://issues.apache.org/jira/browse/ATLAS-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2272: - Attachment: (was: ATLAS-2272-branch0.8.patch) > Save the state of dragged columns using save search API. > > > Key: ATLAS-2272 > URL: https://issues.apache.org/jira/browse/ATLAS-2272 > Project: Atlas > Issue Type: Improvement >Reporter: pratik pandey >Assignee: Nixon Rodrigues > Fix For: trunk > > Attachments: ATLAS-2272-master-ui.patch, ATLAS-2272.master.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2272) Save the state of dragged columns using save search API.
[ https://issues.apache.org/jira/browse/ATLAS-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2272: - Attachment: ATLAS-2272-branch0.8.patch ATLAS-2272-master-ui.patch > Save the state of dragged columns using save search API. > > > Key: ATLAS-2272 > URL: https://issues.apache.org/jira/browse/ATLAS-2272 > Project: Atlas > Issue Type: Improvement >Reporter: pratik pandey >Assignee: Nixon Rodrigues > Fix For: trunk > > Attachments: ATLAS-2272-branch0.8.patch, ATLAS-2272-master-ui.patch, > ATLAS-2272.master.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2282) Saved favorite search appears only on refresh after creation when there are 25+ favorite searches .
[ https://issues.apache.org/jira/browse/ATLAS-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2282: - Attachment: ATLAS-2282.patch > Saved favorite search appears only on refresh after creation when there are > 25+ favorite searches . > --- > > Key: ATLAS-2282 > URL: https://issues.apache.org/jira/browse/ATLAS-2282 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: pratik pandey > Fix For: 1.0.0, 0.8.2 > > Attachments: ATLAS-2282.patch > > > 1. Created 24 basic favorite search . > 2. Created 25th basic favorite search. Popup notification displayed that the > search is successfully created.Without any refresh , 25th favorite search > appeared in the favorite search list. > 3. Created 26th basic favorite search. Popup notification displayed that the > search is successfully created. > 4.But the favorite search list didn't display the 26th basic favorite search > but only the ld 25 searches, > 5.On page refresh , the 26th favorite search was displayed. > Thus , when more than 25 Basic/Advanced favorite searches (Basic and Advanced > separately 25) are created , the newly created favorite search is displayed > only on page refresh. > CC : [~kevalbhatt] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2282) Saved favorite search appears only on refresh after creation when there are 25+ favorite searches .
[ https://issues.apache.org/jira/browse/ATLAS-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2282: - Fix Version/s: 0.8.2 1.0.0 > Saved favorite search appears only on refresh after creation when there are > 25+ favorite searches . > --- > > Key: ATLAS-2282 > URL: https://issues.apache.org/jira/browse/ATLAS-2282 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: pratik pandey > Fix For: 1.0.0, 0.8.2 > > Attachments: ATLAS-2282.patch > > > 1. Created 24 basic favorite search . > 2. Created 25th basic favorite search. Popup notification displayed that the > search is successfully created.Without any refresh , 25th favorite search > appeared in the favorite search list. > 3. Created 26th basic favorite search. Popup notification displayed that the > search is successfully created. > 4.But the favorite search list didn't display the 26th basic favorite search > but only the ld 25 searches, > 5.On page refresh , the 26th favorite search was displayed. > Thus , when more than 25 Basic/Advanced favorite searches (Basic and Advanced > separately 25) are created , the newly created favorite search is displayed > only on page refresh. > CC : [~kevalbhatt] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2300) UI - Delete Tag is not functioning from Entity Details page
[ https://issues.apache.org/jira/browse/ATLAS-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2300: - Attachment: ATLAS-2300.patch > 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 >Assignee: pratik pandey > Attachments: ATLAS-2300.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-2300) UI - Delete Tag is not functioning from Entity Details page
[ https://issues.apache.org/jira/browse/ATLAS-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2300: Assignee: pratik pandey > 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 >Assignee: pratik pandey > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-2282) Saved favorite search appears only on refresh after creation when there are 25+ favorite searches .
[ https://issues.apache.org/jira/browse/ATLAS-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey reassigned ATLAS-2282: Assignee: pratik pandey > Saved favorite search appears only on refresh after creation when there are > 25+ favorite searches . > --- > > Key: ATLAS-2282 > URL: https://issues.apache.org/jira/browse/ATLAS-2282 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: pratik pandey > > 1. Created 24 basic favorite search . > 2. Created 25th basic favorite search. Popup notification displayed that the > search is successfully created.Without any refresh , 25th favorite search > appeared in the favorite search list. > 3. Created 26th basic favorite search. Popup notification displayed that the > search is successfully created. > 4.But the favorite search list didn't display the 26th basic favorite search > but only the ld 25 searches, > 5.On page refresh , the 26th favorite search was displayed. > Thus , when more than 25 Basic/Advanced favorite searches (Basic and Advanced > separately 25) are created , the newly created favorite search is displayed > only on page refresh. > CC : [~kevalbhatt] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2285) UI : Renamed saved search with date attribute.
[ https://issues.apache.org/jira/browse/ATLAS-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2285: - Fix Version/s: 0.8.2 1.0.0 > UI : Renamed saved search with date attribute. > -- > > Key: ATLAS-2285 > URL: https://issues.apache.org/jira/browse/ATLAS-2285 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: pratik pandey >Priority: Critical > Fix For: 1.0.0, 0.8.2 > > Attachments: ATLAS-2285.patch, saved_search_with_date_renamed.mov > > > 1. Fired basic search typename = hive_table , filter CreateTime = 08/02/2017 > 9:10 PM and saved search as date_search > 2. Clicked on the saved search "date_search" and verified the filters. filter > CreateTime = 08/02/2017 9:10 PM is rightly set. > 3. Clicked on the "date_search" and renamed it to "date_search_renamed" > without modifying the filters . > 4.PUT REST call to update the search had the correct filter value. > 5. Refreshed the page and clicked on the "date_search_renamed". Now , the > date filter was modified to CreateTime = 01/01/1970 5:30 AM . > 6. /api/atlas/v2/search/saved GET response had 08/02/2017 9:10 PM filter > value for "date_search_renamed" but UI shows 01/01/1970 5:30 AM. > Attached the video recording. > CC : [~kevalbhatt] [~praik24mac] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2285) UI : Renamed saved search with date attribute.
[ https://issues.apache.org/jira/browse/ATLAS-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2285: - Attachment: ATLAS-2285.patch > UI : Renamed saved search with date attribute. > -- > > Key: ATLAS-2285 > URL: https://issues.apache.org/jira/browse/ATLAS-2285 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: pratik pandey >Priority: Critical > Attachments: ATLAS-2285.patch, saved_search_with_date_renamed.mov > > > 1. Fired basic search typename = hive_table , filter CreateTime = 08/02/2017 > 9:10 PM and saved search as date_search > 2. Clicked on the saved search "date_search" and verified the filters. filter > CreateTime = 08/02/2017 9:10 PM is rightly set. > 3. Clicked on the "date_search" and renamed it to "date_search_renamed" > without modifying the filters . > 4.PUT REST call to update the search had the correct filter value. > 5. Refreshed the page and clicked on the "date_search_renamed". Now , the > date filter was modified to CreateTime = 01/01/1970 5:30 AM . > 6. /api/atlas/v2/search/saved GET response had 08/02/2017 9:10 PM filter > value for "date_search_renamed" but UI shows 01/01/1970 5:30 AM. > Attached the video recording. > CC : [~kevalbhatt] [~praik24mac] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1964) UI : Support to resize and order columns in Search table
[ https://issues.apache.org/jira/browse/ATLAS-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-1964: - Attachment: (was: ATLAS-1964-branch0.8-1.patch) > UI : Support to resize and order columns in Search table > > > Key: ATLAS-1964 > URL: https://issues.apache.org/jira/browse/ATLAS-1964 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Keval Bhatt >Assignee: pratik pandey > Fix For: 1.0.0, 0.8.1 > > Attachments: ATLAS-1964-branch0.8.patch, ATLAS-1964-master.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2297) UI : Support to resize columns in Search table
[ https://issues.apache.org/jira/browse/ATLAS-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pratik pandey updated ATLAS-2297: - Fix Version/s: 0.8.2 1.0.0 > UI : Support to resize columns in Search table > -- > > Key: ATLAS-2297 > URL: https://issues.apache.org/jira/browse/ATLAS-2297 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: pratik pandey >Assignee: pratik pandey > Fix For: 1.0.0, 0.8.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)