[jira] [Created] (ATLAS-3715) ZipFileMigrationImporter: Improve Speed of Primitive Attribute Assignment

[Ashutosh Mestry (Jira)]

Ashutosh Mestry created ATLAS-3715:
--

 Summary: ZipFileMigrationImporter: Improve Speed of Primitive 
Attribute Assignment
 Key: ATLAS-3715
 URL: https://issues.apache.org/jira/browse/ATLAS-3715
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: trunk
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
 Fix For: trunk


*Background*

While profiling entity creation as part of zip file-based migration import, it 
was observed that over 50% of time is spent in assigning values to attributes 
that are of primitive type viz. string, date, etc.

*Methodology Used*

The entity creation flow already has _MetricRecorder_ added to key steps within 
the entity creation flow. Additional methods (like _mapPrimitiveValue_) were 
profiled to get complete breakdown.

Data set contained large number of entities of various types. Ones used were 
_hdfs_path, hive_db, hive_table, hive_column, hive_process, 
hive_process_execution, hive_column_lineage_.

*Solution*

Within the migration request context, use the _setEncodedProperty_ instead of 
using the current route of creating _AtttributeMutationContext_.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Review Request 72287: Edge Creation Improvements

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72287/#review220181
---


Fix it, then Ship it!





repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
Lines 344 (patched)


edgeLabel is typicallu used to find subset of edges from a given vertex. 
Having an edge-index on the label probably won't help improve the performance; 
however, need to understand the impact of creating this index in an existing 
Atlas instance having large number of edges. 1) Would index be populated with 
existing edge labels? 2) If yes, how long would the index creation take - say 
for 1m edges? 3) If no, would search ignore edges that were not indexd?

I suggest to find the performace impact of not having this index.


- Madhan Neethiraj


On March 30, 2020, 11:19 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72287/
> ---
> 
> (Updated March 30, 2020, 11:19 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3706
> https://issues.apache.org/jira/browse/ATLAS-3706
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> 
> 1. Added Metrics to most of the methods in entity creation. (The patch does 
> not include the additional metrics added to additional places.)
> 2. Started importing large number of entities using the 
> _ZipFileMigrationImporter_.
> 3. Observed behavior of import over 24 hours. Observations included CPU 
> usage, memory usage and the import throughput using the _metric.log_.
> 4. Changes were added to the one at a time. Impact of the change was observed 
> for performance (via metric.log) and accuracy before next change was added.
> 
> **Observations**
> * Relationship creation took inordinately large amount of time under load. 
> The time was spent in _GraphHelper.getAdjacentEdgesByLabel_. This 
> implementation also caused memory build up of _AtlasEdge_ objects which 
> stayed in memory for long time. This had the secondary effect of slowing down 
> entity creation operations after about 6 hours (this duration differed with 
> node configuration).
> * _GraphHelper.getOrCreateEdge_ did a vertex to vertex comparison which is 
> time consuming.
> * _GraphBackedSearchIndexer_ edge label index. Majority of edge creation 
> operation included lookup by edge label.
> 
> **Configuration**
> Cluster: 3 node: 40 cores, 128 GB RAM, 1.5 TB of disk space.
> Atlas configuration: 32 GB RAM.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  647e3040c 
>   repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
> 5ab9f4d13 
> 
> 
> Diff: https://reviews.apache.org/r/72287/diff/1/
> 
> 
> Testing
> ---
> 
> **Manual tests**
> (See above).
> Accuracy verification.
> 
> **Unit tests**
> Executed existing unit tests.
> 
> **Pre-commit build**
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1776/
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 72287: Edge Creation Improvements

[Nikhil Bonte]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72287/#review220180
---


Ship it!




Ship It!

- Nikhil Bonte


On March 30, 2020, 11:19 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72287/
> ---
> 
> (Updated March 30, 2020, 11:19 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3706
> https://issues.apache.org/jira/browse/ATLAS-3706
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> 
> 1. Added Metrics to most of the methods in entity creation. (The patch does 
> not include the additional metrics added to additional places.)
> 2. Started importing large number of entities using the 
> _ZipFileMigrationImporter_.
> 3. Observed behavior of import over 24 hours. Observations included CPU 
> usage, memory usage and the import throughput using the _metric.log_.
> 4. Changes were added to the one at a time. Impact of the change was observed 
> for performance (via metric.log) and accuracy before next change was added.
> 
> **Observations**
> * Relationship creation took inordinately large amount of time under load. 
> The time was spent in _GraphHelper.getAdjacentEdgesByLabel_. This 
> implementation also caused memory build up of _AtlasEdge_ objects which 
> stayed in memory for long time. This had the secondary effect of slowing down 
> entity creation operations after about 6 hours (this duration differed with 
> node configuration).
> * _GraphHelper.getOrCreateEdge_ did a vertex to vertex comparison which is 
> time consuming.
> * _GraphBackedSearchIndexer_ edge label index. Majority of edge creation 
> operation included lookup by edge label.
> 
> **Configuration**
> Cluster: 3 node: 40 cores, 128 GB RAM, 1.5 TB of disk space.
> Atlas configuration: 32 GB RAM.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  647e3040c 
>   repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
> 5ab9f4d13 
> 
> 
> Diff: https://reviews.apache.org/r/72287/diff/1/
> 
> 
> Testing
> ---
> 
> **Manual tests**
> (See above).
> Accuracy verification.
> 
> **Unit tests**
> Executed existing unit tests.
> 
> **Pre-commit build**
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1776/
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

[jira] [Resolved] (ATLAS-3701) Performance improvements in writing audit logs - Classification dissociation

[Nikhil Bonte (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikhil Bonte resolved ATLAS-3701.
-
Fix Version/s: 3.0.0
   2.1.0
   Resolution: Fixed

> Performance improvements in writing audit logs - Classification dissociation
> 
>
> Key: ATLAS-3701
> URL: https://issues.apache.org/jira/browse/ATLAS-3701
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> Further to ATLAS-3568, 
> this will improve audit writing in case of classfication dissociation



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3710) [Business Metadata] Missing Business Metadata attribute info in list view

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072747#comment-17072747
 ] 

ASF subversion and git services commented on ATLAS-3710:


Commit bf63f0f400b37a31d07b98a668358a278a8e822f in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=bf63f0f ]

ATLAS-3710 : [Business Metadata] Missing Business Metadata attribute info in 
list view

(cherry picked from commit 2fbfb5572e3ae7e71e71b70e391844d98293599a)


> [Business Metadata] Missing Business Metadata attribute info in list view
> -
>
> Key: ATLAS-3710
> URL: https://issues.apache.org/jira/browse/ATLAS-3710
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3710.patch, Screenshot 2020-03-31 at 7.28.48 
> PM.png, Screenshot 2020-03-31 at 7.29.39 PM.png
>
>
> Currently only Attribute Name, Type and Applicable Type(s) are listed in the 
> UI. Need to list Search Weight, Enable Multi values and Max length too. 
> Currently, the only way to know these attributes is to click on edit. Tedious 
> when the user wants to track multiple attributes.
> Screenshots attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3706) UI: Audit change for Business metadata/labels/user-define property

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072746#comment-17072746
 ] 

