Re: Review Request 72938: ATLAS-3984 Add UI Date Timezone and UI Date Format in Session api
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72938/ --- (Updated Oct. 9, 2020, 6:21 a.m.) Review request for atlas, Jayendra Parab, Madhan Neethiraj, Nixon Rodrigues, and Sarath Subramanian. Changes --- UI date format changed from "MM/dd/ hh:mm:ss tt" to "MM/DD/ hh:mm:ss A" Bugs: ATLAS-3984 https://issues.apache.org/jira/browse/ATLAS-3984 Repository: atlas Description --- 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. Diffs (updated) - webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 3a6139f Diff: https://reviews.apache.org/r/72938/diff/2/ Changes: https://reviews.apache.org/r/72938/diff/1-2/ Testing --- Thanks, Mandar Ambawane
[jira] [Resolved] (ATLAS-3987) Atlas client export API does not pass server response code in case of failure
[ https://issues.apache.org/jira/browse/ATLAS-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deep Singh resolved ATLAS-3987. --- Resolution: Fixed > Atlas client export API does not pass server response code in case of failure > - > > Key: ATLAS-3987 > URL: https://issues.apache.org/jira/browse/ATLAS-3987 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Deep Singh >Assignee: Deep Singh >Priority: Major > > For Atlas export, Admin priveledges are required. If such priveledges are not > there, then Export API fails with 403 status. However, the atlasClient does > not pass this information in the exception. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
[
https://issues.apache.org/jira/browse/ATLAS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-3989:
---
Attachment: ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
> Behavior change in Atlas API to get Atlas Server object during metadata
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments:
> ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
>
>
> There is a change being noticed in the Atlas server API used during atlas
> metadata replication in hive.
> Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster
> name, used to work.
> Now, it doesn't work any more. This Api is used during replication to get
> the changeMarker info.
> Now the API works with some thing called server name which is 'default' by
> default.
> Also, now the prerequisite is to at least have one export or import API call
> in order to get this 'default' initialized.
> The change-marker is obtained prior to invoking export and hence the all
> policy is bound to fail unless we mandate calling Export or Import API
> outside hive replication once to get this object initialized, even if hive
> uses 'default' in the call.
>
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
[
https://issues.apache.org/jira/browse/ATLAS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-3989:
---
Attachment: (was:
ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch)
> Behavior change in Atlas API to get Atlas Server object during metadata
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
>
> There is a change being noticed in the Atlas server API used during atlas
> metadata replication in hive.
> Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster
> name, used to work.
> Now, it doesn't work any more. This Api is used during replication to get
> the changeMarker info.
> Now the API works with some thing called server name which is 'default' by
> default.
> Also, now the prerequisite is to at least have one export or import API call
> in order to get this 'default' initialized.
> The change-marker is obtained prior to invoking export and hence the all
> policy is bound to fail unless we mandate calling Export or Import API
> outside hive replication once to get this object initialized, even if hive
> uses 'default' in the call.
>
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
[
https://issues.apache.org/jira/browse/ATLAS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211511#comment-17211511
]
Sarath Subramanian commented on ATLAS-3989:
---
Looks good +1. Thanks [~amestry].
> Behavior change in Atlas API to get Atlas Server object during metadata
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments:
> ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
>
>
> There is a change being noticed in the Atlas server API used during atlas
> metadata replication in hive.
> Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster
> name, used to work.
> Now, it doesn't work any more. This Api is used during replication to get
> the changeMarker info.
> Now the API works with some thing called server name which is 'default' by
> default.
> Also, now the prerequisite is to at least have one export or import API call
> in order to get this 'default' initialized.
> The change-marker is obtained prior to invoking export and hence the all
> policy is bound to fail unless we mandate calling Export or Import API
> outside hive replication once to get this object initialized, even if hive
> uses 'default' in the call.
>
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
Ashutosh Mestry created ATLAS-3989: -- Summary: Behavior change in Atlas API to get Atlas Server object during metadata replication Key: ATLAS-3989 URL: https://issues.apache.org/jira/browse/ATLAS-3989 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Ashutosh Mestry Assignee: Ashutosh Mestry There is a change being noticed in the Atlas server API used during atlas metadata replication in hive. Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster name, used to work. Now, it doesn't work any more. This Api is used during replication to get the changeMarker info. Now the API works with some thing called server name which is 'default' by default. Also, now the prerequisite is to at least have one export or import API call in order to get this 'default' initialized. The change-marker is obtained prior to invoking export and hence the all policy is bound to fail unless we mandate calling Export or Import API outside hive replication once to get this object initialized, even if hive uses 'default' in the call. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
[ https://issues.apache.org/jira/browse/ATLAS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3989: --- Attachment: ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch > Behavior change in Atlas API to get Atlas Server object during metadata > replication > --- > > Key: ATLAS-3989 > URL: https://issues.apache.org/jira/browse/ATLAS-3989 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch > > > There is a change being noticed in the Atlas server API used during atlas > metadata replication in hive. > Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster > name, used to work. > Now, it doesn't work any more. This Api is used during replication to get the > changeMarker info. > Now the API works with some thing called server name which is 'default' by > default. > Also, now the prerequisite is to at least have one export or import API call > in order to get this 'default' initialized. > The change-marker is obtained prior to invoking export and hence the all > policy is bound to fail unless we mandate calling Export or Import API > outside hive replication once to get this object initialized, even if hive > uses 'default' in the call. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
[
https://issues.apache.org/jira/browse/ATLAS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-3989:
---
Description:
There is a change being noticed in the Atlas server API used during atlas
metadata replication in hive.
Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster
name, used to work.
Now, it doesn't work any more. This Api is used during replication to get the
changeMarker info.
Now the API works with some thing called server name which is 'default' by
default.
Also, now the prerequisite is to at least have one export or import API call
in order to get this 'default' initialized.
The change-marker is obtained prior to invoking export and hence the all
policy is bound to fail unless we mandate calling Export or Import API outside
hive replication once to get this object initialized, even if hive uses
'default' in the call.
*Root cause*
We switched from using
{code:java}
atlas.cluster.name{code}
to
{code:java}
atlas.metadata.namespace{code}
was:
There is a change being noticed in the Atlas server API used during atlas
metadata replication in hive.
Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster name,
used to work.
Now, it doesn't work any more. This Api is used during replication to get the
changeMarker info.
Now the API works with some thing called server name which is 'default' by
default.
Also, now the prerequisite is to at least have one export or import API call in
order to get this 'default' initialized.
The change-marker is obtained prior to invoking export and hence the all policy
is bound to fail unless we mandate calling Export or Import API outside hive
replication once to get this object initialized, even if hive uses 'default' in
the call.
> Behavior change in Atlas API to get Atlas Server object during metadata
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments:
> ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
>
>
> There is a change being noticed in the Atlas server API used during atlas
> metadata replication in hive.
> Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster
> name, used to work.
> Now, it doesn't work any more. This Api is used during replication to get
> the changeMarker info.
> Now the API works with some thing called server name which is 'default' by
> default.
> Also, now the prerequisite is to at least have one export or import API call
> in order to get this 'default' initialized.
> The change-marker is obtained prior to invoking export and hence the all
> policy is bound to fail unless we mandate calling Export or Import API
> outside hive replication once to get this object initialized, even if hive
> uses 'default' in the call.
>
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3987) Atlas client export API does not pass server response code in case of failure
[ https://issues.apache.org/jira/browse/ATLAS-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211180#comment-17211180 ] ASF subversion and git services commented on ATLAS-3987: Commit 47c3155e04a438f02e2fd49740065ce983aa66e9 in atlas's branch refs/heads/branch-2.0 from Deep Singh [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=47c3155 ] ATLAS-3987: Atlas client export API, must pass server error code in the exception Signed-off-by: Ashutosh Mestry > Atlas client export API does not pass server response code in case of failure > - > > Key: ATLAS-3987 > URL: https://issues.apache.org/jira/browse/ATLAS-3987 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Deep Singh >Assignee: Deep Singh >Priority: Major > > For Atlas export, Admin priveledges are required. If such priveledges are not > there, then Export API fails with 403 status. However, the atlasClient does > not pass this information in the exception. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3987) Atlas client export API does not pass server response code in case of failure
Deep Singh created ATLAS-3987: - Summary: Atlas client export API does not pass server response code in case of failure Key: ATLAS-3987 URL: https://issues.apache.org/jira/browse/ATLAS-3987 Project: Atlas Issue Type: Bug Components: atlas-intg Reporter: Deep Singh Assignee: Deep Singh For Atlas export, Admin priveledges are required. If such priveledges are not there, then Export API fails with 403 status. However, the atlasClient does not pass this information in the exception. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72933: ATLAS-3982 : Upgrade Atlas Spring framework version to 4.3.29.RELEASE
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72933/ --- (Updated Oct. 9, 2020, 10:38 a.m.) Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sarath Subramanian. Bugs: ATLAS-3982 https://issues.apache.org/jira/browse/ATLAS-3982 Repository: atlas Description --- Upgrading Apache atlas spring framework version to prevent attacks from CVE-2020-5421 Diffs - pom.xml 6b5d2fde6 Diff: https://reviews.apache.org/r/72933/diff/1/ Testing --- Tested with following scenario : Created entities eg from Hive shell mvn clean install mvn clean package -Pdist,embedded-hbase-solr -DskipTests Atlas server is running successfully Thanks, chaitali
Review Request 72942: ATLAS-3987: Atlas client export API does not pass server response code in case of failure
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72942/ --- Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath Subramanian. Bugs: ATLAS-3987 https://issues.apache.org/jira/browse/ATLAS-3987 Repository: atlas Description --- For Atlas export, Admin priveledges are required. If such priveledges are not there, then Export API fails with 403 status. However, the atlasClient does not pass this information in the exception. AtlasServiceException did not have any constructon with another AtlasServiceException object as parameter. There is a constructon which takes generic Exception parameter, and does not care about the status in the exception. I have added a new constructor which retains the status of passed exception. Diffs - client/common/src/main/java/org/apache/atlas/AtlasBaseClient.java 6e03669ef client/common/src/main/java/org/apache/atlas/AtlasServiceException.java 6b4dd1165 webapp/src/test/java/org/apache/atlas/web/resources/AdminExportImportTestIT.java e53f9a8a6 Diff: https://reviews.apache.org/r/72942/diff/1/ Testing --- Unit testing Additional unit tests added. Thanks, Deep Singh
[jira] [Commented] (ATLAS-3612) Error while starting apache atlas
[ https://issues.apache.org/jira/browse/ATLAS-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210794#comment-17210794 ] Merlin Wang commented on ATLAS-3612: You can use echo $JAVA_HOME to check whether JAVA_HOME is set correctly. I also encountered this problem because the JAVA_HOME was modified to a non-existent path. > Error while starting apache atlas > - > > Key: ATLAS-3612 > URL: https://issues.apache.org/jira/browse/ATLAS-3612 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8.4 > Environment: NAME="CentOS Linux" > VERSION="7 (Core)" >Reporter: Balaji Mohanarangam >Priority: Major > > Received the following error while starting atlas on an unix machine with > default config. > [root@xmdmpoc-as-1d apache-atlas-0.8.5-SNAPSHOT]# ./bin/atlas_start.py > Exception: [Errno 2] No such file or directory > Traceback (most recent call last): > File "./bin/atlas_start.py", line 150, in > File "./bin/atlas_start.py", line 74, in main > File "/app/atlas/apache-atlas-0.8.5-SNAPSHOT/bin/atlas_config.py", line 149, > i n expandWebApp > jar(atlasWarPath) > File "/app/atlas/apache-atlas-0.8.5-SNAPSHOT/bin/atlas_config.py", line 202, > i n jar > process = runProcess(commandline) > File "/app/atlas/apache-atlas-0.8.5-SNAPSHOT/bin/atlas_config.py", line 238, > i n runProcess > p = subprocess.Popen(commandline, stdout=stdoutFile, stderr=stderrFile, shel > l=shell) > File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__ > errread, errwrite) > File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child > raise child_exception > OSError: [Errno 2] No such file or directory > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Review Request 72943: ATLAS-3988 : REST GET entity API with type's GUID throws NPE
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72943/ --- Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sarath Subramanian. Bugs: ATLAS-3988 https://issues.apache.org/jira/browse/ATLAS-3988 Repository: atlas Description --- Issue : GET on /api/atlas/v2/entity/guid/ throws invalid GUID exception. BUT GET on /api/atlas/v2/entity/guid/ throws NPE. 2020-01-14 02:19:07,272 ERROR - [pool-2-thread-3 - a0b7457e-d43f-4fca-9581-8db695ef7af3:] ~ graph rollback due to exception (GraphTransactionInterceptor:167) java.lang.NullPointerException at org.apache.atlas.type.AtlasTypeRegistry.getType(AtlasTypeRegistry.java:94) at org.apache.atlas.repository.store.graph.v2.EntityGraphRetriever.mapAttributes(EntityGraphRetriever.java:608) at org.apache.atlas.repository.store.graph.v2.EntityGraphRetriever.mapVertexToAtlasEntity(EntityGraphRetriever.java:448) This patch fixes the issue by adding a null check for typename exists or not for the guid passed. Diffs - intg/src/main/java/org/apache/atlas/AtlasErrorCode.java a14e43a1e repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java 00146b106 Diff: https://reviews.apache.org/r/72943/diff/1/ Testing --- Tested with GET call GET on /api/atlas/v2/entity/guid/ by passing typename guid to this entity call. Thanks, chaitali
Re: Review Request 72942: ATLAS-3987: Atlas client export API does not pass server response code in case of failure
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72942/#review222007 --- Ship it! Ship It! - Nixon Rodrigues On Oct. 9, 2020, 8:16 a.m., Deep Singh wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72942/ > --- > > (Updated Oct. 9, 2020, 8:16 a.m.) > > > Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath > Subramanian. > > > Bugs: ATLAS-3987 > https://issues.apache.org/jira/browse/ATLAS-3987 > > > Repository: atlas > > > Description > --- > > For Atlas export, Admin priveledges are required. If such priveledges are not > there, then Export API fails with 403 status. However, the atlasClient does > not pass this information in the exception. > > AtlasServiceException did not have any constructon with another > AtlasServiceException object as parameter. > There is a constructon which takes generic Exception parameter, and does not > care about the status in the exception. > > I have added a new constructor which retains the status of passed exception. > > > Diffs > - > > client/common/src/main/java/org/apache/atlas/AtlasBaseClient.java 6e03669ef > client/common/src/main/java/org/apache/atlas/AtlasServiceException.java > 6b4dd1165 > > webapp/src/test/java/org/apache/atlas/web/resources/AdminExportImportTestIT.java > e53f9a8a6 > > > Diff: https://reviews.apache.org/r/72942/diff/1/ > > > Testing > --- > > Unit testing > Additional unit tests added. > > > Thanks, > > Deep Singh > >
[jira] [Created] (ATLAS-3988) REST GET entity API with type's GUID throws NPE
chaitali borole created ATLAS-3988: -- Summary: REST GET entity API with type's GUID throws NPE Key: ATLAS-3988 URL: https://issues.apache.org/jira/browse/ATLAS-3988 Project: Atlas Issue Type: Improvement Reporter: chaitali borole Assignee: chaitali borole GET on /api/atlas/v2/entity/guid/ throws invalid GUID exception. BUT GET on /api/atlas/v2/entity/guid/ throws NPE. 2020-01-14 02:19:07,272 ERROR - [pool-2-thread-3 - a0b7457e-d43f-4fca-9581-8db695ef7af3:] ~ graph rollback due to exception (GraphTransactionInterceptor:167) java.lang.NullPointerException at org.apache.atlas.type.AtlasTypeRegistry.getType(AtlasTypeRegistry.java:94) at org.apache.atlas.repository.store.graph.v2.EntityGraphRetriever.mapAttributes(EntityGraphRetriever.java:608) at org.apache.atlas.repository.store.graph.v2.EntityGraphRetriever.mapVertexToAtlasEntity(EntityGraphRetriever.java:448) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3988) REST GET entity API with type's GUID throws NPE
[ https://issues.apache.org/jira/browse/ATLAS-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3988: --- Fix Version/s: 3.0.0 > REST GET entity API with type's GUID throws NPE > --- > > Key: ATLAS-3988 > URL: https://issues.apache.org/jira/browse/ATLAS-3988 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > GET on /api/atlas/v2/entity/guid/ throws invalid GUID exception. > BUT GET on /api/atlas/v2/entity/guid/ throws NPE. > > 2020-01-14 02:19:07,272 ERROR - [pool-2-thread-3 - > a0b7457e-d43f-4fca-9581-8db695ef7af3:] ~ graph rollback due to exception > (GraphTransactionInterceptor:167) > java.lang.NullPointerException > at > org.apache.atlas.type.AtlasTypeRegistry.getType(AtlasTypeRegistry.java:94) > at > org.apache.atlas.repository.store.graph.v2.EntityGraphRetriever.mapAttributes(EntityGraphRetriever.java:608) > at > org.apache.atlas.repository.store.graph.v2.EntityGraphRetriever.mapVertexToAtlasEntity(EntityGraphRetriever.java:448) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3988) REST GET entity API with type's GUID throws NPE
[ https://issues.apache.org/jira/browse/ATLAS-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3988: --- Affects Version/s: 3.0.0 > REST GET entity API with type's GUID throws NPE > --- > > Key: ATLAS-3988 > URL: https://issues.apache.org/jira/browse/ATLAS-3988 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > GET on /api/atlas/v2/entity/guid/ throws invalid GUID exception. > BUT GET on /api/atlas/v2/entity/guid/ throws NPE. > > 2020-01-14 02:19:07,272 ERROR - [pool-2-thread-3 - > a0b7457e-d43f-4fca-9581-8db695ef7af3:] ~ graph rollback due to exception > (GraphTransactionInterceptor:167) > java.lang.NullPointerException > at > org.apache.atlas.type.AtlasTypeRegistry.getType(AtlasTypeRegistry.java:94) > at > org.apache.atlas.repository.store.graph.v2.EntityGraphRetriever.mapAttributes(EntityGraphRetriever.java:608) > at > org.apache.atlas.repository.store.graph.v2.EntityGraphRetriever.mapVertexToAtlasEntity(EntityGraphRetriever.java:448) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work
[ https://issues.apache.org/jira/browse/ATLAS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210818#comment-17210818 ] ASF subversion and git services commented on ATLAS-3978: Commit 87cf906b4a696a39130b4cd2310cbb096d7c1a83 in atlas's branch refs/heads/branch-2.0 from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=87cf906 ] ATLAS-3978: In Administration, Audits filter for 'OR' condition does not work (cherry picked from commit 4ab4962314a80d9e0ac766f81018e22995c8e83d) > In Administration, Audits filter for 'OR' condition does not work > - > > Key: ATLAS-3978 > URL: https://issues.apache.org/jira/browse/ATLAS-3978 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3978.patch, OR condition not working.mkv > > > Description:: > When user uses OR condition it does not apply on filter, results are listed > with AND condition. PFA evidence file [OR condition not working.mkv] > Steps to regenerate:: > # Go to Administration- Audits > # Select the OR condition filter > # Check the console for response > # Results are listed with 'AND' operator instead of 'OR' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work
[ https://issues.apache.org/jira/browse/ATLAS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210696#comment-17210696 ] Durga Kadam commented on ATLAS-3978: +1 > In Administration, Audits filter for 'OR' condition does not work > - > > Key: ATLAS-3978 > URL: https://issues.apache.org/jira/browse/ATLAS-3978 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3978.patch, OR condition not working.mkv > > > Description:: > When user uses OR condition it does not apply on filter, results are listed > with AND condition. PFA evidence file [OR condition not working.mkv] > Steps to regenerate:: > # Go to Administration- Audits > # Select the OR condition filter > # Check the console for response > # Results are listed with 'AND' operator instead of 'OR' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work
[ https://issues.apache.org/jira/browse/ATLAS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210817#comment-17210817 ] ASF subversion and git services commented on ATLAS-3978: Commit 4ab4962314a80d9e0ac766f81018e22995c8e83d in atlas's branch refs/heads/master from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4ab4962 ] ATLAS-3978: In Administration, Audits filter for 'OR' condition does not work > In Administration, Audits filter for 'OR' condition does not work > - > > Key: ATLAS-3978 > URL: https://issues.apache.org/jira/browse/ATLAS-3978 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3978.patch, OR condition not working.mkv > > > Description:: > When user uses OR condition it does not apply on filter, results are listed > with AND condition. PFA evidence file [OR condition not working.mkv] > Steps to regenerate:: > # Go to Administration- Audits > # Select the OR condition filter > # Check the console for response > # Results are listed with 'AND' operator instead of 'OR' -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72908: ATLAS-3957 Use Audit framework to capture audit entries for "Server Start" and "Server In Active mode" (HA)
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72908/ --- (Updated Oct. 9, 2020, 2:46 p.m.) Review request for atlas, Jayendra Parab, Madhan Neethiraj, Nixon Rodrigues, and Sarath Subramanian. Changes --- Addressed review comments Bugs: ATLAS-3957 https://issues.apache.org/jira/browse/ATLAS-3957 Repository: atlas Description --- 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. Diffs (updated) - addons/models/-Area0/0010-base_model.json 1de9e57 addons/models/-Area0/patches/006-base_model_add_atlas_operation_attributes.json a27525e intg/src/main/java/org/apache/atlas/model/audit/AtlasAuditEntry.java 9ed4168 test-tools/src/main/resources/solr/core-template/solrconfig.xml 7cbfbd9 webapp/src/main/java/org/apache/atlas/BeanUtil.java PRE-CREATION webapp/src/main/java/org/apache/atlas/web/service/EmbeddedServer.java 6985291 webapp/src/main/java/org/apache/atlas/web/service/ServiceState.java 113b2b2 Diff: https://reviews.apache.org/r/72908/diff/3/ Changes: https://reviews.apache.org/r/72908/diff/2-3/ Testing --- https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/35/console https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/66/consoleFull Thanks, Mandar Ambawane
