Re: Planning for Apache Atlas 2.2.0 release

[Umesh Padashetty]

Hi Sidharth

That's an exciting list of new features/optimisations. Looks great to me.

+1 for the release.

On Wed, 28 Jul 2021 at 10:50, Nikhil Bonte <
nikhil.bo...@freestoneinfotech.com> wrote:

> Thanks for volunteering Sidharth!
>
> +1 for the release Apache Atlas 2.2.
>
>
> Regards
> Nikhil P. Bonte
>
>
> On Wed, Jul 28, 2021 at 10:46 AM Ashutosh Mestry 
> wrote:
>
>> Sidharth: Thanks for volunteering!
>>
>>
>>
>> +1 for the release.
>>
>>
>>
>> *~ ashutosh*
>>
>> *Ashutosh Mestry* * . Staff Software Engineer .
>> Cloudera, Inc. . *
>>
>> ...
>>
>> *No hurry, no pause. – Tim Ferriss, Life Hacker, Author*
>>
>>
>>
>>
>>
>> *From: *Sarath Subramanian 
>> *Date: *Tuesday, July 27, 2021 at 10:06 PM
>> *To: *dev@atlas.apache.org 
>> *Cc: *u...@atlas.apache.org 
>> *Subject: *Re: Planning for Apache Atlas 2.2.0 release
>>
>> Thanks for volunteering to release Apache Atlas 2.2
>>
>> +1
>>
>>
>> Thanks,
>> Sarath
>>
>>
>> On Tue, Jul 27, 2021 at 12:11 PM Sidharth Mishra 
>> wrote:
>>
>> > Dear Atlas community,
>> >
>> > Since Apache Atlas 2.1 was released, there are many new features,
>> > improvements and fixes. Here are few features/enhancements since last
>> > release, Apache Atlas 2.1:
>> >
>> > - Introduced Deferred Action - Tag propagation will be handled as
>> > a background process (AtlasTask)
>> >
>> > - Added Re-indexing as JAVA_PATCH
>> >
>> > - Created JavaPatch to add new super types to existing entities
>> >
>> > - Supported for Business Metadata in Atlas Export API
>> >
>> > - Supported HA for admin/task API
>> >
>> > - Enhanced export service to export Terms
>> >
>> > - Added new models and addition attributes to Atlas for Apache
>> > Flink, GCP and ADLS Gen 2
>> >
>> > - Added support to Configure HiveServer2 Hook to send Lineage-only
>> > Messages
>> >
>> > - Improved and enhanced Bulk Glossary Import supporting import
>> > with relations
>> >
>> > - Dependency between Atlas and Kafka Zookeeper removed
>> >
>> > - Improved performance of GraphHelper's guid and status getter
>> methods
>> >
>> > - Added new privilege - "admin-audits" for Atlas Admin Audits
>> > authorization
>> >
>> > - Basic search Improvements - search text with special characters,
>> > optimize pagination
>> >
>> > - Updated free-text search processor to support Elasticsearch
>> >
>> > - Refactored and enhanced Atlas Python Client supporting Python 2.7
>> >
>> > - DSL Search enhancements - Support glossary terms and
>> > relationship, can handle null attribute values, Java Tinkerpop
>> > Traversals instead of GremlinScriptEngine, support search by
>> > classification and its attribute, Caching mechanism for translated dsl
>> > queries
>> >
>> > - Enhanced Export/Import Service to conditionally Support
>> > Simultaneous Operations
>> >
>> > - Enhanced NotificationHookConsumer for Large Message Processing
>> >
>> > - Enhanced Atlas authorization for Add/Update/Remove
>> > classification on entities
>> >
>> > - Provided option to add mandatory attribute to existing entity
>> > definition
>> >
>> > - Fixed Atlas UI to load faster in case of large number of
>> > classifications & entities
>> >
>> > - Updated versions of dependent libraries/components: JanusGraph,
>> > elasticsearch, JQuery, Http core, Http Client, slf4j, log4j, ant,
>> > gremlin, Solr, groovy, netty, Kafka
>> >
>> > There are around 336 plus commits on branch 2.0 and 205 resolved
>> > issues with fix version 2.2.0 after 2.1.0 release.
>> > With these significant improvements in place, it is time for the next
>> > release of Apache Atlas!
>> >
>> > I propose to release Apache Atlas 2.2 by early next month. Please
>> > review and send your comments.
>> >
>> > Regards,
>> > Sidharth
>> >
>>
>

-- 
Thanks,
Umesh

Re: Planning for Apache Atlas 2.2.0 release

[Nikhil Bonte]

Thanks for volunteering Sidharth!

+1 for the release Apache Atlas 2.2.


Regards
Nikhil P. Bonte


On Wed, Jul 28, 2021 at 10:46 AM Ashutosh Mestry 
wrote:

> Sidharth: Thanks for volunteering!
>
>
>
> +1 for the release.
>
>
>
> *~ ashutosh*
>
> *Ashutosh Mestry* * . Staff Software Engineer .
> Cloudera, Inc. . *
>
> ...
>
> *No hurry, no pause. – Tim Ferriss, Life Hacker, Author*
>
>
>
>
>
> *From: *Sarath Subramanian 
> *Date: *Tuesday, July 27, 2021 at 10:06 PM
> *To: *dev@atlas.apache.org 
> *Cc: *u...@atlas.apache.org 
> *Subject: *Re: Planning for Apache Atlas 2.2.0 release
>
> Thanks for volunteering to release Apache Atlas 2.2
>
> +1
>
>
> Thanks,
> Sarath
>
>
> On Tue, Jul 27, 2021 at 12:11 PM Sidharth Mishra 
> wrote:
>
> > Dear Atlas community,
> >
> > Since Apache Atlas 2.1 was released, there are many new features,
> > improvements and fixes. Here are few features/enhancements since last
> > release, Apache Atlas 2.1:
> >
> > - Introduced Deferred Action - Tag propagation will be handled as
> > a background process (AtlasTask)
> >
> > - Added Re-indexing as JAVA_PATCH
> >
> > - Created JavaPatch to add new super types to existing entities
> >
> > - Supported for Business Metadata in Atlas Export API
> >
> > - Supported HA for admin/task API
> >
> > - Enhanced export service to export Terms
> >
> > - Added new models and addition attributes to Atlas for Apache
> > Flink, GCP and ADLS Gen 2
> >
> > - Added support to Configure HiveServer2 Hook to send Lineage-only
> > Messages
> >
> > - Improved and enhanced Bulk Glossary Import supporting import
> > with relations
> >
> > - Dependency between Atlas and Kafka Zookeeper removed
> >
> > - Improved performance of GraphHelper's guid and status getter
> methods
> >
> > - Added new privilege - "admin-audits" for Atlas Admin Audits
> > authorization
> >
> > - Basic search Improvements - search text with special characters,
> > optimize pagination
> >
> > - Updated free-text search processor to support Elasticsearch
> >
> > - Refactored and enhanced Atlas Python Client supporting Python 2.7
> >
> > - DSL Search enhancements - Support glossary terms and
> > relationship, can handle null attribute values, Java Tinkerpop
> > Traversals instead of GremlinScriptEngine, support search by
> > classification and its attribute, Caching mechanism for translated dsl
> > queries
> >
> > - Enhanced Export/Import Service to conditionally Support
> > Simultaneous Operations
> >
> > - Enhanced NotificationHookConsumer for Large Message Processing
> >
> > - Enhanced Atlas authorization for Add/Update/Remove
> > classification on entities
> >
> > - Provided option to add mandatory attribute to existing entity
> > definition
> >
> > - Fixed Atlas UI to load faster in case of large number of
> > classifications & entities
> >
> > - Updated versions of dependent libraries/components: JanusGraph,
> > elasticsearch, JQuery, Http core, Http Client, slf4j, log4j, ant,
> > gremlin, Solr, groovy, netty, Kafka
> >
> > There are around 336 plus commits on branch 2.0 and 205 resolved
> > issues with fix version 2.2.0 after 2.1.0 release.
> > With these significant improvements in place, it is time for the next
> > release of Apache Atlas!
> >
> > I propose to release Apache Atlas 2.2 by early next month. Please
> > review and send your comments.
> >
> > Regards,
> > Sidharth
> >
>

Re: Planning for Apache Atlas 2.2.0 release

[Ashutosh Mestry]

Sidharth: Thanks for volunteering!

+1 for the release.