ASF subversion and git services commented on ATLAS-3706:


Commit 003bdb5e9bfbddd5f2021b5d8bdafe824d9e730e in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=003bdb5 ]

ATLAS-3706 : UI: Audit change for Business metadata/labels/user-define property

(cherry picked from commit 95923fba04e99c9bcf4af70fe8faf834c802fdf9)


> UI: Audit change for Business metadata/labels/user-define property
> --
>
> Key: ATLAS-3706
> URL: https://issues.apache.org/jira/browse/ATLAS-3706
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3706.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3706) UI: Audit change for Business metadata/labels/user-define property

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072745#comment-17072745
 ] 

ASF subversion and git services commented on ATLAS-3706:


Commit 95923fba04e99c9bcf4af70fe8faf834c802fdf9 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=95923fb ]

ATLAS-3706 : UI: Audit change for Business metadata/labels/user-define property


> UI: Audit change for Business metadata/labels/user-define property
> --
>
> Key: ATLAS-3706
> URL: https://issues.apache.org/jira/browse/ATLAS-3706
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3706.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3710) [Business Metadata] Missing Business Metadata attribute info in list view

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072744#comment-17072744
 ] 

ASF subversion and git services commented on ATLAS-3710:


Commit 2fbfb5572e3ae7e71e71b70e391844d98293599a in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2fbfb55 ]

ATLAS-3710 : [Business Metadata] Missing Business Metadata attribute info in 
list view


> [Business Metadata] Missing Business Metadata attribute info in list view
> -
>
> Key: ATLAS-3710
> URL: https://issues.apache.org/jira/browse/ATLAS-3710
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3710.patch, Screenshot 2020-03-31 at 7.28.48 
> PM.png, Screenshot 2020-03-31 at 7.29.39 PM.png
>
>
> Currently only Attribute Name, Type and Applicable Type(s) are listed in the 
> UI. Need to list Search Weight, Enable Multi values and Max length too. 
> Currently, the only way to know these attributes is to click on edit. Tedious 
> when the user wants to track multiple attributes.
> Screenshots attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3710) [Business Metadata] Missing Business Metadata attribute info in list view

