[jira] [Commented] (ATLAS-2856) add utility method to find earliest active request in Atlas server
[ https://issues.apache.org/jira/browse/ATLAS-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599526#comment-16599526 ] ASF subversion and git services commented on ATLAS-2856: Commit f2e714550a1bb30f7a7b4fbea5688225b628a4bc in atlas's branch refs/heads/branch-0.8 from [~mad...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=f2e7145 ] ATLAS-2856: added utility methods to RequestContext, to find number of active requests and earliest active request-time > add utility method to find earliest active request in Atlas server > -- > > Key: ATLAS-2856 > URL: https://issues.apache.org/jira/browse/ATLAS-2856 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > > RequestContext class captures context for the current request (i.e. REST API > call, Notification processing) in a thread-local. An utility method is needed > in this class to find the earliest active request - to be used in incremental > export feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68593: ATLAS-2856: added utility methods to RequestContext, to find number of active requests and earliest active request-time
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68593/#review208212 --- Ship it! Ship It! - Abhay Kulkarni On Aug. 31, 2018, 11:31 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68593/ > --- > > (Updated Aug. 31, 2018, 11:31 p.m.) > > > Review request for atlas, Apoorv Naik, Ashutosh Mestry, Abhay Kulkarni, and > Sarath Subramanian. > > > Bugs: ATLAS-2856 > https://issues.apache.org/jira/browse/ATLAS-2856 > > > Repository: atlas > > > Description > --- > > added utility methods in RequestContext and RequestContextV1, to find number > of active requests and earliest active request-time > > > Diffs > - > > > repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1Test.java > 35d1a74da > server-api/src/main/java/org/apache/atlas/RequestContext.java 3b2b575a6 > server-api/src/main/java/org/apache/atlas/RequestContextV1.java 8506d1869 > > > Diff: https://reviews.apache.org/r/68593/diff/1/ > > > Testing > --- > > Pre-commit test run: > https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/649 > > > Thanks, > > Madhan Neethiraj > >
Re: Review Request 68593: ATLAS-2856: added utility methods to RequestContext, to find number of active requests and earliest active request-time
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68593/#review208209 --- Ship it! Ship It! - Sarath Subramanian On Aug. 31, 2018, 4:31 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68593/ > --- > > (Updated Aug. 31, 2018, 4:31 p.m.) > > > Review request for atlas, Apoorv Naik, Ashutosh Mestry, Abhay Kulkarni, and > Sarath Subramanian. > > > Bugs: ATLAS-2856 > https://issues.apache.org/jira/browse/ATLAS-2856 > > > Repository: atlas > > > Description > --- > > added utility methods in RequestContext and RequestContextV1, to find number > of active requests and earliest active request-time > > > Diffs > - > > > repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1Test.java > 35d1a74da > server-api/src/main/java/org/apache/atlas/RequestContext.java 3b2b575a6 > server-api/src/main/java/org/apache/atlas/RequestContextV1.java 8506d1869 > > > Diff: https://reviews.apache.org/r/68593/diff/1/ > > > Testing > --- > > Pre-commit test run: > https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/649 > > > Thanks, > > Madhan Neethiraj > >
Re: Review Request 68580: ATLAS-2851: Retrieving entity with SET attribute contains duplicate entries if attribute type updated from LIST to SET
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68580/#review208208 --- Ship it! Ship It! - Madhan Neethiraj On Aug. 31, 2018, 11:06 p.m., Sarath Subramanian wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68580/ > --- > > (Updated Aug. 31, 2018, 11:06 p.m.) > > > Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj. > > > Bugs: ATLAS-2851 > https://issues.apache.org/jira/browse/ATLAS-2851 > > > Repository: atlas > > > Description > --- > > Retrieving entity with SET attribute type contains duplicate entries if > attribute type updated from LIST to SET > > > Diffs > - > > repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java > b4189d2d1 > > repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java > c57e30ab5 > > repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java > 0d9cb05ca > > repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java > 5a863b733 > > > Diff: https://reviews.apache.org/r/68580/diff/2/ > > > Testing > --- > > Validated that SET attributes returns unique values even if graph store > contains duplicate value for the attribute. > > > Thanks, > > Sarath Subramanian > >
Review Request 68593: ATLAS-2856: added utility methods to RequestContext, to find number of active requests and earliest active request-time
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68593/ --- Review request for atlas, Apoorv Naik, Ashutosh Mestry, Abhay Kulkarni, and Sarath Subramanian. Bugs: ATLAS-2856 https://issues.apache.org/jira/browse/ATLAS-2856 Repository: atlas Description --- added utility methods in RequestContext and RequestContextV1, to find number of active requests and earliest active request-time Diffs - repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1Test.java 35d1a74da server-api/src/main/java/org/apache/atlas/RequestContext.java 3b2b575a6 server-api/src/main/java/org/apache/atlas/RequestContextV1.java 8506d1869 Diff: https://reviews.apache.org/r/68593/diff/1/ Testing --- Pre-commit test run: https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/649 Thanks, Madhan Neethiraj
[jira] [Created] (ATLAS-2856) add utility method to find earliest active request in Atlas server
Madhan Neethiraj created ATLAS-2856: --- Summary: add utility method to find earliest active request in Atlas server Key: ATLAS-2856 URL: https://issues.apache.org/jira/browse/ATLAS-2856 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj RequestContext class captures context for the current request (i.e. REST API call, Notification processing) in a thread-local. An utility method is needed in this class to find the earliest active request - to be used in incremental export feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68580: ATLAS-2851: Retrieving entity with SET attribute contains duplicate entries if attribute type updated from LIST to SET
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68580/ --- (Updated Aug. 31, 2018, 4:06 p.m.) Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj. Bugs: ATLAS-2851 https://issues.apache.org/jira/browse/ATLAS-2851 Repository: atlas Description --- Retrieving entity with SET attribute type contains duplicate entries if attribute type updated from LIST to SET Diffs (updated) - repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java b4189d2d1 repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java c57e30ab5 repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java 0d9cb05ca repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java 5a863b733 Diff: https://reviews.apache.org/r/68580/diff/2/ Changes: https://reviews.apache.org/r/68580/diff/1-2/ Testing --- Validated that SET attributes returns unique values even if graph store contains duplicate value for the attribute. Thanks, Sarath Subramanian
[jira] [Updated] (ATLAS-2794) Ensure that Atlas REST client uses JacksonJsonProvider from com.fasterxml.jackson package
[ https://issues.apache.org/jira/browse/ATLAS-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2794: Fix Version/s: 0.8.3 > Ensure that Atlas REST client uses JacksonJsonProvider from > com.fasterxml.jackson package > - > > Key: ATLAS-2794 > URL: https://issues.apache.org/jira/browse/ATLAS-2794 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Abhay Kulkarni >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2794.patch > > > In order that Ranger REST client and Atlas REST client co-exist in tagsync > process, each client needs to ensure that it explicitly uses > JacksonJsonProvider of its choice when initializing respective REST clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2794) Ensure that Atlas REST client uses JacksonJsonProvider from com.fasterxml.jackson package
[ https://issues.apache.org/jira/browse/ATLAS-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599243#comment-16599243 ] ASF subversion and git services commented on ATLAS-2794: Commit c5c4742b72d6f7a5e26135f54bd67a2141890595 in atlas's branch refs/heads/branch-0.8 from [~mad...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=c5c4742 ] ATLAS-2794: updated AtlasClient to explicitly specify JacksonJaxbJsonProvider (cherry picked from commit 9097d695c5509b874c86e0eae159cecf2a812de8) (cherry picked from commit 50c3adf1519cb3d4d01ea86c2e90e1bba4df3c46) > Ensure that Atlas REST client uses JacksonJsonProvider from > com.fasterxml.jackson package > - > > Key: ATLAS-2794 > URL: https://issues.apache.org/jira/browse/ATLAS-2794 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Abhay Kulkarni >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2794.patch > > > In order that Ranger REST client and Atlas REST client co-exist in tagsync > process, each client needs to ensure that it explicitly uses > JacksonJsonProvider of its choice when initializing respective REST clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68584: ATLAS-2853: updated to send entity-notifications after successful graph transaction commit
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68584/#review208186 --- Ship it! Ship It! - Sarath Subramanian On Aug. 31, 2018, 9:12 a.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68584/ > --- > > (Updated Aug. 31, 2018, 9:12 a.m.) > > > Review request for atlas, Apoorv Naik, Ashutosh Mestry, Graham Wallis, keval > bhatt, Nixon Rodrigues, and Sarath Subramanian. > > > Bugs: ATLAS-2853 > https://issues.apache.org/jira/browse/ATLAS-2853 > > > Repository: atlas > > > Description > --- > > updated to send entity notifications only after graph transaction is committed > > > Diffs > - > > > repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java > 783d62fb3 > > webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java > c70011f24 > > webapp/src/main/java/org/apache/atlas/notification/EntityNotificationSender.java > PRE-CREATION > > webapp/src/main/java/org/apache/atlas/notification/NotificationEntityChangeListener.java > 1eeecefc1 > > > Diff: https://reviews.apache.org/r/68584/diff/2/ > > > Testing > --- > > Verified that the notifications are sent post transaction commit. > > Pre-commit test run: > https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/645 > > > Thanks, > > Madhan Neethiraj > >
[jira] [Commented] (ATLAS-2844) Add timestamp in EntityNotification
[ https://issues.apache.org/jira/browse/ATLAS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599022#comment-16599022 ] ASF subversion and git services commented on ATLAS-2844: Commit 4eb4120514963442ea328bae50bdedf15cca049c in atlas's branch refs/heads/branch-1.0 from [~mad...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=4eb4120 ] ATLAS-2844: added eventTime field in EntityNotificationV2 (cherry picked from commit 96f2c2996e6e3ccfd26e0297be5f29640a2ec781) > Add timestamp in EntityNotification > --- > > Key: ATLAS-2844 > URL: https://issues.apache.org/jira/browse/ATLAS-2844 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Madhan Neethiraj >Priority: Minor > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2844.patch > > > If we add a timestamp to the EntityNotification it will allow a consumer of > the notification to accurately specify the time that the event occurred, even > after publication and subsequent consume through Kafka topic. This would > improve precision. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2844) Add timestamp in EntityNotification
[ https://issues.apache.org/jira/browse/ATLAS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599020#comment-16599020 ] ASF subversion and git services commented on ATLAS-2844: Commit 96f2c2996e6e3ccfd26e0297be5f29640a2ec781 in atlas's branch refs/heads/master from [~mad...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=96f2c29 ] ATLAS-2844: added eventTime field in EntityNotificationV2 > Add timestamp in EntityNotification > --- > > Key: ATLAS-2844 > URL: https://issues.apache.org/jira/browse/ATLAS-2844 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Madhan Neethiraj >Priority: Minor > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2844.patch > > > If we add a timestamp to the EntityNotification it will allow a consumer of > the notification to accurately specify the time that the event occurred, even > after publication and subsequent consume through Kafka topic. This would > improve precision. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2853) Entity notifications to be sent after transaction commit
[ https://issues.apache.org/jira/browse/ATLAS-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2853: Fix Version/s: (was: 0.8.3) > Entity notifications to be sent after transaction commit > > > Key: ATLAS-2853 > URL: https://issues.apache.org/jira/browse/ATLAS-2853 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2853.patch > > > Currently, notification on entity changes (create/update/delete entities, > add/update/remove classifications on entities) are sent before the changes > are committed in the database. If commit fails, the entity state seen by > notification receivers would be different from Atlas. To avoid this, Atlas > server should entity notifications only after the transaction is committed to > the database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2853) Entity notifications to be sent after transaction commit
[ https://issues.apache.org/jira/browse/ATLAS-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598999#comment-16598999 ] ASF subversion and git services commented on ATLAS-2853: Commit e576b763a21ae3089e80a1448aaef9e9a678fcb8 in atlas's branch refs/heads/branch-1.0 from [~mad...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=e576b76 ] ATLAS-2853: updated to send entity-notifications after successful graph transaction commit (cherry picked from commit 56eefb2a9806265df997dda2ef70274eede72675) > Entity notifications to be sent after transaction commit > > > Key: ATLAS-2853 > URL: https://issues.apache.org/jira/browse/ATLAS-2853 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2853.patch > > > Currently, notification on entity changes (create/update/delete entities, > add/update/remove classifications on entities) are sent before the changes > are committed in the database. If commit fails, the entity state seen by > notification receivers would be different from Atlas. To avoid this, Atlas > server should entity notifications only after the transaction is committed to > the database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2853) Entity notifications to be sent after transaction commit
[ https://issues.apache.org/jira/browse/ATLAS-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598995#comment-16598995 ] ASF subversion and git services commented on ATLAS-2853: Commit 56eefb2a9806265df997dda2ef70274eede72675 in atlas's branch refs/heads/master from [~mad...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=56eefb2 ] ATLAS-2853: updated to send entity-notifications after successful graph transaction commit > Entity notifications to be sent after transaction commit > > > Key: ATLAS-2853 > URL: https://issues.apache.org/jira/browse/ATLAS-2853 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2853.patch > > > Currently, notification on entity changes (create/update/delete entities, > add/update/remove classifications on entities) are sent before the changes > are committed in the database. If commit fails, the entity state seen by > notification receivers would be different from Atlas. To avoid this, Atlas > server should entity notifications only after the transaction is committed to > the database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68583: ATLAS-2844: added eventTime field in EntityNotificationV2
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68583/#review208182
---
Ship it!
Ship It!
- Apoorv Naik
On Aug. 30, 2018, 10:52 p.m., Madhan Neethiraj wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68583/
> ---
>
> (Updated Aug. 30, 2018, 10:52 p.m.)
>
>
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Graham Wallis, and
> Sarath Subramanian.
>
>
> Bugs: ATLAS-2844
> https://issues.apache.org/jira/browse/ATLAS-2844
>
>
> Repository: atlas
>
>
> Description
> ---
>
> updated EntityNotificationV2 with addition of 'eventTime' attribute. Here is
> a sample notification message with this change:
>
> {
> "type":"ENTITY_NOTIFICATION_V2",
> "entity": {"typeName":"hive_table",
> "attributes":{"owner":"hive",
>"createTime":1535622192000,
>"qualifiedName":"test.testtbl2@cl1",
>"name":"testtbl2"},
> "guid":"8bc1ba7b-3c76-4311-81ae-c05fd07d667b",
> "status":"ACTIVE",
> "displayText":"testtbl2"
> },
> "operationType":"ENTITY_CREATE",
> "eventTime":1535622192647
> }
>
>
> Diffs
> -
>
>
> intg/src/main/java/org/apache/atlas/model/notification/EntityNotification.java
> 6cdae8925
>
> webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java
> c70011f24
>
>
> Diff: https://reviews.apache.org/r/68583/diff/1/
>
>
> Testing
> ---
>
> Verified that the notification includes eventTime attribute - as shown above.
>
>
> Thanks,
>
> Madhan Neethiraj
>
>
Re: Review Request 68584: ATLAS-2853: updated to send entity-notifications after successful graph transaction commit
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68584/#review208181 --- Ship it! Ship It! - Apoorv Naik On Aug. 31, 2018, 4:12 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68584/ > --- > > (Updated Aug. 31, 2018, 4:12 p.m.) > > > Review request for atlas, Apoorv Naik, Ashutosh Mestry, Graham Wallis, keval > bhatt, Nixon Rodrigues, and Sarath Subramanian. > > > Bugs: ATLAS-2853 > https://issues.apache.org/jira/browse/ATLAS-2853 > > > Repository: atlas > > > Description > --- > > updated to send entity notifications only after graph transaction is committed > > > Diffs > - > > > repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java > 783d62fb3 > > webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java > c70011f24 > > webapp/src/main/java/org/apache/atlas/notification/EntityNotificationSender.java > PRE-CREATION > > webapp/src/main/java/org/apache/atlas/notification/NotificationEntityChangeListener.java > 1eeecefc1 > > > Diff: https://reviews.apache.org/r/68584/diff/2/ > > > Testing > --- > > Verified that the notifications are sent post transaction commit. > > Pre-commit test run: > https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/645 > > > Thanks, > > Madhan Neethiraj > >
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598991#comment-16598991 ] Nigel Jones commented on ATLAS-1773: Fixup patch removed as no longer relevant given changes (omrs->egeria, latest 1773 patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-31.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nigel Jones updated ATLAS-1773: --- Attachment: (was: ATLAS-1799-nigel-fixup-20180718a,.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-31.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
HBase hook for atlas
Hai Team, I am Manikandan,Working as a data engineer in one of the MNC. I am trying to connect My Hbase database with Atlas to manage the metadata of hbase tables and columns.The problem is i can able to fetch only the data's from Hive and not from Hbase.i did so much R and i could not find any related to this. i am in need of your help. Could you guys guide me on setting up the environment to fetch the Hbase column family,column qualifier from Hbase and display it on Atlas UI My cluster details are, Hortonworks HDP 2.6.4.9 Atlas 0.8 Thanks in advance. Regards, Manikandan
Re: Review Request 68584: ATLAS-2853: updated to send entity-notifications after successful graph transaction commit
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68584/#review208161 --- Ship it! Elegant fix - thanks Madhan. Once this is committed I will modify the OMRS event mapper. - Graham Wallis On Aug. 31, 2018, 4:12 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68584/ > --- > > (Updated Aug. 31, 2018, 4:12 p.m.) > > > Review request for atlas, Apoorv Naik, Ashutosh Mestry, Graham Wallis, keval > bhatt, Nixon Rodrigues, and Sarath Subramanian. > > > Bugs: ATLAS-2853 > https://issues.apache.org/jira/browse/ATLAS-2853 > > > Repository: atlas > > > Description > --- > > updated to send entity notifications only after graph transaction is committed > > > Diffs > - > > > repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java > 783d62fb3 > > webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java > c70011f24 > > webapp/src/main/java/org/apache/atlas/notification/EntityNotificationSender.java > PRE-CREATION > > webapp/src/main/java/org/apache/atlas/notification/NotificationEntityChangeListener.java > 1eeecefc1 > > > Diff: https://reviews.apache.org/r/68584/diff/2/ > > > Testing > --- > > Verified that the notifications are sent post transaction commit. > > Pre-commit test run: > https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/645 > > > Thanks, > > Madhan Neethiraj > >
Re: Review Request 68584: ATLAS-2853: updated to send entity-notifications after successful graph transaction commit
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68584/ --- (Updated Aug. 31, 2018, 4:11 p.m.) Review request for atlas, Apoorv Naik, Ashutosh Mestry, keval bhatt, Nixon Rodrigues, and Sarath Subramanian. Changes --- updated to extend post-commit notificaiton sending for V1 notificaitons as well Bugs: ATLAS-2853 https://issues.apache.org/jira/browse/ATLAS-2853 Repository: atlas Description --- updated to send entity notifications only after graph transaction is committed Diffs (updated) - repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java 783d62fb3 webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java c70011f24 webapp/src/main/java/org/apache/atlas/notification/EntityNotificationSender.java PRE-CREATION webapp/src/main/java/org/apache/atlas/notification/NotificationEntityChangeListener.java 1eeecefc1 Diff: https://reviews.apache.org/r/68584/diff/2/ Changes: https://reviews.apache.org/r/68584/diff/1-2/ Testing --- Verified that the notifications are sent post transaction commit. Thanks, Madhan Neethiraj
[VOTE] Release Apache Atlas version 1.1.0 - rc0
Atlas team, Apache Atlas 1.1.0 release candidate #0 is now available for a vote within dev community. Links to the release artifacts are given below. Please review and vote. The vote will be open for at least 72 hours or until necessary votes are reached. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Nixon Rodrigues List of issues addressed in this release: https://issues.apache.org/jira/browse/ATLAS-2849?jql=project%20%3D%20Atlas%20AND%20resolution%20%3D%20Fixed%20%20%20%20AND%20fixVersion%20%3D%201.1.0%20ORDER%20BY%20key%20DESC Git tag for the release: https://github.com/apache/atlas/tree/release-1.1.0-rc0 Sources for the release: https://dist.apache.org/repos/dist/dev/atlas/1.1.0-rc0/apache-atlas-1.1.0-sources.tar.gz Source release verification: PGP Signature: https://dist.apache.org/repos/dist/dev/atlas/1.1.0-rc0/apache-atlas-1.1.0-sources.tar.gz.asc SHA512 Hash: https://dist.apache.org/repos/dist/dev/atlas/1.1.0-rc0/apache-atlas-1.1.0-sources.tar.gz.sha512 Keys to verify the signature of the release artifacts are available at: https://dist.apache.org/repos/dist/dev/atlas/KEYS
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-08-31.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-31.patch, > ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-08-17.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-08-23.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-08-22.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68412: ATLAS-1773: Atlas OMRS Repository Connector
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68412/ --- (Updated Aug. 31, 2018, 3:44 p.m.) Review request for atlas. Changes --- Updated diff with changes from first round of review comments plus enhancements from the last week Repository: atlas Description --- ATLAS-1773: Atlas OMRS Repository Connector Diffs (updated) - open-metadata/pom.xml PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/eventmapper/AtlasOMRSRepositoryEventMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/eventmapper/AtlasOMRSRepositoryEventMapperProvider.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasAttributeDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasAttributeMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasBaseTypeDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasClassificationDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasEntityDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasEntityMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasRelationshipDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasRelationshipMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasStoresProxy.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasStoresProxyImpl.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/Comparator.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/DSLQueryHelper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/EntityDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/FamousFive.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/ISpringBridge.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/LocalAtlasOMRSErrorCode.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/LocalAtlasOMRSMetadataCollection.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/LocalAtlasOMRSRepositoryConnector.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/LocalAtlasOMRSRepositoryConnectorProvider.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/SpringBridge.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TypeDefsByCategory.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TypeNameUtils.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/admin/server/spring/OpenMetadataAdminResource.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasClassificationDefMapper.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasEntityDefMapper.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasEntityMapper.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasRelationshipDefMapper.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasRelationshipMapper.java PRE-CREATION pom.xml c60a53b0e webapp/pom.xml 78aa81e80 webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION webapp/src/main/webapp/WEB-INF/web.xml 23dc0637a Diff: https://reviews.apache.org/r/68412/diff/2/ Changes: https://reviews.apache.org/r/68412/diff/1-2/ Testing --- Unit Testing (approx 80 tests) and Functional Testing of major operations (creation of types, instances, reference copies and proxies). Thanks, Graham Wallis
[jira] [Commented] (ATLAS-2724) UI enhancement for Avro schemas and other JSON-valued attributes
[ https://issues.apache.org/jira/browse/ATLAS-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598761#comment-16598761 ] ASF subversion and git services commented on ATLAS-2724: Commit 27be0da52cef2ed268442d140527d3a00083c3e7 in atlas's branch refs/heads/branch-1.0 from kevalbhatt [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=27be0da ] ATLAS-2724 : UI enhancement for Avro schemas and other JSON-valued attributes > UI enhancement for Avro schemas and other JSON-valued attributes > > > Key: ATLAS-2724 > URL: https://issues.apache.org/jira/browse/ATLAS-2724 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.8-incubating >Reporter: Barbara Eckman >Assignee: Keval Bhatt >Priority: Critical > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: 0001-Add-pretty-printed-json-values-in-tables.patch, > ATLAS-2724-master.patch, ATLAS-2724.patch, new_table.png > > > Currently JSON-valued attributes are fully displayed in-line with other > attributes, not pretty-printed, cluttering the display. To support a better > display, we can display JSON-valued attributes in a one-line box that can be > scrolled down, or fully expanded with a mouse click that pretty-prints the > JSON. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2724) UI enhancement for Avro schemas and other JSON-valued attributes
[ https://issues.apache.org/jira/browse/ATLAS-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-2724: --- Fix Version/s: 2.0.0 1.1.0 > UI enhancement for Avro schemas and other JSON-valued attributes > > > Key: ATLAS-2724 > URL: https://issues.apache.org/jira/browse/ATLAS-2724 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.8-incubating >Reporter: Barbara Eckman >Assignee: Keval Bhatt >Priority: Critical > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: 0001-Add-pretty-printed-json-values-in-tables.patch, > ATLAS-2724-master.patch, ATLAS-2724.patch, new_table.png > > > Currently JSON-valued attributes are fully displayed in-line with other > attributes, not pretty-printed, cluttering the display. To support a better > display, we can display JSON-valued attributes in a one-line box that can be > scrolled down, or fully expanded with a mouse click that pretty-prints the > JSON. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2847) UI: Add grunt scripts in package.json
[ https://issues.apache.org/jira/browse/ATLAS-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598759#comment-16598759 ] ASF subversion and git services commented on ATLAS-2847: Commit 0f31b466a5d6a0a66be923fb04ce428c845dd327 in atlas's branch refs/heads/branch-1.0 from kevalbhatt [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=0f31b46 ] ATLAS-2847 : UI: Add grunt scripts in package.json > UI: Add grunt scripts in package.json > -- > > Key: ATLAS-2847 > URL: https://issues.apache.org/jira/browse/ATLAS-2847 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2847-branch0.8.patch, ATLAS-2847-master.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2741) Deleted entities : DSL search with tag doesn't list the deleted entities to which that tag is associated
[ https://issues.apache.org/jira/browse/ATLAS-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2741: --- Fix Version/s: (was: 1.0.0) 2.0.0 1.1.0 > Deleted entities : DSL search with tag doesn't list the deleted entities to > which that tag is associated > > > Key: ATLAS-2741 > URL: https://issues.apache.org/jira/browse/ATLAS-2741 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2741-Deleted-entities-DSL-search-with-tag-does.patch > > > 1.Create an hive_table employee and add tag1 to it. > 2.Drop the table. > 3. DSL search : hive_table where name="employee" lists the DELETED table. > 4. Basic search with tag1 and excludeDeletedEntities set to False lists the > DELETED table. > 3. But, DSL search "hive_table isa tag1" doesn't list the DELETED table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2746) [Glossary] Simple Term/Category creation should work with CREATE privilege
[ https://issues.apache.org/jira/browse/ATLAS-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2746: --- Fix Version/s: (was: 1.0.0) (was: trunk) 2.0.0 1.1.0 > [Glossary] Simple Term/Category creation should work with CREATE privilege > -- > > Key: ATLAS-2746 > URL: https://issues.apache.org/jira/browse/ATLAS-2746 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2746-Term-Category-create-shouldn-t-require-UP.patch > > > Currently this operation needs following privileges > > Entity.READ, Entity.CREATE, Entity.UPDATE > > with the change simple term/category creation without any other relations > e.g. children, parent, categorized terms etc. can work with > > Entity.READ and Entity.CREATE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2745) Atlas EnumDefStore does not remember default value
[ https://issues.apache.org/jira/browse/ATLAS-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2745: --- Fix Version/s: 2.0.0 1.1.0 > Atlas EnumDefStore does not remember default value > -- > > Key: ATLAS-2745 > URL: https://issues.apache.org/jira/browse/ATLAS-2745 > Project: Atlas > Issue Type: Bug >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2745-2018-06-07.patch > > > If an enum def has a default value it is not remembered when the enum is > stored. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2745) Atlas EnumDefStore does not remember default value
[ https://issues.apache.org/jira/browse/ATLAS-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2745: --- Fix Version/s: 0.8.3 > Atlas EnumDefStore does not remember default value > -- > > Key: ATLAS-2745 > URL: https://issues.apache.org/jira/browse/ATLAS-2745 > Project: Atlas > Issue Type: Bug >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2745-2018-06-07.patch > > > If an enum def has a default value it is not remembered when the enum is > stored. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2769) Atlas start just after the upgrade fails with "TableNotFoundException: atlas_janus" exception
[ https://issues.apache.org/jira/browse/ATLAS-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2769: --- Fix Version/s: 2.0.0 > Atlas start just after the upgrade fails with "TableNotFoundException: > atlas_janus" exception > - > > Key: ATLAS-2769 > URL: https://issues.apache.org/jira/browse/ATLAS-2769 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > On Checking the upgrade history , Atlas start after upgrade is done > successfully. But Atlas has failed to come up with "TableNotFoundException: > atlas_janus" exception. > HBase logs at this time frame seem to be fine. > In one of the clusters , restarted Atlas ,which brought up Atlas fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2775) Enhance basic search to search entities with any classifications or no classifications
[ https://issues.apache.org/jira/browse/ATLAS-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2775: --- Fix Version/s: 2.0.0 > Enhance basic search to search entities with any classifications or no > classifications > -- > > Key: ATLAS-2775 > URL: https://issues.apache.org/jira/browse/ATLAS-2775 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > Enhance basic search to search on entities with any classifications or no > classifications > Basic search can now take the following value for classification: > * *_CLASSIFIED -* Search on all entities with ANY classification associated > (directly or through propagation) > * *_NOT_CLASSIFIED -* Search on all entities with NO classifications > associated (directly or through propagation) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2777) Enhance advanced search (DSL) to support classification search on _CLASSIFIED or _NOT_CLASSIFIED keyword
[ https://issues.apache.org/jira/browse/ATLAS-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2777: --- Fix Version/s: 2.0.0 > Enhance advanced search (DSL) to support classification search on _CLASSIFIED > or _NOT_CLASSIFIED keyword > > > Key: ATLAS-2777 > URL: https://issues.apache.org/jira/browse/ATLAS-2777 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2777-Enhance-advanced-search-DSL-to-support-cl.patch > > > ATLAS-2775 introduced keywords - _CLASSIFIED and __NOT__CLASSIFIED on basic > search to search on entities with ANY classifications or NO classifications. > This JIRA supports the same keywords in advanced search (DSL). > e.g: > * `_CLASSIFIED`, > * `_NOT_CLASSIFIED` > * hive_table isa _CLASSIFIED > * hive_column isa _NOT__CLASSIFIED -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2778) UI: Enhance advanced search (DSL) by adding _CLASSIFIED and _NOT_CLASSIFIED keyword in classification search
[ https://issues.apache.org/jira/browse/ATLAS-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2778: --- Fix Version/s: 2.0.0 > UI: Enhance advanced search (DSL) by adding _CLASSIFIED and _NOT_CLASSIFIED > keyword in classification search > - > > Key: ATLAS-2778 > URL: https://issues.apache.org/jira/browse/ATLAS-2778 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.1.0 >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2778.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2785) Import Hive script should handle table name with database in -t option
[ https://issues.apache.org/jira/browse/ATLAS-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2785: --- Fix Version/s: (was: trunk) 2.0.0 > Import Hive script should handle table name with database in -t option > -- > > Key: ATLAS-2785 > URL: https://issues.apache.org/jira/browse/ATLAS-2785 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk, 1.1.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > Import Hive script should handle table name with database in -t > option.Currently if database name is there in table name for - t or > tablename option , it imports all the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2801) Create a separate tar file for atlas-server components excluding atlas hook related components
[ https://issues.apache.org/jira/browse/ATLAS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2801: --- Fix Version/s: 2.0.0 1.1.0 > Create a separate tar file for atlas-server components excluding atlas hook > related components > -- > > Key: ATLAS-2801 > URL: https://issues.apache.org/jira/browse/ATLAS-2801 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2801-Create-a-separate-tar-file-for-atlas-serv.patch, > ATLAS-2801-Create-a-separate-tar-file-for-atlas-server-part-2.patch, > ATLAS-2801-Fix-for-tools-directory-absent-in-tar.gz.patch > > > Create a separate tar file for atlas-server components excluding atlas hook > related components. Already we have separate tar files for each of the atlas > hooks and it's better to have a separate atlas-server tar file for better > management of the packages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2812) Upgrade commons-fileupload to 1.3.3
[ https://issues.apache.org/jira/browse/ATLAS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2812: --- Fix Version/s: (was: 1.0.0) 2.0.0 > Upgrade commons-fileupload to 1.3.3 > --- > > Key: ATLAS-2812 > URL: https://issues.apache.org/jira/browse/ATLAS-2812 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8-incubating, 0.8.1, 0.8.2 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2812-Upgrade-commons-fileupload-to-1.3.3-master.patch, > 0001-ATLAS-2812-Upgrade-commons-fileupload-to-1.3.3.patch > > > Atlas packages commons-fileupload-1.2.1.jar which has a potential security > vulnerability > Need to upgrade to 1.3.1+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2815) Slow UI load and REST improvement for entities with ownedRef
[
https://issues.apache.org/jira/browse/ATLAS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-2815:
---
Fix Version/s: (was: trunk)
2.0.0
> Slow UI load and REST improvement for entities with ownedRef
>
>
> Key: ATLAS-2815
> URL: https://issues.apache.org/jira/browse/ATLAS-2815
> Project: Atlas
> Issue Type: Improvement
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.1, 1.1.0, 2.0.0
>
> Attachments: ATLAS-2815.patch, ATLAS-2815_UI.patch
>
>
> The approach is to check if query param-
> {color:#212121}*minExtInfo*:{color}*true* and the entity has schemaOptions,
> then the server will send the attributes accordingly in referredEntities.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2822) Provide option whether to delete propagated classification on entity delete during add classification
[ https://issues.apache.org/jira/browse/ATLAS-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2822: --- Fix Version/s: (was: 1.1.0) 2.0.0 > Provide option whether to delete propagated classification on entity delete > during add classification > - > > Key: ATLAS-2822 > URL: https://issues.apache.org/jira/browse/ATLAS-2822 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0, 1.1.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0, 2.0.0 > > > By default, when an entity is deleted - its associated classifications which > have been propagated to downstream entities will be retained. > This JIRA provides a boolean option when adding a new classification to an > entity - *"Remove Propagations on Entity Delete"* > When this flag is set to : > *TRUE* - Propagated classifications are removed during entity delete > *FALSE* - Propagated classifications are retained during entity delete -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2817) Update to JanusGraph 0.3.x
[ https://issues.apache.org/jira/browse/ATLAS-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2817: --- Fix Version/s: 2.0.0 1.1.0 > Update to JanusGraph 0.3.x > -- > > Key: ATLAS-2817 > URL: https://issues.apache.org/jira/browse/ATLAS-2817 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: 0001-Janusgraph-update-to-0.3.0.patch > > > There are couple of index related improvements in this version which helps > resolve the slowness in few of our DSL queries. This upgrade would speed up > DSL execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2725) Update license for JanusGraph usage
[ https://issues.apache.org/jira/browse/ATLAS-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2725: --- Fix Version/s: (was: 1.0.0) > Update license for JanusGraph usage > --- > > Key: ATLAS-2725 > URL: https://issues.apache.org/jira/browse/ATLAS-2725 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.1.0 > > Attachments: ATLAS-2725.patch > > > Update license txt for JanusGraph usage in Apache Atlas 1.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2823) Update hooks to enable asynchronous notifications
[ https://issues.apache.org/jira/browse/ATLAS-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2823: --- Fix Version/s: 2.0.0 1.1.0 > Update hooks to enable asynchronous notifications > - > > Key: ATLAS-2823 > URL: https://issues.apache.org/jira/browse/ATLAS-2823 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 1.1.0, 2.0.0 > > > With refactoring of hooks to use V2 style notifications (ATLAS-2491), the > option to send notifications asynchronously was removed. Sending the > notifications asynchronously is helpful, to avoid delays in host component; > hence should be supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2823) Update hooks to enable asynchronous notifications
[ https://issues.apache.org/jira/browse/ATLAS-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-2823. Resolution: Fixed > Update hooks to enable asynchronous notifications > - > > Key: ATLAS-2823 > URL: https://issues.apache.org/jira/browse/ATLAS-2823 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 1.1.0, 2.0.0 > > > With refactoring of hooks to use V2 style notifications (ATLAS-2491), the > option to send notifications asynchronously was removed. Sending the > notifications asynchronously is helpful, to avoid delays in host component; > hence should be supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2725) Update license for JanusGraph usage
[ https://issues.apache.org/jira/browse/ATLAS-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2725: --- Fix Version/s: 1.1.0 > Update license for JanusGraph usage > --- > > Key: ATLAS-2725 > URL: https://issues.apache.org/jira/browse/ATLAS-2725 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.0.0, 1.1.0 > > Attachments: ATLAS-2725.patch > > > Update license txt for JanusGraph usage in Apache Atlas 1.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2855) StructInsance.setNull does not handle enum types
Daniel Kelencz created ATLAS-2855:
-
Summary: StructInsance.setNull does not handle enum types
Key: ATLAS-2855
URL: https://issues.apache.org/jira/browse/ATLAS-2855
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8.2
Reporter: Daniel Kelencz
Fix For: 0.8.3
When trying to:
POST /api/atlas/v2/entity/bulk
{noformat}
{
"entities": [
{
"typeName": "hive_db",
"attributes": {
"qualifiedName": "findme",
"name": "findme",
"clusterName":
},
"status": "ACTIVE",
"createdBy": "admin",
"updatedBy": "admin",
"createTime": 1489585008165,
"updateTime": 1489585008801,
"version": 0,
"classifications": [],
"superTypes": []
}
],
"referredEntities": {}
}{noformat}
The following occurs in the logs:
{noformat}
Caused by: org.apache.atlas.AtlasException: Unknown datatype
{name=hive_principal_type, description=hive_principal_type}
at
org.apache.atlas.typesystem.persistence.StructInstance.setNull(StructInstance.java:274)
at
org.apache.atlas.repository.audit.EntityAuditListener.clearAttributeValues(EntityAuditListener.java:175)
at
org.apache.atlas.repository.audit.EntityAuditListener.getAuditEventDetail(EntityAuditListener.java:158)
at
org.apache.atlas.repository.audit.EntityAuditListener.createEvent(EntityAuditListener.java:133)
at
org.apache.atlas.repository.audit.EntityAuditListener.onEntitiesAdded(EntityAuditListener.java:63)
at
org.apache.atlas.repository.store.graph.v1.AtlasEntityChangeNotifier.notifyListeners(AtlasEntityChangeNotifier.java:164)
... 101 more {noformat}
This is because the hive_db contains hive_principal_type which is an enum, and
StructInstance.setNull does not handle enum types.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2854) Atlas fails to lookup users groups if any group names cannot be found
Sean Roberts created ATLAS-2854:
---
Summary: Atlas fails to lookup users groups if any group names
cannot be found
Key: ATLAS-2854
URL: https://issues.apache.org/jira/browse/ATLAS-2854
Project: Atlas
Issue Type: Bug
Affects Versions: 0.8.1
Reporter: Sean Roberts
When a user has groups whose names are not available, Atlas hits an exception
and fails to find any of the groups resulting in no Atlas access for that user:
{code}
$ id sroberts
uid=1415428167(sroberts) gid=100(users)
groups=100(users),1415476164(hdp_admins),1415476163(hdp_users),1414200513,1414548426,1415124193,1414548429
{code}
{code}
## Atlas application.log:
2018-08-31 08:53:31,552 INFO - [pool-2-thread-25:] ~ SSO login user : sroberts
(AtlasKnoxSSOAuthenticationFilter:182)
2018-08-31 08:53:31,662 WARN - [pool-2-thread-25:] ~ got exception trying to
get groups for user sroberts: id: cannot find name for group ID 1414200513
java.io.IOException: No groups found for user sroberts
{code}
This scenario is common in directory (LDAP/AD) integrated environments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2853) Entity notifications to be sent after transaction commit
[ https://issues.apache.org/jira/browse/ATLAS-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598463#comment-16598463 ] Graham Wallis commented on ATLAS-2853: -- In addition to the problem of what happens on a rollback, the problem also affects commit - but I think your patch addresses it. The additional aspect to the problem is that if the notification is sent prior to commit then the subscribers can pick it up and query the graph before the graph has had a chance to commit - so the subscribers see the old (stale) state. The most obvious example of this was on an entity create - the subscriber then queried the graph and the graph denied any knowledge of the new entity. Doing the commit before send is better in both the commit and rollback cases. > Entity notifications to be sent after transaction commit > > > Key: ATLAS-2853 > URL: https://issues.apache.org/jira/browse/ATLAS-2853 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2853.patch > > > Currently, notification on entity changes (create/update/delete entities, > add/update/remove classifications on entities) are sent before the changes > are committed in the database. If commit fails, the entity state seen by > notification receivers would be different from Atlas. To avoid this, Atlas > server should entity notifications only after the transaction is committed to > the database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