~ ashutosh
Ashutosh Mestry . Staff Software Engineer . 
Cloudera, Inc. .
...
No hurry, no pause. – Tim Ferriss, Life Hacker, Author


From: Sarath Subramanian 
Date: Tuesday, July 27, 2021 at 10:06 PM
To: dev@atlas.apache.org 
Cc: u...@atlas.apache.org 
Subject: Re: Planning for Apache Atlas 2.2.0 release
Thanks for volunteering to release Apache Atlas 2.2

+1


Thanks,
Sarath


On Tue, Jul 27, 2021 at 12:11 PM Sidharth Mishra 
wrote:

> Dear Atlas community,
>
> Since Apache Atlas 2.1 was released, there are many new features,
> improvements and fixes. Here are few features/enhancements since last
> release, Apache Atlas 2.1:
>
> - Introduced Deferred Action - Tag propagation will be handled as
> a background process (AtlasTask)
>
> - Added Re-indexing as JAVA_PATCH
>
> - Created JavaPatch to add new super types to existing entities
>
> - Supported for Business Metadata in Atlas Export API
>
> - Supported HA for admin/task API
>
> - Enhanced export service to export Terms
>
> - Added new models and addition attributes to Atlas for Apache
> Flink, GCP and ADLS Gen 2
>
> - Added support to Configure HiveServer2 Hook to send Lineage-only
> Messages
>
> - Improved and enhanced Bulk Glossary Import supporting import
> with relations
>
> - Dependency between Atlas and Kafka Zookeeper removed
>
> - Improved performance of GraphHelper's guid and status getter methods
>
> - Added new privilege - "admin-audits" for Atlas Admin Audits
> authorization
>
> - Basic search Improvements - search text with special characters,
> optimize pagination
>
> - Updated free-text search processor to support Elasticsearch
>
> - Refactored and enhanced Atlas Python Client supporting Python 2.7
>
> - DSL Search enhancements - Support glossary terms and
> relationship, can handle null attribute values, Java Tinkerpop
> Traversals instead of GremlinScriptEngine, support search by
> classification and its attribute, Caching mechanism for translated dsl
> queries
>
> - Enhanced Export/Import Service to conditionally Support
> Simultaneous Operations
>
> - Enhanced NotificationHookConsumer for Large Message Processing
>
> - Enhanced Atlas authorization for Add/Update/Remove
> classification on entities
>
> - Provided option to add mandatory attribute to existing entity
> definition
>
> - Fixed Atlas UI to load faster in case of large number of
> classifications & entities
>
> - Updated versions of dependent libraries/components: JanusGraph,
> elasticsearch, JQuery, Http core, Http Client, slf4j, log4j, ant,
> gremlin, Solr, groovy, netty, Kafka
>
> There are around 336 plus commits on branch 2.0 and 205 resolved
> issues with fix version 2.2.0 after 2.1.0 release.
> With these significant improvements in place, it is time for the next
> release of Apache Atlas!
>
> I propose to release Apache Atlas 2.2 by early next month. Please
> review and send your comments.
>
> Regards,
> Sidharth
>

Re: Planning for Apache Atlas 2.2.0 release

[Sarath Subramanian]

Thanks for volunteering to release Apache Atlas 2.2

+1


Thanks,
Sarath


On Tue, Jul 27, 2021 at 12:11 PM Sidharth Mishra 
wrote:

> Dear Atlas community,
>
> Since Apache Atlas 2.1 was released, there are many new features,
> improvements and fixes. Here are few features/enhancements since last
> release, Apache Atlas 2.1:
>
> - Introduced Deferred Action - Tag propagation will be handled as
> a background process (AtlasTask)
>
> - Added Re-indexing as JAVA_PATCH
>
> - Created JavaPatch to add new super types to existing entities
>
> - Supported for Business Metadata in Atlas Export API
>
> - Supported HA for admin/task API
>
> - Enhanced export service to export Terms
>
> - Added new models and addition attributes to Atlas for Apache
> Flink, GCP and ADLS Gen 2
>
> - Added support to Configure HiveServer2 Hook to send Lineage-only
> Messages
>
> - Improved and enhanced Bulk Glossary Import supporting import
> with relations
>
> - Dependency between Atlas and Kafka Zookeeper removed
>
> - Improved performance of GraphHelper's guid and status getter methods
>
> - Added new privilege - "admin-audits" for Atlas Admin Audits
> authorization
>
> - Basic search Improvements - search text with special characters,
> optimize pagination
>
> - Updated free-text search processor to support Elasticsearch
>
> - Refactored and enhanced Atlas Python Client supporting Python 2.7
>
> - DSL Search enhancements - Support glossary terms and
> relationship, can handle null attribute values, Java Tinkerpop
> Traversals instead of GremlinScriptEngine, support search by
> classification and its attribute, Caching mechanism for translated dsl
> queries
>
> - Enhanced Export/Import Service to conditionally Support
> Simultaneous Operations
>
> - Enhanced NotificationHookConsumer for Large Message Processing
>
> - Enhanced Atlas authorization for Add/Update/Remove
> classification on entities
>
> - Provided option to add mandatory attribute to existing entity
> definition
>
> - Fixed Atlas UI to load faster in case of large number of
> classifications & entities
>
> - Updated versions of dependent libraries/components: JanusGraph,
> elasticsearch, JQuery, Http core, Http Client, slf4j, log4j, ant,
> gremlin, Solr, groovy, netty, Kafka
>
> There are around 336 plus commits on branch 2.0 and 205 resolved
> issues with fix version 2.2.0 after 2.1.0 release.
> With these significant improvements in place, it is time for the next
> release of Apache Atlas!
>
> I propose to release Apache Atlas 2.2 by early next month. Please
> review and send your comments.
>
> Regards,
> Sidharth
>

Re: Review Request 73492: ATLAS-4372: Upgrade nimbus-jose-jwt to 9.8.1

[Ashutosh Mestry via Review Board]

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


Ship it!




Ship It!

- Ashutosh Mestry


On July 27, 2021, 9:01 p.m., Disha Talreja wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73492/
> ---
> 
> (Updated July 27, 2021, 9:01 p.m.)
> 
> 
> Review request for atlas, Radhika Kundam and Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Atlas is currently pulling in nimbus-jose-jwt 5.4. This patch upgrades it to 
> 9.8.1.
> 
> 
> Diffs
> -
> 
>   webapp/pom.xml ccbcc3141 
> 
> 
> Diff: https://reviews.apache.org/r/73492/diff/1/
> 
> 
> Testing
> ---
> 
> mvn clean -DskipTests install 
> mvn clean -DskipTests package -Pdist,embedded-hbase-solr 
> Atlas server running.
> PC Build: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/774/
> 
> 
> Thanks,
> 
> Disha Talreja
> 
>

[jira] [Commented] (ATLAS-4340) Set Solr wait-searcher property to false by default to make Solr commits async

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4340:


Commit f08a4078cb30aaf0c34ea376f6c00bb2e3cac94c in atlas's branch 
refs/heads/branch-2.0 from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f08a407 ]

ATLAS-4340: Set Solr wait-searcher property to false by default to make Solr 
commits async

(cherry picked from commit a7ac64d54954064be6b0f56c04f05bbe128772d5)


> Set Solr wait-searcher property to false by default to make Solr commits async
> --
>
> Key: ATLAS-4340
> URL: https://issues.apache.org/jira/browse/ATLAS-4340
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>  Labels: perfomance, solr
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4340-001.patch
>
>
>  In Atlas when a transaction is committed, the entries are committed to HBase 
> (primary storage) and Solr (indexing storage). A transaction is rolled-back 
> if the primary storage commit fails, on the other hand when the secondary 
> commit fails (solr), the transaction is not-rolled back and logged as warning 
> and it is recommended to use reindex to repair the missing index documents. 
> This behavior is due to the fact that the primary storage is the source of 
> truth and indexes can be rebuild.
> In Janusgraph, there is a property for Solr to make solr commits async. This 
> is set to *true* in Atlas making every commit to wait until the solr commit 
> is successful. This will have a negative impact on performance and is 
> recommended to be false by default.
> Property: *index.[X].solr.wait-searcher*
> |When mutating - wait for the index to reflect new mutations before 
> returning. This can have a negative impact on performance.|
>  
> This Jira is about setting the default value for above property to FALSE and 
> can be overridden if need arises. 
> The solution should use the _StandardTransactionLogProcessor_ provided within 
> JanusGraph to track failures to indexes (secondary storage in JanusGraph 
> parlance) during commit. Using this would provide recovery mechanism in case 
> of failures during transaction commit.



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