[Nixon Rodrigues (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072728#comment-17072728
 ] 

Nixon Rodrigues commented on ATLAS-3710:


+1 for the patch. [~kevalbhatt] thanks.

> [Business Metadata] Missing Business Metadata attribute info in list view
> -
>
> Key: ATLAS-3710
> URL: https://issues.apache.org/jira/browse/ATLAS-3710
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3710.patch, Screenshot 2020-03-31 at 7.28.48 
> PM.png, Screenshot 2020-03-31 at 7.29.39 PM.png
>
>
> Currently only Attribute Name, Type and Applicable Type(s) are listed in the 
> UI. Need to list Search Weight, Enable Multi values and Max length too. 
> Currently, the only way to know these attributes is to click on edit. Tedious 
> when the user wants to track multiple attributes.
> Screenshots attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3710) [Business Metadata] Missing Business Metadata attribute info in list view

[Keval Bhatt (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-3710:
---
Attachment: ATLAS-3710.patch

> [Business Metadata] Missing Business Metadata attribute info in list view
> -
>
> Key: ATLAS-3710
> URL: https://issues.apache.org/jira/browse/ATLAS-3710
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3710.patch, Screenshot 2020-03-31 at 7.28.48 
> PM.png, Screenshot 2020-03-31 at 7.29.39 PM.png
>
>
> Currently only Attribute Name, Type and Applicable Type(s) are listed in the 
> UI. Need to list Search Weight, Enable Multi values and Max length too. 
> Currently, the only way to know these attributes is to click on edit. Tedious 
> when the user wants to track multiple attributes.
> Screenshots attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3706) UI: Audit change for Business metadata/labels/user-define property

[Nixon Rodrigues (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072681#comment-17072681
 ] 

Nixon Rodrigues commented on ATLAS-3706:


+1 for the patch. Thanks [~kevalbhatt] for the patch

> UI: Audit change for Business metadata/labels/user-define property
> --
>
> Key: ATLAS-3706
> URL: https://issues.apache.org/jira/browse/ATLAS-3706
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3706.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3706) UI: Audit change for Business metadata/labels/user-define property

[Keval Bhatt (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-3706:
---
Attachment: ATLAS-3706.patch

> UI: Audit change for Business metadata/labels/user-define property
> --
>
> Key: ATLAS-3706
> URL: https://issues.apache.org/jira/browse/ATLAS-3706
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3706.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-3714) UI: Show Business Metadata column name in search results columns droupdown

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3714:
--

 Summary: UI: Show Business Metadata column name in search results 
columns droupdown
 Key: ATLAS-3714
 URL: https://issues.apache.org/jira/browse/ATLAS-3714
 Project: Atlas
  Issue Type: Sub-task
Reporter: Keval Bhatt
Assignee: Keval Bhatt






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Review Request 72300: ATLAS-3696 : [Business Metadata] No option to check/uncheck Business Metadata field in search results

[Pinal Shah]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72300/
---

Review request for atlas, keval bhatt, Madhan Neethiraj, Mandar Ambawane, Nixon 
Rodrigues, and Sarath Subramanian.


Bugs: ATLAS-3696
https://issues.apache.org/jira/browse/ATLAS-3696


Repository: atlas


Description
---

For instance, there is no way to show "Business Metadata" column if Business 
Metadata attribute filter is not applied while searching.


Diffs
-

  intg/src/main/java/org/apache/atlas/model/instance/AtlasEntityHeader.java 
7d2476a64 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
 3a0d001bc 


Diff: https://reviews.apache.org/r/72300/diff/1/


Testing
---

Selected Entity which has business attribute, the response of basic search will 
include businessMetadata attributes


Thanks,

Pinal Shah

[jira] [Commented] (ATLAS-3711) UI: Classification/Term modal should close after "create/update/delete" response

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072586#comment-17072586
 ] 

ASF subversion and git services commented on ATLAS-3711:


Commit e71d6c29e2d265f707341cf060d1f2e3633a2f4d in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e71d6c2 ]

ATLAS-3711 : UI: Classification/Term modal should close after 
create/update/delete response

(cherry picked from commit 2ac034253386ca8d173f67317505076783cedbf7)


> UI: Classification/Term modal should close after "create/update/delete"  
> response
> -
>
> Key: ATLAS-3711
> URL: https://issues.apache.org/jira/browse/ATLAS-3711
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3711.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3713) UI : DSL select count() query doesn't display results on UI

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072585#comment-17072585
 ] 

ASF subversion and git services commented on ATLAS-3713:


Commit fdbd3b7fe2c32d0d7fc9392555daf7c7b9ed0887 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fdbd3b7 ]

ATLAS-3713 : UI : DSL select count() query doesn't display results on UI

(cherry picked from commit 6ece28fd957ca2e90936914bdfd26c7c35c1f306)


> UI : DSL select count() query doesn't display results on UI
> ---
>
> Key: ATLAS-3713
> URL: https://issues.apache.org/jira/browse/ATLAS-3713
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3713.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3713) UI : DSL select count() query doesn't display results on UI

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072580#comment-17072580
 ] 

ASF subversion and git services commented on ATLAS-3713:


Commit 6ece28fd957ca2e90936914bdfd26c7c35c1f306 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=6ece28f ]

ATLAS-3713 : UI : DSL select count() query doesn't display results on UI


> UI : DSL select count() query doesn't display results on UI
> ---
>
> Key: ATLAS-3713
> URL: https://issues.apache.org/jira/browse/ATLAS-3713
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3713.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3711) UI: Classification/Term modal should close after "create/update/delete" response

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072579#comment-17072579
 ] 

ASF subversion and git services commented on ATLAS-3711:


Commit 2ac034253386ca8d173f67317505076783cedbf7 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2ac0342 ]

ATLAS-3711 : UI: Classification/Term modal should close after 
create/update/delete response


> UI: Classification/Term modal should close after "create/update/delete"  
> response
> -
>
> Key: ATLAS-3711
> URL: https://issues.apache.org/jira/browse/ATLAS-3711
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3711.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3711) UI: Classification/Term modal should close after "create/update/delete" response

[Nixon Rodrigues (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072573#comment-17072573
 ] 

Nixon Rodrigues commented on ATLAS-3711:


+1 for the patch, thanks [~kevalbhatt]

> UI: Classification/Term modal should close after "create/update/delete"  
> response
> -
>
> Key: ATLAS-3711
> URL: https://issues.apache.org/jira/browse/ATLAS-3711
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3711.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3713) UI : DSL select count() query doesn't display results on UI

[Nixon Rodrigues (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072572#comment-17072572
 ] 

Nixon Rodrigues commented on ATLAS-3713:


+1 for the patch, Thanks [~kevalbhatt]

> UI : DSL select count() query doesn't display results on UI
> ---
>
> Key: ATLAS-3713
> URL: https://issues.apache.org/jira/browse/ATLAS-3713
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3713.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3706) UI: Audit change for Business metadata/labels/user-define property