[jira] [Commented] (ATLAS-4340) Set Solr wait-searcher property to false by default to make Solr commits async

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4340:


Commit a7ac64d54954064be6b0f56c04f05bbe128772d5 in atlas's branch 
refs/heads/master from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a7ac64d ]

ATLAS-4340: Set Solr wait-searcher property to false by default to make Solr 
commits async


> Set Solr wait-searcher property to false by default to make Solr commits async
> --
>
> Key: ATLAS-4340
> URL: https://issues.apache.org/jira/browse/ATLAS-4340
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>  Labels: perfomance, solr
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4340-001.patch
>
>
>  In Atlas when a transaction is committed, the entries are committed to HBase 
> (primary storage) and Solr (indexing storage). A transaction is rolled-back 
> if the primary storage commit fails, on the other hand when the secondary 
> commit fails (solr), the transaction is not-rolled back and logged as warning 
> and it is recommended to use reindex to repair the missing index documents. 
> This behavior is due to the fact that the primary storage is the source of 
> truth and indexes can be rebuild.
> In Janusgraph, there is a property for Solr to make solr commits async. This 
> is set to *true* in Atlas making every commit to wait until the solr commit 
> is successful. This will have a negative impact on performance and is 
> recommended to be false by default.
> Property: *index.[X].solr.wait-searcher*
> |When mutating - wait for the index to reflect new mutations before 
> returning. This can have a negative impact on performance.|
>  
> This Jira is about setting the default value for above property to FALSE and 
> can be overridden if need arises. 
> The solution should use the _StandardTransactionLogProcessor_ provided within 
> JanusGraph to track failures to indexes (secondary storage in JanusGraph 
> parlance) during commit. Using this would provide recovery mechanism in case 
> of failures during transaction commit.



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

Re: Review Request 73430: ATLAS-4340: Set Solr wait-searcher property to false by default to make Solr commits async

[Ashutosh Mestry via Review Board]

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


Ship it!




Ship It!

- Ashutosh Mestry


On July 27, 2021, 6:32 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73430/
> ---
> 
> (Updated July 27, 2021, 6:32 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
> Nikhil Bonte, and Pinal Shah.
> 
> 
> Bugs: ATLAS-4340
> https://issues.apache.org/jira/browse/ATLAS-4340
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> In Atlas when a transaction is committed, the entries are committed to HBase 
> (primary storage) and Solr (indexing storage). A transaction is rolled-back 
> if the primary storage commit fails, on the other hand when the secondary 
> commit fails (solr), the transaction is not-rolled back and logged as warning 
> and it is recommended to use reindex to repair the missing index documents. 
> This behavior is due to the fact that the primary storage is the source of 
> truth and indexes can be rebuild.
> 
> In Janusgraph, there is a property for Solr to make solr commits async. This 
> is set to true in Atlas making every commit to wait until the solr commit is 
> successful. This will have a negative impact on performance and is 
> recommended to be false by default.
> 
> Property: index.[X].solr.wait-searcher
> 
> When mutating - wait for the index to reflect new mutations before returning. 
> This can have a negative impact on performance.
>  
> 
> This Jira is about setting the default value for above property to FALSE and 
> can be overridden if need arises.
> 
> 
> Diffs
> -
> 
>   addons/falcon-bridge/src/test/resources/atlas-application.properties 
> 898b69c99 
>   addons/hbase-bridge/src/test/resources/atlas-application.properties 
> 898b69c99 
>   addons/kafka-bridge/src/test/resources/atlas-application.properties 
> 91fd8b092 
>   authorization/src/test/resources/atlas-application.properties 2e02678a6 
>   distro/pom.xml d84f5e7b1 
>   distro/src/bin/atlas_config.py 493a34ad8 
>   distro/src/bin/atlas_start.py 7cf35a92a 
>   distro/src/test/python/scripts/TestMetadata.py 662fbddba 
>   graphdb/janus/src/test/resources/atlas-application.properties a355234e9 
>   intg/src/main/java/org/apache/atlas/ApplicationProperties.java bf97ab146 
>   intg/src/test/resources/atlas-application.properties 50ce01e70 
>   webapp/src/test/resources/atlas-application.properties 1d45e78f3 
> 
> 
> Diff: https://reviews.apache.org/r/73430/diff/2/
> 
> 
> Testing
> ---
> 
> 1. Precommit Test: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/688/
> 2. Build Atlas with embedded Hbase/Solr profile and validated basic sanity 
> tests - running quick start, basic search, tag propagation
> 3. Performance Test details:
> 
> 
> Run with default settings - Solr wait-searcher property enabled - true 
> (without patch)
> --
> Start Time : Tue Jun 15 22:26:58 PDT 2021
> End Time   : Fri Jun 18 02:32:34 PDT 2021
> Messages Processed : 91,225
> Time Taken : 52 hours 5 mins
> Rate   : ~ 29.2 messages/minute
> 
> 
> Run with disabled Solr wait-searcher property (will improve solr commit time 
> making it async) - with patch
> ---
> Start Time : Mon Jun 14 13:30:04 PDT 2021
> End Time   : Tue Jun 15 17:23:56 PDT 2021
> Messages Processed : 91,225
> Time Taken : 27 hours 54 mins
> Rate   : ~ 54.5 messages/minute
> 
> 
> We see almost 50% perf imrpovement with this change.
> 
> Precommit (updated): 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/772/console
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 73430: ATLAS-4340: Set Solr wait-searcher property to false by default to make Solr commits async

[Ashutosh Mestry via Review Board]

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




distro/src/bin/atlas_start.py
Line 113 (original), 113 (patched)


nit: What is the reason for CRLF?



intg/src/main/java/org/apache/atlas/ApplicationProperties.java
Line 346 (original), 346 (patched)


This comment is no longer relevant.


- Ashutosh Mestry


On July 27, 2021, 6:32 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73430/
> ---
> 
> (Updated July 27, 2021, 6:32 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
> Nikhil Bonte, and Pinal Shah.
> 
> 
> Bugs: ATLAS-4340
> https://issues.apache.org/jira/browse/ATLAS-4340
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> In Atlas when a transaction is committed, the entries are committed to HBase 
> (primary storage) and Solr (indexing storage). A transaction is rolled-back 
> if the primary storage commit fails, on the other hand when the secondary 
> commit fails (solr), the transaction is not-rolled back and logged as warning 
> and it is recommended to use reindex to repair the missing index documents. 
> This behavior is due to the fact that the primary storage is the source of 
> truth and indexes can be rebuild.
> 
> In Janusgraph, there is a property for Solr to make solr commits async. This 
> is set to true in Atlas making every commit to wait until the solr commit is 
> successful. This will have a negative impact on performance and is 
> recommended to be false by default.
> 
> Property: index.[X].solr.wait-searcher
> 
> When mutating - wait for the index to reflect new mutations before returning. 
> This can have a negative impact on performance.
>  
> 
> This Jira is about setting the default value for above property to FALSE and 
> can be overridden if need arises.
> 
> 
> Diffs
> -
> 
>   addons/falcon-bridge/src/test/resources/atlas-application.properties 
> 898b69c99 
>   addons/hbase-bridge/src/test/resources/atlas-application.properties 
> 898b69c99 
>   addons/kafka-bridge/src/test/resources/atlas-application.properties 
> 91fd8b092 
>   authorization/src/test/resources/atlas-application.properties 2e02678a6 
>   distro/pom.xml d84f5e7b1 
>   distro/src/bin/atlas_config.py 493a34ad8 
>   distro/src/bin/atlas_start.py 7cf35a92a 
>   distro/src/test/python/scripts/TestMetadata.py 662fbddba 
>   graphdb/janus/src/test/resources/atlas-application.properties a355234e9 
>   intg/src/main/java/org/apache/atlas/ApplicationProperties.java bf97ab146 
>   intg/src/test/resources/atlas-application.properties 50ce01e70 
>   webapp/src/test/resources/atlas-application.properties 1d45e78f3 
> 
> 
> Diff: https://reviews.apache.org/r/73430/diff/2/
> 
> 
> Testing
> ---
> 
> 1. Precommit Test: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/688/
> 2. Build Atlas with embedded Hbase/Solr profile and validated basic sanity 
> tests - running quick start, basic search, tag propagation
> 3. Performance Test details:
> 
> 
> Run with default settings - Solr wait-searcher property enabled - true 
> (without patch)
> --
> Start Time : Tue Jun 15 22:26:58 PDT 2021
> End Time   : Fri Jun 18 02:32:34 PDT 2021
> Messages Processed : 91,225
> Time Taken : 52 hours 5 mins
> Rate   : ~ 29.2 messages/minute
> 
> 
> Run with disabled Solr wait-searcher property (will improve solr commit time 
> making it async) - with patch
> ---
> Start Time : Mon Jun 14 13:30:04 PDT 2021
> End Time   : Tue Jun 15 17:23:56 PDT 2021
> Messages Processed : 91,225
> Time Taken : 27 hours 54 mins
> Rate   : ~ 54.5 messages/minute
> 
> 
> We see almost 50% perf imrpovement with this change.
> 
> Precommit (updated): 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/772/console
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Review Request 73492: ATLAS-4372: Upgrade nimbus-jose-jwt to 9.8.1

[Disha Talreja via Review Board]

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

Review request for atlas, Radhika Kundam and Sarath Subramanian.


Repository: atlas


Description
---

Atlas is currently pulling in nimbus-jose-jwt 5.4. This patch upgrades it to 
9.8.1.


Diffs
-

  webapp/pom.xml ccbcc3141 


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


Testing
---

mvn clean -DskipTests install 
mvn clean -DskipTests package -Pdist,embedded-hbase-solr 
Atlas server running.


Thanks,

Disha Talreja

Re: Review Request 73478: ATLAS-4368: Upgrade elasticsearch version to 6.8.15

[Disha Talreja via Review Board]

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

(Updated July 27, 2021, 8:45 p.m.)


Review request for atlas, Ashutosh Mestry, Radhika Kundam, Sarath Subramanian, 
and Sidharth Mishra.


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


Repository: atlas


Description
---

Currently Atlas is pulling in Elasticsearch 6.8.14
this patch upgrades Elasticsearch version to 6.8.15


Diffs
-

  pom.xml 19db43146 


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


Testing (updated)
---

mvn clean -DskipTests install 
mvn clean -DskipTests package -Pdist,embedded-hbase-solr 
Atlas server running.
PC Build: 
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/767/


Thanks,

Disha Talreja

Re: Planning for Apache Atlas 2.2.0 release

[Jean-Baptiste Onofré]

Hi,

It sounds good to me.

Thanks for the proposal.

Regards
JB

On 7/27/21 9:11 PM, Sidharth Mishra wrote:

Dear Atlas community,

Since Apache Atlas 2.1 was released, there are many new features,
improvements and fixes. Here are few features/enhancements since last
release, Apache Atlas 2.1:

 - Introduced Deferred Action - Tag propagation will be handled as
a background process (AtlasTask)

 - Added Re-indexing as JAVA_PATCH

 - Created JavaPatch to add new super types to existing entities

 - Supported for Business Metadata in Atlas Export API

 - Supported HA for admin/task API

 - Enhanced export service to export Terms

 - Added new models and addition attributes to Atlas for Apache
Flink, GCP and ADLS Gen 2

 - Added support to Configure HiveServer2 Hook to send Lineage-only Messages

 - Improved and enhanced Bulk Glossary Import supporting import
with relations

 - Dependency between Atlas and Kafka Zookeeper removed

 - Improved performance of GraphHelper's guid and status getter methods

 - Added new privilege - "admin-audits" for Atlas Admin Audits authorization

 - Basic search Improvements - search text with special characters,
optimize pagination

 - Updated free-text search processor to support Elasticsearch

 - Refactored and enhanced Atlas Python Client supporting Python 2.7

 - DSL Search enhancements - Support glossary terms and
relationship, can handle null attribute values, Java Tinkerpop
Traversals instead of GremlinScriptEngine, support search by
classification and its attribute, Caching mechanism for translated dsl
queries

 - Enhanced Export/Import Service to conditionally Support
Simultaneous Operations

 - Enhanced NotificationHookConsumer for Large Message Processing

 - Enhanced Atlas authorization for Add/Update/Remove
classification on entities

 - Provided option to add mandatory attribute to existing entity definition

 - Fixed Atlas UI to load faster in case of large number of
classifications & entities

 - Updated versions of dependent libraries/components: JanusGraph,
elasticsearch, JQuery, Http core, Http Client, slf4j, log4j, ant,
gremlin, Solr, groovy, netty, Kafka

There are around 336 plus commits on branch 2.0 and 205 resolved
issues with fix version 2.2.0 after 2.1.0 release.
With these significant improvements in place, it is time for the next
release of Apache Atlas!

I propose to release Apache Atlas 2.2 by early next month. Please
review and send your comments.

Regards,
Sidharth



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Planning for Apache Atlas 2.2.0 release

[Sidharth Mishra]

Dear Atlas community,

Since Apache Atlas 2.1 was released, there are many new features,
improvements and fixes. Here are few features/enhancements since last
release, Apache Atlas 2.1:

- Introduced Deferred Action - Tag propagation will be handled as
a background process (AtlasTask)

- Added Re-indexing as JAVA_PATCH

- Created JavaPatch to add new super types to existing entities

- Supported for Business Metadata in Atlas Export API

- Supported HA for admin/task API

- Enhanced export service to export Terms

- Added new models and addition attributes to Atlas for Apache
Flink, GCP and ADLS Gen 2

- Added support to Configure HiveServer2 Hook to send Lineage-only Messages

- Improved and enhanced Bulk Glossary Import supporting import
with relations

- Dependency between Atlas and Kafka Zookeeper removed

- Improved performance of GraphHelper's guid and status getter methods

- Added new privilege - "admin-audits" for Atlas Admin Audits authorization

- Basic search Improvements - search text with special characters,
optimize pagination

- Updated free-text search processor to support Elasticsearch

- Refactored and enhanced Atlas Python Client supporting Python 2.7

- DSL Search enhancements - Support glossary terms and
relationship, can handle null attribute values, Java Tinkerpop
Traversals instead of GremlinScriptEngine, support search by
classification and its attribute, Caching mechanism for translated dsl
queries

- Enhanced Export/Import Service to conditionally Support
Simultaneous Operations

- Enhanced NotificationHookConsumer for Large Message Processing

- Enhanced Atlas authorization for Add/Update/Remove
classification on entities

- Provided option to add mandatory attribute to existing entity definition

- Fixed Atlas UI to load faster in case of large number of
classifications & entities

- Updated versions of dependent libraries/components: JanusGraph,
elasticsearch, JQuery, Http core, Http Client, slf4j, log4j, ant,
gremlin, Solr, groovy, netty, Kafka

There are around 336 plus commits on branch 2.0 and 205 resolved
issues with fix version 2.2.0 after 2.1.0 release.
With these significant improvements in place, it is time for the next
release of Apache Atlas!

I propose to release Apache Atlas 2.2 by early next month. Please
review and send your comments.

Regards,
Sidharth

[jira] [Comment Edited] (ATLAS-4324) FS entity created for load data inpath is created as shell entity

[Radhika Kundam (Jira)]

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

Radhika Kundam edited comment on ATLAS-4324 at 7/27/21, 6:55 PM:
-

With this patch we are including Path entities to be retained at HS2 
ActiveEntityfilter. And also provided configuration option at Hive Hook to add 
any entity types (comma separated)to be retained.

config property is : 
*atlas.hook.hive.hs2.filter.entity.additional.types.to.retain**=,*

 


was (Author: radhikak):
With this patch we are including Path entities to be retained at HS2 
ActiveEntityfilter. And also provided configuration option at Hive Hook to add 
any entity types (comma separated)to be retained.

config property is : 
*atlas.hook.hive.hs2.filter.entity.types.to.retain=,*

 

> FS entity created for load data inpath is created as shell entity
> -
>
> Key: ATLAS-4324
> URL: https://issues.apache.org/jira/browse/ATLAS-4324
> Project: Atlas
>  Issue Type: Bug
>  Components: hive-integration
>Affects Versions: 2.1.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>  Labels: hive-hooks
> Fix For: 3.0.0, 2.2.0
>
> Attachments: load_data_shell_entity.png
>
>
> beeline >
> create external table default.hive_table_cloud_load_data_in_path_123 
> (student_roll int, student_name string, student_dob date) ROW FORMAT 
> DELIMITED FIELDS TERMINATED BY ' ' STORED AS TEXTFILE location 
> 'hdfs://ns1/tmp/hive_table_cloud_load_data_in_path_123'
>  
> load data inpath 'hdfs://ns1/tmp/data123.txt' into table 
> hive_table_cloud_load_data_in_path_123;
>  
> Creates 'hdfs://ns1/tmp/data123.txt' as shell entity. 



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

Re: Review Request 73430: ATLAS-4340: Set Solr wait-searcher property to false by default to make Solr commits async

[Sarath Subramanian]

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

(Updated July 27, 2021, 11:32 a.m.)


Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
Nikhil Bonte, and Pinal Shah.


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


Repository: atlas


Description
---

In Atlas when a transaction is committed, the entries are committed to HBase 
(primary storage) and Solr (indexing storage). A transaction is rolled-back if 
the primary storage commit fails, on the other hand when the secondary commit 
fails (solr), the transaction is not-rolled back and logged as warning and it 
is recommended to use reindex to repair the missing index documents. This 
behavior is due to the fact that the primary storage is the source of truth and 
indexes can be rebuild.

In Janusgraph, there is a property for Solr to make solr commits async. This is 
set to true in Atlas making every commit to wait until the solr commit is 
successful. This will have a negative impact on performance and is recommended 
to be false by default.

Property: index.[X].solr.wait-searcher

When mutating - wait for the index to reflect new mutations before returning. 
This can have a negative impact on performance.
 

This Jira is about setting the default value for above property to FALSE and 
can be overridden if need arises.


Diffs (updated)
-

  addons/falcon-bridge/src/test/resources/atlas-application.properties 
898b69c99 
  addons/hbase-bridge/src/test/resources/atlas-application.properties 898b69c99 
  addons/kafka-bridge/src/test/resources/atlas-application.properties 91fd8b092 
  authorization/src/test/resources/atlas-application.properties 2e02678a6 
  distro/pom.xml d84f5e7b1 
  distro/src/bin/atlas_config.py 493a34ad8 
  distro/src/bin/atlas_start.py 7cf35a92a 
  distro/src/test/python/scripts/TestMetadata.py 662fbddba 
  graphdb/janus/src/test/resources/atlas-application.properties a355234e9 
  intg/src/main/java/org/apache/atlas/ApplicationProperties.java bf97ab146 
  intg/src/test/resources/atlas-application.properties 50ce01e70 
  webapp/src/test/resources/atlas-application.properties 1d45e78f3 


Diff: https://reviews.apache.org/r/73430/diff/2/

Changes: https://reviews.apache.org/r/73430/diff/1-2/


Testing
---

1. Precommit Test: 
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/688/
2. Build Atlas with embedded Hbase/Solr profile and validated basic sanity 
tests - running quick start, basic search, tag propagation
3. Performance Test details:


Run with default settings - Solr wait-searcher property enabled - true (without 
patch)
--
Start Time : Tue Jun 15 22:26:58 PDT 2021
End Time   : Fri Jun 18 02:32:34 PDT 2021
Messages Processed : 91,225
Time Taken : 52 hours 5 mins
Rate   : ~ 29.2 messages/minute


Run with disabled Solr wait-searcher property (will improve solr commit time 
making it async) - with patch
---
Start Time : Mon Jun 14 13:30:04 PDT 2021
End Time   : Tue Jun 15 17:23:56 PDT 2021
Messages Processed : 91,225
Time Taken : 27 hours 54 mins
Rate   : ~ 54.5 messages/minute


We see almost 50% perf imrpovement with this change.


Thanks,

Sarath Subramanian

[jira] [Commented] (ATLAS-4324) FS entity created for load data inpath is created as shell entity

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4324:


Commit 0cc6ae84a759886486ef2446a87aa4f63d11d6db in atlas's branch 
refs/heads/branch-2.0 from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=0cc6ae8 ]

ATLAS-4324: FS entity created for load data inpath is created as shell entity - 
adding ozone_key

Signed-off-by: Sarath Subramanian 
(cherry picked from commit 98c6cea0140d64761542e603532d13127a0524b4)


> FS entity created for load data inpath is created as shell entity
> -
>
> Key: ATLAS-4324
> URL: https://issues.apache.org/jira/browse/ATLAS-4324
> Project: Atlas
>  Issue Type: Bug
>  Components: hive-integration
>Affects Versions: 2.1.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>  Labels: hive-hooks
> Fix For: 3.0.0, 2.2.0
>
> Attachments: load_data_shell_entity.png
>
>
> beeline >
> create external table default.hive_table_cloud_load_data_in_path_123 
> (student_roll int, student_name string, student_dob date) ROW FORMAT 
> DELIMITED FIELDS TERMINATED BY ' ' STORED AS TEXTFILE location 
> 'hdfs://ns1/tmp/hive_table_cloud_load_data_in_path_123'
>  
> load data inpath 'hdfs://ns1/tmp/data123.txt' into table 
> hive_table_cloud_load_data_in_path_123;
>  
> Creates 'hdfs://ns1/tmp/data123.txt' as shell entity. 



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

[jira] [Commented] (ATLAS-4324) FS entity created for load data inpath is created as shell entity

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4324:


Commit 98c6cea0140d64761542e603532d13127a0524b4 in atlas's branch 
refs/heads/master from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=98c6cea ]