[Keval Bhatt (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-3706:
---
Summary: UI: Audit change for Business metadata/labels/user-define property 
 (was: UI: Audit change for Business metadata)

> UI: Audit change for Business metadata/labels/user-define property
> --
>
> Key: ATLAS-3706
> URL: https://issues.apache.org/jira/browse/ATLAS-3706
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3713) UI : DSL select count() query doesn't display results on UI

[Keval Bhatt (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-3713:
---
Attachment: ATLAS-3713.patch

> UI : DSL select count() query doesn't display results on UI
> ---
>
> Key: ATLAS-3713
> URL: https://issues.apache.org/jira/browse/ATLAS-3713
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3713.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3711) UI: Classification/Term modal should close after "create/update/delete" response

[Keval Bhatt (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-3711:
---
Fix Version/s: 3.0.0
   2.1.0

> UI: Classification/Term modal should close after "create/update/delete"  
> response
> -
>
> Key: ATLAS-3711
> URL: https://issues.apache.org/jira/browse/ATLAS-3711
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3711.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3711) UI: Classification/Term modal should close after "create/update/delete" response

[Keval Bhatt (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-3711:
---
Attachment: ATLAS-3711.patch

> UI: Classification/Term modal should close after "create/update/delete"  
> response
> -
>
> Key: ATLAS-3711
> URL: https://issues.apache.org/jira/browse/ATLAS-3711
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-3711.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-3713) UI : DSL select count() query doesn't display results on UI

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3713:
--

 Summary: UI : DSL select count() query doesn't display results on 
UI
 Key: ATLAS-3713
 URL: https://issues.apache.org/jira/browse/ATLAS-3713
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 2.1.0, 3.0.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Reopened] (ATLAS-3709) [Business Metadata] Issues with quick search/suggestions in conjunction with Business Metadata attributes

[Keval Bhatt (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt reopened ATLAS-3709:


> [Business Metadata] Issues with quick search/suggestions in conjunction with 
> Business Metadata attributes
> -
>
> Key: ATLAS-3709
> URL: https://issues.apache.org/jira/browse/ATLAS-3709
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Blocker
> Attachments: Screenshot 2020-03-31 at 6.10.14 PM.png, Screenshot 
> 2020-03-31 at 6.15.51 PM.png
>
>
> Quick search and suggestions has been enabled on Business metadata 
> attriibutes as per ATLAS-3675. But they don't seem to work as expected.
> For instance, we can define search weight for each business metadatda 
> attributes. And once these attributes are assigned to entities, attribute 
> values should be listed in suggestions dorp down and the entities should be 
> listed in quick search results.
> Issues observed:
>  # Under a single Business Metadata
>  ## When multiple attributes are defined and added to entities (with the same 
> search weight), quick search and suggestion is working only on the first 
> attribute which is added to the entity. Any attributes (with same weight) 
> which are added to entity later are not listed in suggestions or quick search
>  ## When multiple attributes are defined and added to entities (with the 
> different search weight), quick search and suggestion is working only on the 
> attributes with search weight 10. Even if we first add an attribute to an 
> entity which has search weight=9
>  # Under 2 different Business Metadata
>  ## Quick search and suggestions stops working completely on all the previous 
> attributes as soon as a new Business Metadata is defined.
>  ## Once I assign this newly defined business metadata, it starts working 
> (but again, only for this attribute value)
> Screenshots attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-3709) [Business Metadata] Issues with quick search/suggestions in conjunction with Business Metadata attributes

[Keval Bhatt (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt resolved ATLAS-3709.

Resolution: Fixed

> [Business Metadata] Issues with quick search/suggestions in conjunction with 
> Business Metadata attributes
> -
>
> Key: ATLAS-3709
> URL: https://issues.apache.org/jira/browse/ATLAS-3709
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Blocker
> Attachments: Screenshot 2020-03-31 at 6.10.14 PM.png, Screenshot 
> 2020-03-31 at 6.15.51 PM.png
>
>
> Quick search and suggestions has been enabled on Business metadata 
> attriibutes as per ATLAS-3675. But they don't seem to work as expected.
> For instance, we can define search weight for each business metadatda 
> attributes. And once these attributes are assigned to entities, attribute 
> values should be listed in suggestions dorp down and the entities should be 
> listed in quick search results.
> Issues observed:
>  # Under a single Business Metadata
>  ## When multiple attributes are defined and added to entities (with the same 
> search weight), quick search and suggestion is working only on the first 
> attribute which is added to the entity. Any attributes (with same weight) 
> which are added to entity later are not listed in suggestions or quick search
>  ## When multiple attributes are defined and added to entities (with the 
> different search weight), quick search and suggestion is working only on the 
> attributes with search weight 10. Even if we first add an attribute to an 
> entity which has search weight=9
>  # Under 2 different Business Metadata
>  ## Quick search and suggestions stops working completely on all the previous 
> attributes as soon as a new Business Metadata is defined.
>  ## Once I assign this newly defined business metadata, it starts working 
> (but again, only for this attribute value)
> Screenshots attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (ATLAS-3709) [Business Metadata] Issues with quick search/suggestions in conjunction with Business Metadata attributes

[Keval Bhatt (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt reassigned ATLAS-3709:
--

Assignee: Keval Bhatt

> [Business Metadata] Issues with quick search/suggestions in conjunction with 
> Business Metadata attributes
> -
>
> Key: ATLAS-3709
> URL: https://issues.apache.org/jira/browse/ATLAS-3709
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Blocker
> Attachments: Screenshot 2020-03-31 at 6.10.14 PM.png, Screenshot 
> 2020-03-31 at 6.15.51 PM.png
>
>
> Quick search and suggestions has been enabled on Business metadata 
> attriibutes as per ATLAS-3675. But they don't seem to work as expected.
> For instance, we can define search weight for each business metadatda 
> attributes. And once these attributes are assigned to entities, attribute 
> values should be listed in suggestions dorp down and the entities should be 
> listed in quick search results.
> Issues observed:
>  # Under a single Business Metadata
>  ## When multiple attributes are defined and added to entities (with the same 
> search weight), quick search and suggestion is working only on the first 
> attribute which is added to the entity. Any attributes (with same weight) 
> which are added to entity later are not listed in suggestions or quick search
>  ## When multiple attributes are defined and added to entities (with the 
> different search weight), quick search and suggestion is working only on the 
> attributes with search weight 10. Even if we first add an attribute to an 
> entity which has search weight=9
>  # Under 2 different Business Metadata
>  ## Quick search and suggestions stops working completely on all the previous 
> attributes as soon as a new Business Metadata is defined.
>  ## Once I assign this newly defined business metadata, it starts working 
> (but again, only for this attribute value)
> Screenshots attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)