ATLAS-4324: FS entity created for load data inpath is created as shell entity - 
adding ozone_key

Signed-off-by: Sarath Subramanian 


> FS entity created for load data inpath is created as shell entity
> -
>
> Key: ATLAS-4324
> URL: https://issues.apache.org/jira/browse/ATLAS-4324
> Project: Atlas
>  Issue Type: Bug
>  Components: hive-integration
>Affects Versions: 2.1.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>  Labels: hive-hooks
> Fix For: 3.0.0, 2.2.0
>
> Attachments: load_data_shell_entity.png
>
>
> beeline >
> create external table default.hive_table_cloud_load_data_in_path_123 
> (student_roll int, student_name string, student_dob date) ROW FORMAT 
> DELIMITED FIELDS TERMINATED BY ' ' STORED AS TEXTFILE location 
> 'hdfs://ns1/tmp/hive_table_cloud_load_data_in_path_123'
>  
> load data inpath 'hdfs://ns1/tmp/data123.txt' into table 
> hive_table_cloud_load_data_in_path_123;
>  
> Creates 'hdfs://ns1/tmp/data123.txt' as shell entity. 



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

[jira] [Created] (ATLAS-4374) [Send lineage only information] When a ctas table is created, there is an additional notification sent by hive

[Dharshana M Krishnamoorthy (Jira)]

Dharshana M Krishnamoorthy created ATLAS-4374:
-

 Summary: [Send lineage only information] When a ctas table is 
created, there is an additional notification sent by hive
 Key: ATLAS-4374
 URL: https://issues.apache.org/jira/browse/ATLAS-4374
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Dharshana M Krishnamoorthy
 Attachments: Screenshot 2021-07-27 at 3.06.59 PM.png, Screenshot 
2021-07-27 at 3.22.47 PM.png

*Scenario*: 
create a table and create a ctas table from it
*Expectation*:
There has to be only 1 notification from hive with *ENTITY_CREATE_V2* type

*Observation*:
There are 2 notifications
one with *ENTITY_CREATE_V2* and other with *ENTITY_PARTIAL_UPDATE_V2*

{code:java}
 
{"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgSourceIP":"172.27.202.195","msgCreatedBy":"hive","msgCreationTime":1627372412791,"spooled":false,"message":{"type":"ENTITY_PARTIAL_UPDATE_V2","user":"hive","entityId":{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"db_mtkns.ctas_table_vwsci@cm"}},"entity":{"entity":{"typeName":"hive_table","attributes":{"parameters":{"numRows":"0","rawDataSize":"0","transient_lastDdlTime":"1627372412","bucketing_version":"2","numFilesErasureCoded":"0","totalSize":"0","transactional_properties":"default","COLUMN_STATS_ACCURATE":"{\"BASIC_STATS\":\"true\"}","numFiles":"0","transactional":"true"}},"isIncomplete":false,"provenanceType":0,"version":0,"proxy":false
{"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgSourceIP":"172.27.202.195","msgCreatedBy":"hive","msgCreationTime":1627372412906,"spooled":false,"message":{"type":"ENTITY_CREATE_V2","user":"hrt_qa","entities":{"referredEntities":{},"entities":[{"typeName":"hive_table_ddl","attributes":{"serviceType":"hive","qualifiedName":"db_mtkns.ctas_table_vwsci@cm:1627372386732","execTime":1627372386732,"queryText":"create
 table db_mtkns.ctas_table_vwsci as select * from 
db_mtkns.table_gmqnw","name":"create table db_mtkns.ctas_table_vwsci as select 
* from 
db_mtkns.table_gmqnw","userName":"hrt_qa"},"guid":"-7790679096914344","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"table":{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"db_mtkns.ctas_table_vwsci@cm"},"relationshipType":"hive_table_ddl_queries"}},"proxy":false},{"typeName":"hive_process","attributes":{"recentQueries":["create
 table db_mtkns.ctas_table_vwsci as select * from 
db_mtkns.table_gmqnw"],"qualifiedName":"db_mtkns.ctas_table_vwsci@cm:1627372412000","clusterName":"cm","name":"db_mtkns.ctas_table_vwsci@cm:1627372412000","queryText":"","operationType":"CREATETABLE_AS_SELECT","startTime":1627372412905,"queryPlan":"Not
 
Supported","endTime":1627372412905,"userName":"","queryId":""},"guid":"-7790679096914345","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"outputs":[{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"db_mtkns.ctas_table_vwsci@cm"},"relationshipType":"process_dataset_outputs"}],"inputs":[{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"db_mtkns.table_gmqnw@cm"},"relationshipType":"dataset_process_inputs"}]},"proxy":false},{"typeName":"hive_process_execution","attributes":{"hostName":"quasar-eotkek-5.quasar-eotkek.root.hwx.site","qualifiedName":"db_mtkns.ctas_table_vwsci@cm:1627372412000:1627372386732:1627372412905","name":"db_mtkns.ctas_table_vwsci@cm:1627372412000:1627372386732:1627372412905","queryText":"create
 table db_mtkns.ctas_table_vwsci as select * from 
db_mtkns.table_gmqnw","startTime":1627372386732,"queryPlan":"Not 

[jira] [Updated] (ATLAS-4374) [Send lineage only information] When a ctas table is created, there is an additional notification sent by hive

[Dharshana M Krishnamoorthy (Jira)]

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

Dharshana M Krishnamoorthy updated ATLAS-4374:
--
Attachment: Screenshot 2021-07-27 at 3.06.59 PM.png

> [Send lineage only information] When a ctas table is created, there is an 
> additional notification sent by hive
> --
>
> Key: ATLAS-4374
> URL: https://issues.apache.org/jira/browse/ATLAS-4374
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
> Attachments: Screenshot 2021-07-27 at 3.06.59 PM.png, Screenshot 
> 2021-07-27 at 3.22.47 PM.png
>
>
> *Scenario*: 
> create a table and create a ctas table from it
> *Expectation*:
> There has to be only 1 notification from hive with *ENTITY_CREATE_V2* type
> *Observation*:
> There are 2 notifications
> one with *ENTITY_CREATE_V2* and other with *ENTITY_PARTIAL_UPDATE_V2*
> {code:java}
>  
> {"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgSourceIP":"172.27.202.195","msgCreatedBy":"hive","msgCreationTime":1627372412791,"spooled":false,"message":{"type":"ENTITY_PARTIAL_UPDATE_V2","user":"hive","entityId":{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"db_mtkns.ctas_table_vwsci@cm"}},"entity":{"entity":{"typeName":"hive_table","attributes":{"parameters":{"numRows":"0","rawDataSize":"0","transient_lastDdlTime":"1627372412","bucketing_version":"2","numFilesErasureCoded":"0","totalSize":"0","transactional_properties":"default","COLUMN_STATS_ACCURATE":"{\"BASIC_STATS\":\"true\"}","numFiles":"0","transactional":"true"}},"isIncomplete":false,"provenanceType":0,"version":0,"proxy":false
> {"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgSourceIP":"172.27.202.195","msgCreatedBy":"hive","msgCreationTime":1627372412906,"spooled":false,"message":{"type":"ENTITY_CREATE_V2","user":"hrt_qa","entities":{"referredEntities":{},"entities":[{"typeName":"hive_table_ddl","attributes":{"serviceType":"hive","qualifiedName":"db_mtkns.ctas_table_vwsci@cm:1627372386732","execTime":1627372386732,"queryText":"create
>  table db_mtkns.ctas_table_vwsci as select * from 
> db_mtkns.table_gmqnw","name":"create table db_mtkns.ctas_table_vwsci as 
> select * from 
> db_mtkns.table_gmqnw","userName":"hrt_qa"},"guid":"-7790679096914344","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"table":{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"db_mtkns.ctas_table_vwsci@cm"},"relationshipType":"hive_table_ddl_queries"}},"proxy":false},{"typeName":"hive_process","attributes":{"recentQueries":["create
>  table db_mtkns.ctas_table_vwsci as select * from 
> db_mtkns.table_gmqnw"],"qualifiedName":"db_mtkns.ctas_table_vwsci@cm:1627372412000","clusterName":"cm","name":"db_mtkns.ctas_table_vwsci@cm:1627372412000","queryText":"","operationType":"CREATETABLE_AS_SELECT","startTime":1627372412905,"queryPlan":"Not
>  
> Supported","endTime":1627372412905,"userName":"","queryId":""},"guid":"-7790679096914345","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"outputs":[{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"db_mtkns.ctas_table_vwsci@cm"},"relationshipType":"process_dataset_outputs"}],"inputs":[{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"db_mtkns.table_gmqnw@cm"},"relationshipType":"dataset_process_inputs"}]},"proxy":false},{"typeName":"hive_process_execution","attributes":{"hostName":"quasar-eotkek-5.quasar-eotkek.root.hwx.site","qualifiedName":"db_mtkns.ctas_table_vwsci@cm:1627372412000:1627372386732:1627372412905","name":"db_mtkns.ctas_table_vwsci@cm:1627372412000:1627372386732:1627372412905","queryText":"create
>  table db_mtkns.ctas_table_vwsci as select * from 
> db_mtkns.table_gmqnw","startTime":1627372386732,"queryPlan":"Not 
> 

[jira] [Updated] (ATLAS-3935) Use Audit framework to capture audit entries for Import/Export operations

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-3935:
---
Fix Version/s: 2.2.0
   3.0.0

> Use Audit framework to capture audit entries for Import/Export operations
> -
>
> Key: ATLAS-3935
> URL: https://issues.apache.org/jira/browse/ATLAS-3935
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3935-V2.patch, ATLAS-3935-V3.patch
>
>
> By using Audit Framework, capture audit entries for Import/Export operations.
> These audit entries can be seen under the "Audits" tab of Admin section.
> *Add Import and Export specific information in Audit entry*
> * Total no. of entities imported/ exported
> * Total no. of entities imported/ exported of specific TypeDef
> * Export operation Fetch Type



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

[jira] [Updated] (ATLAS-3957) Use Audit framework to capture audit entries for "Server Start" and "Server In Active mode" (HA)

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-3957:
---
Fix Version/s: 2.2.0
   3.0.0

> Use Audit framework to capture audit entries for "Server Start" and "Server 
> In Active mode" (HA)
> 
>
> Key: ATLAS-3957
> URL: https://issues.apache.org/jira/browse/ATLAS-3957
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3957-V3.patch, ATLAS-3957.patch
>
>
> By using Audit Framework, capture audit entries for "Server Start" and 
> "Server In Active mode" (HA)
> These audit entries can be seen under the "Audits" tab of Admin section.



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

[jira] [Updated] (ATLAS-3984) Add UI Date Timezone and UI Date Format in Session api

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-3984:
---
Fix Version/s: 2.2.0
   3.0.0

> Add UI Date Timezone and UI Date Format in Session api
> --
>
> Key: ATLAS-3984
> URL: https://issues.apache.org/jira/browse/ATLAS-3984
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3984-V2.patch
>
>
> Add UI Date Timezone and UI Date Format in Session api.
> Provide a way to user to read these "UI Date Timezone" and "UI Date Format" 
> values from property file.



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

[jira] [Updated] (ATLAS-4034) Export operation audit with result count 0 for empty exports is inconsistent

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-4034:
---
Fix Version/s: 2.2.0
   3.0.0

> Export operation audit with result count 0 for empty exports is inconsistent
> 
>
> Key: ATLAS-4034
> URL: https://issues.apache.org/jira/browse/ATLAS-4034
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4034-ATLAS-4041.patch
>
>
> Export operation creates an audit with *count 0* for the following request:
> {code:java}
> {
>  "itemsToExport": [
>  
>  ]
> }
> {code}
> But the following input does not create any audit entry : Please note the 
> *{}* in the *itemsToExport* array
> {code:java}
> {
>  "itemsToExport": [
>    {}
>  ]
> }
>  {code}
> We need to keep the result consistent. Either create entry for the later with 
> result count 0 or do not create an entry for the former



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

[jira] [Updated] (ATLAS-4041) It will be good to have the operation status info of EXPORT operation in the Admin export audits

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-4041:
---
Fix Version/s: 2.2.0
   3.0.0

> It will be good to have the operation status info of EXPORT operation in the 
> Admin export audits
> 
>
> Key: ATLAS-4041
> URL: https://issues.apache.org/jira/browse/ATLAS-4041
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4034-ATLAS-4041.patch
>
>
> Currently we do not have information if the export operation is "PASS" or 
> "FAIL" or "PARTIAL_PASS"
> It will be good to have this information
> Current output:
> {code}
>  {
>  "guid": "",
>  "userName": "",
>  "operation": "EXPORT",
>  "params": "\{\"fetchType\":\"FULL\",\"matchType\":\"startsWith\"}",
>  "startTime": 1605089955917,
>  "endTime": 1605089957959,
>  "clientId": "",
>  "result": "\{\"hdfs_path\":1,\"dharshana\":1,\"hive_db\":1}",
>  "resultCount": 3
>  }
> {code}



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

[jira] [Updated] (ATLAS-4135) [Atlas: Glossary Term Bulk Import] It will be good to ignore the glossaries and terms that are already present instead of failing the bulk import

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-4135:
---
Fix Version/s: 2.2.0
   3.0.0

> [Atlas: Glossary Term Bulk Import] It will be good to ignore the glossaries 
> and terms that are already present instead of failing the bulk import
> -
>
> Key: ATLAS-4135
> URL: https://issues.apache.org/jira/browse/ATLAS-4135
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4135-ATLAS-4139.patch, Screenshot 2021-02-04 at 
> 7.06.56 PM.png
>
>
> Consider the following scenario:
> Already available glossaries and terms:
> glossary_1 ==> term_1
> glossary_1 ==> term_2
> glossary_2 ==> term_1
> glossary_2 ==> term_2
>  
> Now if the user is performing a bulk import and if glossary_1 ==> term_1 is 
> part of the input, currently the call fails.
> {code:java}
> {errorCode: "ATLAS-500-00-016", errorMessage: "Error occurred while creating 
> glossary term: {0}",…}errorCause: "Glossary term with qualifiedName 
> term_1@aglossary_01 already exists"errorCode: "ATLAS-500-00-016"errorMessage: 
> "Error occurred while creating glossary term: {0}" {code}
> Expectation:
> If it already exists, then just update the other field values eg, long 
> description and the linked terms and do not fail
>  



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

[jira] [Updated] (ATLAS-4139) [Atlas: Glossary Term Bulk Import] When AdditionalAttributes is not provided in key:value format, the error message does not convey that

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-4139:
---
Fix Version/s: 2.2.0
   3.0.0

> [Atlas: Glossary Term Bulk Import] When AdditionalAttributes is not provided 
> in key:value format, the error message does not convey that
> 
>
> Key: ATLAS-4139
> URL: https://issues.apache.org/jira/browse/ATLAS-4139
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4139.patch, Screenshot 2021-02-05 at 4.07.46 PM.png
>
>
> Consider the following input for bulk import term_glossary
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1, "glossary_1 term_1 short description", "glossary_1 term_1 
> long description", "Examples", "AB", "glossary_1 term_1 Usage", "random_key"
>  {code}
> Here *AdditionalAttributes* is *random_key*
> When this is imported we get
> {code:java}
> errorCode: "ATLAS-500-00-001"errorMessage: "The uploaded file has not been 
> processed due to the following errors : ↵[↵The Data in the uploaded file is 
> incorrectly specified  : random_key]" {code}
> It mentions The Data in the uploaded file is incorrectly specified : 
> random_key
> It would be good to convey as "AdditionalAttributes has to a key:value pair" 
> or something similar



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

[jira] [Updated] (ATLAS-4146) [Atlas: Glossary] On updating the related terms, UI allows the user to add the already added term

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-4146:
---
Fix Version/s: 2.2.0
   3.0.0

> [Atlas: Glossary] On updating the related terms, UI allows the user to add 
> the already added term
> -
>
> Key: ATLAS-4146
> URL: https://issues.apache.org/jira/browse/ATLAS-4146
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4146.patch, Screen Recording 2021-02-05 at 6.50.31 
> PM.mov
>
>
> Steps to repro:
>  # Create a glossary(glossary_1) and a few terms (term_1, term_2, term_3, 
> term_4, term_5)
>  # Click on term_1 and add related terms "alsoSee"
>  # Choose term_5 of glossary_1
>  # Provide inputs and assign
>  # term_5 will be added as a related term
>  # Now, add one more related term and choose the same term_5 of glossary_1 
> [UI allows this]
>  # Provide new input and assign
>  # The assignment will be successful
> This makes the user think, that term_5 with new data is saved. But that is 
> not the case, only old data is present
> Expectation:
> Do not allow the user to assign the same term again.
> If allowed, update the data with the new data
> [^Screen Recording 2021-02-05 at 6.50.31 PM.mov]



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

[jira] [Updated] (ATLAS-4150) UI : __AtlasAuditEntry appearing in metrics window

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-4150:
---
Fix Version/s: 2.2.0
   3.0.0

> UI : __AtlasAuditEntry appearing in metrics window
> --
>
> Key: ATLAS-4150
> URL: https://issues.apache.org/jira/browse/ATLAS-4150
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Mandar Ambawane
>Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4150.patch, Screenshot from 2021-02-09 10-38-46.png
>
>
> !Screenshot from 2021-02-09 10-38-46.png|width=584,height=432!
> As seen in the above screenshot, entries for AtlasAuditEntry are visible. 
> That is an system internal entity and should ideally not be visible in the 
> metrics UI.



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

[jira] [Commented] (ATLAS-4359) UI: Misalignment in Searchweight tooltip text in business metadata

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4359:


Commit 32b8fe3cd5a3582d5a02bbb6a038ca2f60dbb7c6 in atlas's branch 
refs/heads/branch-2.0 from prasad pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=32b8fe3 ]

ATLAS-4359:UI: Misalignment in Searchweight tooltip text in business 
metadata,fixed

(cherry picked from commit 9a5c5c5a39bbc5167127e25bf243c8cf93d81971)


> UI: Misalignment in Searchweight tooltip text in business metadata
> --
>
> Key: ATLAS-4359
> URL: https://issues.apache.org/jira/browse/ATLAS-4359
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4359-UI-Misalignment-in-Searchweight-tooltip-t.patch
>
>
> When you hover over the tooltip (?) for searchweight in the page for editing 
> business metadata, there is misalignment in the text explaining the 
> searchweight ranges.



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

[jira] [Commented] (ATLAS-4360) UI: Misalignment of placeholder text in labels, enum attributes and classification fields in Chrome

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4360:


Commit 21dc7f5713e113ea811e6714e299911724289693 in atlas's branch 
refs/heads/branch-2.0 from prasad pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=21dc7f5 ]

ATLAS-4360:UI: Misalignment of placeholder text in labels, enum attributes and 
classification fields in Chrome, fixed

(cherry picked from commit e9c99739010b451638ad90773ca8d36e86fd2841)


> UI: Misalignment of placeholder text in labels, enum attributes and 
> classification fields in Chrome
> ---
>
> Key: ATLAS-4360
> URL: https://issues.apache.org/jira/browse/ATLAS-4360
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4360-UI-Misalignment-of-placeholder-text-in-la.patch
>
>
> While adding label in entity detail page, or while creating enumeration 
> attributes and  while selecting parent classification, if one erases all the 
> values entered, then the placeholder text gets misaligned as in the attached 
> video.[^Global_issue.webm]



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

[jira] [Commented] (ATLAS-4356) UI: Unusual behaviour after clicking back button on business metadata

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4356:


Commit 3626be1a72083c5e2ce6fdee6e3135a03d774a06 in atlas's branch 
refs/heads/branch-2.0 from prasad pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3626be1 ]

ATLAS-4356:#1 UI: Unusual behaviour after clicking back button on business 
metadata, fixed

Signed-off-by: nixonrodrigues 
(cherry picked from commit b667943ff5217e8dc328dbd7f41c2c89199a78dd)


> UI: Unusual behaviour after clicking back button on business metadata
> -
>
> Key: ATLAS-4356
> URL: https://issues.apache.org/jira/browse/ATLAS-4356
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments: 
> 0001-ATLAS-4356-1-UI-Unusual-behaviour-after-clicking-bac.patch
>
>
> 1. Go to Admin->Administration
>  2. In Business Metadata, click on any existing Business metadata.
>  3. Click the (<) back button next to the title of the Business metadata
>  4. Perform a search in basic search
>  5. Click on Admin->Administration
> You will see that the details of the previous business metadata are still 
> open. It goes away after clicking on Administration again. But it again comes 
> back if you do another search and then click on Administration again.
>  
> This issue occurs in new UI only.



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

[jira] [Commented] (ATLAS-4356) UI: Unusual behaviour after clicking back button on business metadata

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4356:


Commit b667943ff5217e8dc328dbd7f41c2c89199a78dd in atlas's branch 
refs/heads/master from prasad pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b667943 ]

ATLAS-4356:#1 UI: Unusual behaviour after clicking back button on business 
metadata, fixed

Signed-off-by: nixonrodrigues 


> UI: Unusual behaviour after clicking back button on business metadata
> -
>
> Key: ATLAS-4356
> URL: https://issues.apache.org/jira/browse/ATLAS-4356
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments: 
> 0001-ATLAS-4356-1-UI-Unusual-behaviour-after-clicking-bac.patch
>
>
> 1. Go to Admin->Administration
>  2. In Business Metadata, click on any existing Business metadata.
>  3. Click the (<) back button next to the title of the Business metadata
>  4. Perform a search in basic search
>  5. Click on Admin->Administration
> You will see that the details of the previous business metadata are still 
> open. It goes away after clicking on Administration again. But it again comes 
> back if you do another search and then click on Administration again.
>  
> This issue occurs in new UI only.



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

[jira] [Commented] (ATLAS-4360) UI: Misalignment of placeholder text in labels, enum attributes and classification fields in Chrome

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4360:


Commit e9c99739010b451638ad90773ca8d36e86fd2841 in atlas's branch 
refs/heads/master from prasad pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e9c9973 ]

ATLAS-4360:UI: Misalignment of placeholder text in labels, enum attributes and 
classification fields in Chrome, fixed


> UI: Misalignment of placeholder text in labels, enum attributes and 
> classification fields in Chrome
> ---
>
> Key: ATLAS-4360
> URL: https://issues.apache.org/jira/browse/ATLAS-4360
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4360-UI-Misalignment-of-placeholder-text-in-la.patch
>
>
> While adding label in entity detail page, or while creating enumeration 
> attributes and  while selecting parent classification, if one erases all the 
> values entered, then the placeholder text gets misaligned as in the attached 
> video.[^Global_issue.webm]



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

[jira] [Commented] (ATLAS-4359) UI: Misalignment in Searchweight tooltip text in business metadata

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-4359:


Commit 9a5c5c5a39bbc5167127e25bf243c8cf93d81971 in atlas's branch 
refs/heads/master from prasad pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9a5c5c5 ]

ATLAS-4359:UI: Misalignment in Searchweight tooltip text in business 
metadata,fixed


> UI: Misalignment in Searchweight tooltip text in business metadata
> --
>
> Key: ATLAS-4359
> URL: https://issues.apache.org/jira/browse/ATLAS-4359
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4359-UI-Misalignment-in-Searchweight-tooltip-t.patch
>
>
> When you hover over the tooltip (?) for searchweight in the page for editing 
> business metadata, there is misalignment in the text explaining the 
> searchweight ranges.



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

[jira] [Updated] (ATLAS-4095) DSL Search : __isIncomplete System Attribute returns incorrect results or throws error

[Pinal (Jira)]

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

Pinal updated ATLAS-4095:
-
Fix Version/s: 2.2.0
   3.0.0

> DSL Search : __isIncomplete System Attribute returns incorrect results or 
> throws error
> --
>
> Key: ATLAS-4095
> URL: https://issues.apache.org/jira/browse/ATLAS-4095
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: DSL
> Fix For: 3.0.0, 2.2.0
>
>
> With DSL search having __isIncomplete System attribute in where clause, it 
> returns empty results.
> Ex: Table where __isIncomplete = false
> Workaround: Need to map boolean value to integer value before querying. Also 
> need to handle check for the presence of attribute.  



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

[jira] [Updated] (ATLAS-4088) Quick Search: Unable to get Aggregation Metric when query text is empty

[Pinal (Jira)]

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

Pinal updated ATLAS-4088:
-
Fix Version/s: 2.2.0
   3.0.0

> Quick Search: Unable to get Aggregation Metric when query text is empty
> ---
>
> Key: ATLAS-4088
> URL: https://issues.apache.org/jira/browse/ATLAS-4088
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: quicksearch
> Fix For: 3.0.0, 2.2.0
>
>
> In case the query text is passed as empty string ,
> [/api/atlas/v2/search/quick?typeName=hive_table=|http://localhost:21000/api/atlas/v2/search/quick?typeName=hive_table=]
>  the aggregation metrics in the response does not contain any information 
> like owners, state of the asset, etc.



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

[jira] [Updated] (ATLAS-4057) DSL Search : Support glossary terms and relationships

[Pinal (Jira)]

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

Pinal updated ATLAS-4057:
-
Fix Version/s: 2.2.0
   3.0.0

> DSL Search : Support glossary terms and relationships
> -
>
> Key: ATLAS-4057
> URL: https://issues.apache.org/jira/browse/ATLAS-4057
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: DSL
> Fix For: 3.0.0, 2.2.0
>
>
> Supporting glossary term in advanced search, will allow user to search the 
> entities which are assigned to particular term.
>  
> 'hasTerm' keyword is added to support glossary term.
> User needs to add fully qualifiedName of glossary term.
>  
> Example queries to search with glossary terms:
> hive_table hasTerm "modernTrade@salesGlossary",
> hive_table hasTerm "modernTrade@salesGlossary" and hive_table isA Dimension
>  
> Example queries to search with relationship:
> hive_table where db.name = "sales"



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

[jira] [Updated] (ATLAS-4332) DSL Query : query with like operator and "/" in search text throws 500

[Pinal (Jira)]

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

Pinal updated ATLAS-4332:
-
Fix Version/s: (was: 2.1.0)
   2.2.0

> DSL Query : query with like operator and "/" in search text throws 500
> --
>
> Key: ATLAS-4332
> URL: https://issues.apache.org/jira/browse/ATLAS-4332
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal
>Priority: Major
>  Labels: AdvancedSearch
> Fix For: 3.0.0, 2.2.0
>
>
> hdfs_path name="/warehouse/tablespace/external/hive/db_fdchj.db" returns 
> right entity.
> hdfs_path name like "/warehouse/*" throws following exception: 



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

[jira] [Updated] (ATLAS-4254) Basic Search : Optimize pagination

[Pinal (Jira)]

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

Pinal updated ATLAS-4254:
-
Fix Version/s: 2.2.0
   3.0.0

> Basic Search : Optimize pagination
> --
>
> Key: ATLAS-4254
> URL: https://issues.apache.org/jira/browse/ATLAS-4254
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 3.0.0, 2.2.0
>
>
> *Current Working of Pagination*
>  * When user specifies page information i.e offset and limit in the request, 
> except some condition, offset is reset to 0
>  * Query is then executed from 0 offset and limit
>  * Filter out the results obtained from query
>  * Generate result set by skipping the results from 0 to the given offset
> *New Working Structure*
>  * New Parameter 'marker' (String) has been introduced in SearchParameters 
> which will have encrypted string as value.
>  * The marker should be  set as '*' for the start of the page
>  * The response of above request (AtlasSearchResult) will have 'nextMarker' 
> field which will have encrypted String which is to be passed as value of 
> 'marker' in the subsequent request
>  * if marker is set then offset should not be greater than 0
> *Improvement*
>  * It will increase performance of the basic search 
>  



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