[jira] [Updated] (ATLAS-4866) Export/Import: Skip adding processed guids in audit while importing huge zip
[
https://issues.apache.org/jira/browse/ATLAS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4866:
--
Description:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When large sized export zipped file is imported, import gives below error,
internally import gets succesful, but fail creating audit.
{code:java}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.janusgraph.core.JanusGraphException:
Could not commit transaction due to exception during
persistence","errorCause":"Could not commit transaction due to exception during
persistence"}
{code}
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
*Solution:*
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry when size of entity goes beyond the value stored in
bytes below
{code:java}
atlas.hbase.client.keyvalue.maxsize{code}
was:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When large sized export zipped file is imported, import gives below error,
internally import gets succesful, but fail creating audit.
_{"errorCode":"ATLAS-500-00-001","errorMessage":"org.janusgraph.core.JanusGraphException:
Could not commit transaction due to exception during
persistence","errorCause":"Could not commit transaction due to exception during
persistence"}_
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
[jira] [Updated] (ATLAS-4866) Export/Import: Skip adding processed guids in audit while importing huge zip
[
https://issues.apache.org/jira/browse/ATLAS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4866:
--
Description:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When large sized export zipped file is imported, import gives below error,
internally import gets succesful, but fail creating audit.
_{"errorCode":"ATLAS-500-00-001","errorMessage":"org.janusgraph.core.JanusGraphException:
Could not commit transaction due to exception during
persistence","errorCause":"Could not commit transaction due to exception during
persistence"}_
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
*Solution:*
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry when size of entity goes beyond the value stored in
bytes below
{code:java}
atlas.hbase.client.keyvalue.maxsize{code}
was:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
[jira] [Updated] (ATLAS-4866) Export/Import: Skip adding processed guids in audit while importing huge zip
[
https://issues.apache.org/jira/browse/ATLAS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4866:
--
Description:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
*Solution:*
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry when size of entity goes beyond the value stored in
bytes below
{code:java}
atlas.hbase.client.keyvalue.maxsize{code}
was:
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry
&
[jira] [Created] (ATLAS-4866) Export/Import: Skip adding processed guids in audit while importing huge zip
Pinal Shah created ATLAS-4866:
-
Summary: Export/Import: Skip adding processed guids in audit while
importing huge zip
Key: ATLAS-4866
URL: https://issues.apache.org/jira/browse/ATLAS-4866
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4830) Make ignore patterns generic for all the hooks
[ https://issues.apache.org/jira/browse/ATLAS-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848702#comment-17848702 ] ASF subversion and git services commented on ATLAS-4830: Commit 45a3fcdd21d6d5a8517a33994d37eb97ca0c656c in atlas's branch refs/heads/branch-2.0 from Amruth S [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=45a3fcdd2 ] ATLAS-4830: Make ignore patterns generic for all the hooks Signed-off-by: Radhika Kundam (cherry picked from commit f3ef15afc9aa336c27aeeb427e5f2078b233d364) > Make ignore patterns generic for all the hooks > -- > > Key: ATLAS-4830 > URL: https://issues.apache.org/jira/browse/ATLAS-4830 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: Radhika Kundam >Assignee: Amruth S >Priority: Major > Attachments: HLDD for Generic Ignore Patterns.pdf > > > Currently the ignore patterns are only applicable for hive tables, but in few > escalations we have seen that there was a need to see if we can add ignore > patterns for other components as well, like spark, etc. > So we need to make these ignore patterns generic, so that it works for all > hooks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4830) Make ignore patterns generic for all the hooks
[ https://issues.apache.org/jira/browse/ATLAS-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848701#comment-17848701 ] ASF subversion and git services commented on ATLAS-4830: Commit f3ef15afc9aa336c27aeeb427e5f2078b233d364 in atlas's branch refs/heads/master from Amruth S [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f3ef15afc ] ATLAS-4830: Make ignore patterns generic for all the hooks Signed-off-by: Radhika Kundam > Make ignore patterns generic for all the hooks > -- > > Key: ATLAS-4830 > URL: https://issues.apache.org/jira/browse/ATLAS-4830 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: Radhika Kundam >Assignee: Amruth S >Priority: Major > Attachments: HLDD for Generic Ignore Patterns.pdf > > > Currently the ignore patterns are only applicable for hive tables, but in few > escalations we have seen that there was a need to see if we can add ignore > patterns for other components as well, like spark, etc. > So we need to make these ignore patterns generic, so that it works for all > hooks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4865) Documentation: Add features, improvement which are missing in the doc
Pinal Shah created ATLAS-4865: - Summary: Documentation: Add features, improvement which are missing in the doc Key: ATLAS-4865 URL: https://issues.apache.org/jira/browse/ATLAS-4865 Project: Atlas Issue Type: Task Components: atlas-webui Affects Versions: 2.3.0 Reporter: Pinal Shah Assignee: Pinal Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4864) BasicSearch: Search with combination of terms and freetext, works incorrectly
Pinal Shah created ATLAS-4864: - Summary: BasicSearch: Search with combination of terms and freetext, works incorrectly Key: ATLAS-4864 URL: https://issues.apache.org/jira/browse/ATLAS-4864 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah Attachments: Screen Shot 2020-06-08 at 4.03.35 PM (1).png Filter of freetext query doen't apply on the term result. !Screen Shot 2020-06-08 at 4.03.35 PM (1).png|width=744,height=303! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4832) Atlas - Upgrade Spring Framework to 5.3.32
[ https://issues.apache.org/jira/browse/ATLAS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] VINAYAK MARRAIYA updated ATLAS-4832: Summary: Atlas - Upgrade Spring Framework to 5.3.32 (was: Atlas - Upgrade Spring Framework to 5.3.27) > Atlas - Upgrade Spring Framework to 5.3.32 > -- > > Key: ATLAS-4832 > URL: https://issues.apache.org/jira/browse/ATLAS-4832 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4832) Atlas - Upgrade Spring Framework to 5.3.27
[ https://issues.apache.org/jira/browse/ATLAS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] VINAYAK MARRAIYA reopened ATLAS-4832: - > Atlas - Upgrade Spring Framework to 5.3.27 > -- > > Key: ATLAS-4832 > URL: https://issues.apache.org/jira/browse/ATLAS-4832 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4832) Atlas - Upgrade Spring Framework to 5.3.27
[ https://issues.apache.org/jira/browse/ATLAS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] VINAYAK MARRAIYA updated ATLAS-4832: Summary: Atlas - Upgrade Spring Framework to 5.3.27 (was: Atlas - Upgrade Spring Framework to 5.3.32) > Atlas - Upgrade Spring Framework to 5.3.27 > -- > > Key: ATLAS-4832 > URL: https://issues.apache.org/jira/browse/ATLAS-4832 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4863) NPE while deleting BusinessMetadata
Pinal Shah created ATLAS-4863:
-
Summary: NPE while deleting BusinessMetadata
Key: ATLAS-4863
URL: https://issues.apache.org/jira/browse/ATLAS-4863
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
If businessMetadata is created without adding any applicable types, we get
NullPointerException when we try to delete that businessmetadata.
Example:
{code:java}
{
"category": "BUSINESS_METADATA",
"guid": "678dc8e1-3897-4b43-94f2-929ea984e8d9",
"createdBy": "h0650206",
"updatedBy": "h0650206",
"createTime": 1714471319783,
"updateTime": 1714731363238,
"version": 3,
"name": "test_create_bussiness_metadata",
"description": "test_create_bussiness_metadata",
"typeVersion": "1.1",
"attributeDefs": [
{
"name": "test",
"typeName": "string",
"isOptional": true,
"cardinality": "SINGLE",
"valuesMinCount": 0,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": true,
"includeInNotification": false,
"searchWeight": 0,
"options": {
"applicableEntityTypes": "[]",
"maxStrLength": "50"
}
}
]
} {code}
If above businessMetadata type is deleted, we get below exception
{code:java}
java.lang.NullPointerException
at java.base/java.util.Objects.requireNonNull(Objects.java:221)
at java.base/java.lang.String.join(String.java:2440)
at
org.apache.atlas.repository.store.graph.v2.AtlasBusinessMetadataDefStoreV2.isBusinessAttributePresent(AtlasBusinessMetadataDefStoreV2.java:425)
at
org.apache.atlas.repository.store.graph.v2.AtlasBusinessMetadataDefStoreV2.checkBusinessMetadataRef(AtlasBusinessMetadataDefStoreV2.java:408)
at
org.apache.atlas.repository.store.graph.v2.AtlasBusinessMetadataDefStoreV2.preDeleteByGuid(AtlasBusinessMetadataDefStoreV2.java:342)
at
org.apache.atlas.repository.store.graph.v2.AtlasAbstractDefStoreV2.deleteByGuid(AtlasAbstractDefStoreV2.java:153)
at
org.apache.atlas.repository.store.graph.v2.AtlasBusinessMetadataDefStoreV2.deleteByGuid(AtlasBusinessMetadataDefStoreV2.java:55)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.deleteTypesDef(AtlasTypeDefGraphStore.java:669)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.deleteTypeByName(AtlasTypeDefGraphStore.java:714)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySpringCGLIB$$5226c80b.invoke()
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4862) Atlas to support Faceted Search
Amruth S created ATLAS-4862: --- Summary: Atlas to support Faceted Search Key: ATLAS-4862 URL: https://issues.apache.org/jira/browse/ATLAS-4862 Project: Atlas Issue Type: New Feature Components: atlas-core Reporter: Amruth S Assignee: Amruth S The basic search feature in Atlas helps users find metadata entities based on keyword matches. However, introducing faceted search will enhance the search experience by providing advanced filtering and navigation options through predefined facets or attributes. Faceted search offers users a more structured and intuitive way to explore metadata within Atlas, leading to improved discoverability and usability of the platform. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4861) Export/Import: add flag to skip updating replicated attributes
Pinal Shah created ATLAS-4861: - Summary: Export/Import: add flag to skip updating replicated attributes Key: ATLAS-4861 URL: https://issues.apache.org/jira/browse/ATLAS-4861 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah *Replicated Attributes:* Users want knowledge of how the entities have landed into Atlas instance, if they were created via hook ingestion or whether they were imported from another Atlas instance. This is addressed by 2 new attributes that are now part of _Referenceable_ entity type viz. _replicatedFrom_ and _replicatedTo_. *Current Behaviour:* At the end of export/import, the entities which are exported/imported are updated with the replicationTo/replicationFrom respectively with the value of AtlasServer object Hence updating each and every entity takes much time. *Improvement:* Add flag to skip such updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4345) UI: Lineage issues for when entities are greater than 9k in a given lineage.
[ https://issues.apache.org/jira/browse/ATLAS-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844649#comment-17844649 ] Brijesh Bhalala commented on ATLAS-4345: The relationship limit is deliberately set to 1000 because this ensures that the entities are properly visible in image-viewing software or browsers regardless of the size of the lineage. > UI: Lineage issues for when entities are greater than 9k in a given lineage. > > > Key: ATLAS-4345 > URL: https://issues.apache.org/jira/browse/ATLAS-4345 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4345-UI-Lineage-issues-for-when-entities-are-g.patch > > > There are two issues that emerge when there are more than 9k entities in a > given lineage: > > # It doesn't display all the entities in the given page, but there is no > message saying why. > # When I attempt to download image, it does nothing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844129#comment-17844129 ] Brijesh Bhalala commented on ATLAS-4860: commited to [Apache master|https://github.com/apache/atlas/commit/3879f460188ca0747a0b7223abbb25897ccabc46] branch > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > 0002-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843837#comment-17843837 ] ASF subversion and git services commented on ATLAS-4860: Commit 7541afa2f3fea0c8242db07ca9091e14ef060952 in atlas's branch refs/heads/branch-2.0 from Brijesh Bhalala [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7541afa2f ] ATLAS-4860: UI: If deleted entity has long name, propertytab in UI is misaligned Signed-off-by: Prasad Pawar > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > 0002-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843836#comment-17843836 ] ASF subversion and git services commented on ATLAS-4860: Commit 3879f460188ca0747a0b7223abbb25897ccabc46 in atlas's branch refs/heads/master from Brijesh Bhalala [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3879f4601 ] ATLAS-4860: UI: If deleted entity has long name, propertytab in UI is misaligned Signed-off-by: Prasad Pawar > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > 0002-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843737#comment-17843737 ] Rahul Kurup edited comment on ATLAS-4860 at 5/6/24 12:56 PM: - +1 was (Author: rahul_fi): https://issues.apache.org/jira/browse/ATLAS-4860 > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > 0002-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843737#comment-17843737 ] Rahul Kurup commented on ATLAS-4860: https://issues.apache.org/jira/browse/ATLAS-4860 > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > 0002-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4860: --- Attachment: 0002-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > 0002-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4225) Support for Chinese character in entity data.
[ https://issues.apache.org/jira/browse/ATLAS-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843125#comment-17843125 ] ASF subversion and git services commented on ATLAS-4225: Commit 09d3f693d934fcae624651489d3e795043364f48 in atlas's branch refs/heads/branch-2.0 from chaitali.borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=09d3f693d ] ATLAS-4225 : Support for Chinese character in Atlas entities Signed-off-by: Pinal Shah > Support for Chinese character in entity data. > - > > Key: ATLAS-4225 > URL: https://issues.apache.org/jira/browse/ATLAS-4225 > Project: Atlas > Issue Type: New Feature >Reporter: Mayank Jain >Assignee: chaitali borole >Priority: Major > Attachments: ATLAS-4225-3.patch > > > Currently we only allow English characters to be used to adding entity data > that is labels , Custom Attributes and Business-Metadata. > > We need to support for Chinese and other languages as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4225) Support for Chinese character in entity data.
[ https://issues.apache.org/jira/browse/ATLAS-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843124#comment-17843124 ] ASF subversion and git services commented on ATLAS-4225: Commit f46d1c47ecca48da9ca13578ea44ba4fe31ce57a in atlas's branch refs/heads/master from chaitali.borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f46d1c47e ] ATLAS-4225 : Support for Chinese character in Atlas entities Signed-off-by: Pinal Shah > Support for Chinese character in entity data. > - > > Key: ATLAS-4225 > URL: https://issues.apache.org/jira/browse/ATLAS-4225 > Project: Atlas > Issue Type: New Feature >Reporter: Mayank Jain >Assignee: chaitali borole >Priority: Major > Attachments: ATLAS-4225-3.patch > > > Currently we only allow English characters to be used to adding entity data > that is labels , Custom Attributes and Business-Metadata. > > We need to support for Chinese and other languages as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4860: --- Attachment: 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4860: --- Fix Version/s: 3.0.0 > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4860: --- Attachment: misaligned_UI.png > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Attachments: misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
Brijesh Bhalala created ATLAS-4860: -- Summary: UI : If deleted entity has long name, propertytab in UI is misaligned Key: ATLAS-4860 URL: https://issues.apache.org/jira/browse/ATLAS-4860 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Brijesh Bhalala Assignee: Brijesh Bhalala Please check the screenshot where the entity is deleted and the property tab of the entity looks misaligned. This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4858) Revisit the Atlas solr config like autoCommit, autoSoftCommit
[ https://issues.apache.org/jira/browse/ATLAS-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheetal Shah reassigned ATLAS-4858: --- Assignee: Sheetal Shah > Revisit the Atlas solr config like autoCommit, autoSoftCommit > - > > Key: ATLAS-4858 > URL: https://issues.apache.org/jira/browse/ATLAS-4858 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Sheetal Shah >Assignee: Sheetal Shah >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4859) NPE during Atlas Import
Priyanshi Shah created ATLAS-4859: - Summary: NPE during Atlas Import Key: ATLAS-4859 URL: https://issues.apache.org/jira/browse/ATLAS-4859 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Priyanshi Shah Assignee: Priyanshi Shah Fix For: 3.0.0, 2.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4858) Revisit the Atlas solr config like autoCommit, autoSoftCommit
Sheetal Shah created ATLAS-4858: --- Summary: Revisit the Atlas solr config like autoCommit, autoSoftCommit Key: ATLAS-4858 URL: https://issues.apache.org/jira/browse/ATLAS-4858 Project: Atlas Issue Type: Task Components: atlas-core Reporter: Sheetal Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4857) Atlas - Upgrade Spring Framework to 6.1.6/6.0.19/5.3.34 due to CVE-2024-22243, CVE-2024-22259 and CVE-2024-22262
Sheetal Shah created ATLAS-4857: --- Summary: Atlas - Upgrade Spring Framework to 6.1.6/6.0.19/5.3.34 due to CVE-2024-22243, CVE-2024-22259 and CVE-2024-22262 Key: ATLAS-4857 URL: https://issues.apache.org/jira/browse/ATLAS-4857 Project: Atlas Issue Type: Task Components: atlas-core Reporter: Sheetal Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4225) Support for Chinese character in entity data.
[ https://issues.apache.org/jira/browse/ATLAS-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841448#comment-17841448 ] chaitali borole commented on ATLAS-4225: In below case this above patch won't work : Description field contains "THIS IS DESCRIPTION FIELD". Now, if we search for each word separately, i.e., (THIS, IS, DESCRIPTION, or FIELD), we will get the output. However, if we search for "THIS IS" or "DESCRIPTION FIELD", it will not work as the space acts as a delimiter here. So (THIS - 1st Token) (IS 2nd Token) and so on.. Similarly, in the case of CJK, "期日" each character is a token. So, if we search for "期", we will get the response or if we search for "日", we will get the response. However, if we search for "期日" together, we will not get an answer. though this works as per design similar to English characters. > Support for Chinese character in entity data. > - > > Key: ATLAS-4225 > URL: https://issues.apache.org/jira/browse/ATLAS-4225 > Project: Atlas > Issue Type: New Feature >Reporter: Mayank Jain >Assignee: chaitali borole >Priority: Major > Attachments: ATLAS-4225-3.patch > > > Currently we only allow English characters to be used to adding entity data > that is labels , Custom Attributes and Business-Metadata. > > We need to support for Chinese and other languages as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4225) Support for Chinese character in entity data.
[ https://issues.apache.org/jira/browse/ATLAS-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-4225: -- Assignee: chaitali borole (was: Mayank Jain) > Support for Chinese character in entity data. > - > > Key: ATLAS-4225 > URL: https://issues.apache.org/jira/browse/ATLAS-4225 > Project: Atlas > Issue Type: New Feature >Reporter: Mayank Jain >Assignee: chaitali borole >Priority: Major > Attachments: ATLAS-4225-3.patch > > > Currently we only allow English characters to be used to adding entity data > that is labels , Custom Attributes and Business-Metadata. > > We need to support for Chinese and other languages as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4856) Parallel Atlas Import is failing with unexpected errors
[ https://issues.apache.org/jira/browse/ATLAS-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4856: -- Description: PermanentLockingException was thrown while running parallel imports. > Parallel Atlas Import is failing with unexpected errors > --- > > Key: ATLAS-4856 > URL: https://issues.apache.org/jira/browse/ATLAS-4856 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > PermanentLockingException was thrown while running parallel imports. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4856) Parallel Atlas Import is failing with unexpected errors
[ https://issues.apache.org/jira/browse/ATLAS-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah reassigned ATLAS-4856: - Assignee: Priyanshi Shah > Parallel Atlas Import is failing with unexpected errors > --- > > Key: ATLAS-4856 > URL: https://issues.apache.org/jira/browse/ATLAS-4856 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4856) Parallel Atlas Import is failing with unexpected errors
Priyanshi Shah created ATLAS-4856: - Summary: Parallel Atlas Import is failing with unexpected errors Key: ATLAS-4856 URL: https://issues.apache.org/jira/browse/ATLAS-4856 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Priyanshi Shah Fix For: 3.0.0, 2.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ATLAS-4849) Initial React setup for Atlas New UI
[ https://issues.apache.org/jira/browse/ATLAS-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839033#comment-17839033 ] Brijesh Bhalala edited comment on ATLAS-4849 at 4/25/24 11:01 AM: -- Combined patch uploaded on ATLAS-4850 JIRA was (Author: JIRAUSER294659): Combined patch uploaded on ATLAS-4849 JIRA > Initial React setup for Atlas New UI > > > Key: ATLAS-4849 > URL: https://issues.apache.org/jira/browse/ATLAS-4849 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > * Initial setup of react for atlas new UI which includes :- > # Dev and Prod env Configuration. > # Folder structure. > # Installation of Libraries in React. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4855) Atlas - Upgrade Nimbus-JOSE-JWT to 9.37.3
[ https://issues.apache.org/jira/browse/ATLAS-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-4855: --- Description: Atlas is currently pulling in nimbus-jose-jwt 9.8.1. Upgrate it to 9.37.3 > Atlas - Upgrade Nimbus-JOSE-JWT to 9.37.3 > - > > Key: ATLAS-4855 > URL: https://issues.apache.org/jira/browse/ATLAS-4855 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Atlas is currently pulling in nimbus-jose-jwt 9.8.1. Upgrate it to 9.37.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4855) Atlas - Upgrade Nimbus-JOSE-JWT to 9.37.3
Mandar Ambawane created ATLAS-4855: -- Summary: Atlas - Upgrade Nimbus-JOSE-JWT to 9.37.3 Key: ATLAS-4855 URL: https://issues.apache.org/jira/browse/ATLAS-4855 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4854) Atlas - Upgrade Spring Security to 5.8.11
[ https://issues.apache.org/jira/browse/ATLAS-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4854: -- Description: Upgrading spring security from 5.8.5 to 5.8.11 > Atlas - Upgrade Spring Security to 5.8.11 > - > > Key: ATLAS-4854 > URL: https://issues.apache.org/jira/browse/ATLAS-4854 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Fix For: 3.0.0 > > > Upgrading spring security from 5.8.5 to 5.8.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4854) Atlas - Upgrade Spring Security to 5.8.11
Priyanshi Shah created ATLAS-4854: - Summary: Atlas - Upgrade Spring Security to 5.8.11 Key: ATLAS-4854 URL: https://issues.apache.org/jira/browse/ATLAS-4854 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Priyanshi Shah Fix For: 3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4854) Atlas - Upgrade Spring Security to 5.8.11
[ https://issues.apache.org/jira/browse/ATLAS-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah reassigned ATLAS-4854: - Assignee: Priyanshi Shah > Atlas - Upgrade Spring Security to 5.8.11 > - > > Key: ATLAS-4854 > URL: https://issues.apache.org/jira/browse/ATLAS-4854 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4844) Atlas - Upgrade Common Configuration2 to 2.10.1
[ https://issues.apache.org/jira/browse/ATLAS-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4844: -- Due Date: (was: 2/Apr/24) > Atlas - Upgrade Common Configuration2 to 2.10.1 > --- > > Key: ATLAS-4844 > URL: https://issues.apache.org/jira/browse/ATLAS-4844 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > > Upgrading common configurations2 from 2.8.0 to 2.10.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4853) Upgrade Netty to 4.1.108.Final due to CVE-2024-29025
Disha Talreja created ATLAS-4853: Summary: Upgrade Netty to 4.1.108.Final due to CVE-2024-29025 Key: ATLAS-4853 URL: https://issues.apache.org/jira/browse/ATLAS-4853 Project: Atlas Issue Type: Task Components: atlas-core Reporter: Disha Talreja Assignee: Disha Talreja Upgrade Netty to 4.1.108.Final due to CVE-2024-29025 Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. The `HttpPostRequestDecoder` can be tricked to accumulate data. While the decoder can store items on the disk if configured so, there are no limits to the number of fields the form can have, an attacher can send a chunked post consisting of many small fields that will be accumulated in the `bodyListHttpData` list. The decoder cumulates bytes in the `undecodedChunk` buffer until it can decode a field, this field can cumulate data without limits. This vulnerability is fixed in 4.1.108.Final. [https://nvd.nist.gov/vuln/detail/CVE-2024-29025] [https://github.com/advisories/GHSA-5jpm-x58v-624v] [https://ossindex.sonatype.org/vulnerability/CVE-2024-29025] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4830) Make ignore patterns generic for all the hooks
[ https://issues.apache.org/jira/browse/ATLAS-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruth S updated ATLAS-4830: Attachment: HLDD for Generic Ignore Patterns.pdf > Make ignore patterns generic for all the hooks > -- > > Key: ATLAS-4830 > URL: https://issues.apache.org/jira/browse/ATLAS-4830 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: Radhika Kundam >Assignee: Amruth S >Priority: Major > Attachments: HLDD for Generic Ignore Patterns.pdf > > > Currently the ignore patterns are only applicable for hive tables, but in few > escalations we have seen that there was a need to see if we can add ignore > patterns for other components as well, like spark, etc. > So we need to make these ignore patterns generic, so that it works for all > hooks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4849) Initial React setup for Atlas New UI
[ https://issues.apache.org/jira/browse/ATLAS-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839033#comment-17839033 ] Brijesh Bhalala commented on ATLAS-4849: Combined patch uploaded on ATLAS-4849 JIRA > Initial React setup for Atlas New UI > > > Key: ATLAS-4849 > URL: https://issues.apache.org/jira/browse/ATLAS-4849 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > * Initial setup of react for atlas new UI which includes :- > # Dev and Prod env Configuration. > # Folder structure. > # Installation of Libraries in React. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4850) Left Sidebar layout for Atlas New UI
[ https://issues.apache.org/jira/browse/ATLAS-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4850: --- Attachment: 0001-ATLAS-4849-ATLAS-4850-ATLAS-UI-Initial-React-setup-L.patch > Left Sidebar layout for Atlas New UI > > > Key: ATLAS-4850 > URL: https://issues.apache.org/jira/browse/ATLAS-4850 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4849-ATLAS-4850-ATLAS-UI-Initial-React-setup-L.patch > > > * Left Sidebar layout :- > # Layout part which includes Header, Left Sidebar > # Sidebar layout with Tree Structure and Search Bar. > # Tree Structure :- > 1) Entities. > 2) Classifications. > 3) Business metadata. > 4) Glossaries. > 5) Relationships. > 6) Custom Filters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Description: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Table View on search page :- * Search page Table view. * Query Builder. 4. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. was: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Table View on search page :- * Search page Table view. * Query Builder. > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. > Sub Tasks :- > # Initial React Setup :- > * Dev and Prod env Configuration. > * Folder structure. > * Installation of Libraries in React. > 2. Left Sidebar Layout :- > * Tree Structure and Search Bar. > 3. Table View on search page :- > * Search page Table view. > * Query Builder. > 4. Global Search Bar on Header :- > * Global search bar for entities search. > * Advance & Quick Search. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4852) Global Search bar in Header
[ https://issues.apache.org/jira/browse/ATLAS-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4852: --- Description: Global search at landing page in Header. * Global search filter for searching Entities. * Advance & Quick search was:Global search > Global Search bar in Header > --- > > Key: ATLAS-4852 > URL: https://issues.apache.org/jira/browse/ATLAS-4852 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > Global search at landing page in Header. > * Global search filter for searching Entities. > * Advance & Quick search -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4852) Global Search bar in Header
[ https://issues.apache.org/jira/browse/ATLAS-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4852: --- Description: Global search > Global Search bar in Header > --- > > Key: ATLAS-4852 > URL: https://issues.apache.org/jira/browse/ATLAS-4852 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > Global search -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4852) Global Search bar in Header
Brijesh Bhalala created ATLAS-4852: -- Summary: Global Search bar in Header Key: ATLAS-4852 URL: https://issues.apache.org/jira/browse/ATLAS-4852 Project: Atlas Issue Type: Sub-task Components: atlas-webui Reporter: Brijesh Bhalala Assignee: Brijesh Bhalala -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Description: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Table View on search page :- * Search page Table view. * Query Builder. was: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Task :- # ATLAS-4849 :- Initial React setup for Atlas New UI. # ATLAS-4850 :- Left Sidebar layout for Atlas New UI. > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. > Sub Tasks :- > # Initial React Setup :- > * Dev and Prod env Configuration. > * Folder structure. > * Installation of Libraries in React. > 2. Left Sidebar Layout :- > * Tree Structure and Search Bar. > 3. Table View on search page :- > * Search page Table view. > * Query Builder. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4851) Table view on search page module
[ https://issues.apache.org/jira/browse/ATLAS-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4851: --- Labels: atlas-react (was: ) > Table view on search page module > - > > Key: ATLAS-4851 > URL: https://issues.apache.org/jira/browse/ATLAS-4851 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > * Right Side Content body on landing page includes: - > # Search page Table view. > # Table functionality which includes Sorting, Column Show/Hide Options, Row > Selection, Column Drag & Drop. > # Query Builder -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4851) Table view on search page module
[ https://issues.apache.org/jira/browse/ATLAS-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4851: --- Description: * Right Side Content body on landing page includes: - # Search page Table view. # Table functionality which includes Sorting, Column Show/Hide Options, Row Selection, Column Drag & Drop. # Query Builder was: * Right Side Content body on landing page includes: - 1)Search page Table view. 2)Table functionality which includes Sorting, Column Show/Hide Options, Row Selection, Column Drag & Drop. 3)Query Builder. > Table view on search page module > - > > Key: ATLAS-4851 > URL: https://issues.apache.org/jira/browse/ATLAS-4851 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > * Right Side Content body on landing page includes: - > # Search page Table view. > # Table functionality which includes Sorting, Column Show/Hide Options, Row > Selection, Column Drag & Drop. > # Query Builder -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4851) Table view on search page module
[ https://issues.apache.org/jira/browse/ATLAS-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4851: --- Description: * Right Side Content body on landing page includes: - 1)Search page Table view. 2)Table functionality which includes Sorting, Column Show/Hide Options, Row Selection, Column Drag & Drop. 3)Query Builder. > Table view on search page module > - > > Key: ATLAS-4851 > URL: https://issues.apache.org/jira/browse/ATLAS-4851 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > * Right Side Content body on landing page includes: - > 1)Search page Table view. > 2)Table functionality which includes Sorting, Column Show/Hide > Options, Row Selection, Column Drag & Drop. > 3)Query Builder. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4851) Table view on search page module
[ https://issues.apache.org/jira/browse/ATLAS-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4851: --- Description: * Right Side Content body on landing page includes: - 1)Search page Table view. 2)Table functionality which includes Sorting, Column Show/Hide Options, Row Selection, Column Drag & Drop. 3)Query Builder. was: * Right Side Content body on landing page includes: - 1)Search page Table view. 2)Table functionality which includes Sorting, Column Show/Hide Options, Row Selection, Column Drag & Drop. 3)Query Builder. > Table view on search page module > - > > Key: ATLAS-4851 > URL: https://issues.apache.org/jira/browse/ATLAS-4851 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > * Right Side Content body on landing page includes: - > 1)Search page Table view. > 2)Table functionality which includes Sorting, Column Show/Hide > Options, > Row Selection, Column Drag & Drop. > 3)Query Builder. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4851) Table view on search page module
Brijesh Bhalala created ATLAS-4851: -- Summary: Table view on search page module Key: ATLAS-4851 URL: https://issues.apache.org/jira/browse/ATLAS-4851 Project: Atlas Issue Type: Sub-task Components: atlas-webui Reporter: Brijesh Bhalala Assignee: Brijesh Bhalala -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Description: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Task :- # ATLAS-4849 :- Initial React setup for Atlas New UI. # ATLAS-4850 :- Left Sidebar layout for Atlas New UI. was: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Task :- # ATLAS-4849 :- Initial React setup for Atlas New UI > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. > Sub Task :- > # ATLAS-4849 :- Initial React setup for Atlas New UI. > # ATLAS-4850 :- Left Sidebar layout for Atlas New UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4850) Left Sidebar layout for Atlas New UI
[ https://issues.apache.org/jira/browse/ATLAS-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4850: --- Description: * Left Sidebar layout :- # Layout part which includes Header, Left Sidebar # Sidebar layout with Tree Structure and Search Bar. # Tree Structure :- 1) Entities. 2) Classifications. 3) Business metadata. 4) Glossaries. 5) Relationships. 6) Custom Filters. > Left Sidebar layout for Atlas New UI > > > Key: ATLAS-4850 > URL: https://issues.apache.org/jira/browse/ATLAS-4850 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > * Left Sidebar layout :- > # Layout part which includes Header, Left Sidebar > # Sidebar layout with Tree Structure and Search Bar. > # Tree Structure :- > 1) Entities. > 2) Classifications. > 3) Business metadata. > 4) Glossaries. > 5) Relationships. > 6) Custom Filters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4850) Left Sidebar layout for Atlas New UI
Brijesh Bhalala created ATLAS-4850: -- Summary: Left Sidebar layout for Atlas New UI Key: ATLAS-4850 URL: https://issues.apache.org/jira/browse/ATLAS-4850 Project: Atlas Issue Type: Sub-task Components: atlas-webui Reporter: Brijesh Bhalala Assignee: Brijesh Bhalala -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Description: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Task :- # ATLAS-4849 :- Initial React setup for Atlas New UI was: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. > Sub Task :- > # ATLAS-4849 :- Initial React setup for Atlas New UI -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4849) Initial React setup for Atlas New UI
[ https://issues.apache.org/jira/browse/ATLAS-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4849: --- Description: * Initial setup of react for atlas new UI which includes :- # Dev and Prod env Configuration. # Folder structure. # Installation of Libraries in React. > Initial React setup for Atlas New UI > > > Key: ATLAS-4849 > URL: https://issues.apache.org/jira/browse/ATLAS-4849 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > * Initial setup of react for atlas new UI which includes :- > # Dev and Prod env Configuration. > # Folder structure. > # Installation of Libraries in React. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4849) Initial React setup for Atlas New UI
[ https://issues.apache.org/jira/browse/ATLAS-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4849: --- Labels: atlas-react (was: ) > Initial React setup for Atlas New UI > > > Key: ATLAS-4849 > URL: https://issues.apache.org/jira/browse/ATLAS-4849 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > * Initial setup of react for atlas new UI which includes :- > # Dev and Prod env Configuration. > # Folder structure. > # Installation of Libraries in React. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Labels: atlas-react (was: ) > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4849) Initial React setup for Atlas New UI
Brijesh Bhalala created ATLAS-4849: -- Summary: Initial React setup for Atlas New UI Key: ATLAS-4849 URL: https://issues.apache.org/jira/browse/ATLAS-4849 Project: Atlas Issue Type: Sub-task Components: atlas-webui Reporter: Brijesh Bhalala Assignee: Brijesh Bhalala -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reassigned ATLAS-4597: -- Assignee: Brijesh Bhalala (was: Farhan Khan) > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Fix Version/s: 3.0.0 2.3.0 > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: ATLAS-4847.patch, NullPointerException_stackTrace.txt > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > Problem is it throws NullPointerException and export is failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4842) Export/Import: fetchType as "incremental" does full export instead of connected
[ https://issues.apache.org/jira/browse/ATLAS-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4842: -- Fix Version/s: 3.0.0 2.3.0 > Export/Import: fetchType as "incremental" does full export instead of > connected > --- > > Key: ATLAS-4842 > URL: https://issues.apache.org/jira/browse/ATLAS-4842 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sheetal Shah >Assignee: Priyanshi Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: ATLAS-4842.patch > > > Create two hive_tables in same database: > # create table hive1(id int); > # create table hive1_ctas as select * from hive1; > # create table hive2(name string); > Perform incremental export of hive1 with changeMarker as 0 and skipLineage > value as false. > Import the zip. > Expectation is only the requested hive_table hive1 and its related entities > should be exported, but it does full export and hive2 is also imported. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4845) Atlas Import is failing with fetchType: Incremental if there are no changes between two consecutive runs
[ https://issues.apache.org/jira/browse/ATLAS-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4845: -- Fix Version/s: 3.0.0 2.3.0 > Atlas Import is failing with fetchType: Incremental if there are no changes > between two consecutive runs > > > Key: ATLAS-4845 > URL: https://issues.apache.org/jira/browse/ATLAS-4845 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: ATLAS-4845.patch > > > Repro steps: > # First export + import with changeMarker “0” - worked as expected. > # I tried to run 2nd export + import without any changes in atlas, 2nd > export also worked and gave different changeMarker in output as expected. > *But 2nd import failed* > In other fetch Types this will work. So we also require similar behaviour in > case of Incremental type also because this is very normal scenario and > customer will hit this very frequently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4838) Export/Import : changeMarker is not set to entity's lastupdatetime or its closer timestamp value
[
https://issues.apache.org/jira/browse/ATLAS-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanshi Shah updated ATLAS-4838:
--
Fix Version/s: 3.0.0
2.3.0
> Export/Import : changeMarker is not set to entity's lastupdatetime or its
> closer timestamp value
>
>
> Key: ATLAS-4838
> URL: https://issues.apache.org/jira/browse/ATLAS-4838
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Sharmadha S
>Assignee: Priyanshi Shah
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: ATLAS-4838-V2.patch
>
>
> When an hive table entity is exported using fetchType incremental with
> changeMarker 0 , after exporting , the changeMarker in the export response is
> not set to recent timestamp.
> For example , on exporting iceberg table with fetchType incremental and
> changeMarker as 0 :
> {code:java}
> 2024-02-08 13:28:43,838 INFO - [etp891461509-20 -
> db3f1141-531c-46c0-909a-5e443d4353a2:] ~
> export(item=AtlasObjectId{guid='null', typeName='iceberg_table',
> uniqueAttributes={qualifiedName:default.iceberg_table2@cm}}; matchType=null,
> fetchType=incremental): found 1 entities: options:
> {"itemsToExport":[{"typeName":"iceberg_table","uniqueAttributes":{"qualifiedName":"default.iceberg_table2@cm"}}],"options":{"fetchType":"incremental","changeMarker":0},"fetchTypeOptionValue":"incremental","skipLineageOptionValue":false,"changeTokenFromOptions":0}
> (StartEntityFetchByExportRequest:123)
> 2024-02-08 13:28:48,697 INFO - [etp891461509-20 -
> db3f1141-531c-46c0-909a-5e443d4353a2:] ~ Assigned guid =
> f5e6342a-dfdf-4d54-a1b3-b24f987c4ecb to newly created entity (DataAccess:85)
> 2024-02-08 13:28:48,697 INFO - [etp891461509-20 -
> db3f1141-531c-46c0-909a-5e443d4353a2:] ~ addAuditEntry: user: admin, source:
> cm, target: , operation: EXPORT (ExportImportAuditService:168)
> 2024-02-08 13:28:48,699 INFO - [etp891461509-20 -
> db3f1141-531c-46c0-909a-5e443d4353a2:] ~ <== export(user=admin,
> from=10.19.28.124): status SUCCESS: changeMarker: 1707225183928
> (ExportService:107) {code}
> changeMarker from response is 1707225183928 => Tuesday, February 6, 2024
> 6:43:03.928 PM
>
> But lastUpdatetime of iceberg table is
> {code:java}
> "createTime": 1707398866970 => Thursday, February 8, 2024 6:57:46.970 PM
> "updateTime": 1707398867375. => Thursday, February 8, 2024 6:57:47.375 PM
> {code}
> Value is set to 2 days back. This is not then an incremental export , as it
> will fetch all updates from Tuesday, February 6, 2024 6:43:03.928 PM in next
> export
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Attachment: NullPointerException_stackTrace.txt > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: ATLAS-4847.patch, NullPointerException_stackTrace.txt > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > Problem is it throws NullPointerException and export is failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[
https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanshi Shah updated ATLAS-4847:
--
Description:
Steps to reproduce:
1. Create a hive_table entity and assign a term to it.
2. Perform 1st incremental export of that entity without using changeMarker.
3. Without any modification on that entity perform 2nd consecutive incremental
export with changeMarker from previous export.
Problem is it throws NullPointerException and export is failed.
was:
Steps to reproduce:
1. Create a hive_table entity and assign a term to it.
2. Perform 1st incremental export of that entity without using changeMarker.
3. Without any modification on that entity perform 2nd consecutive incremental
export with changeMarker from previous export.
Problem is it throws NullPointerException and export is failed.
Application.log
2024-04-10 17:49:44,148 INFO - [etp370869802-458 -
76b2eeb5-22fb-4631-a99a-2567c307152a:] ~ ==> export(user=admin, from=127.0.0.1)
(ExportService:95)
2024-04-10 17:49:44,219 INFO - [etp370869802-458 -
76b2eeb5-22fb-4631-a99a-2567c307152a:] ~
export(item=AtlasObjectId\{guid='null', typeName='hive_table',
uniqueAttributes={qualifiedName:test_db.abc__hive_impala_table_1@cm}};
matchType=null, fetchType=INCREMENTAL): found 1 entities: options:
\{"itemsToExport":[{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"test_db.abc__hive_impala_table_1@cm"}}],"options":\{"fetchType":"INCREMENTAL","changeMarker":1712751459762},"fetchTypeOptionValue":"INCREMENTAL","skipLineageOptionValue":false,"omitZipResponseForEmptyExport":false,"changeTokenFromOptions":1712751459762}
(StartEntityFetchByExportRequest:123)
2024-04-10 17:49:44,242 ERROR - [etp370869802-458 -
76b2eeb5-22fb-4631-a99a-2567c307152a:] ~ Operation failed: (ExportService:103)
java.lang.{color:#de350b}NullPointerException{color}
at
org.apache.atlas.repository.impexp.ExportService$ExportContext.getEntitiesWithModifiedTimestamp(ExportService.java:445)
at
org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:332)
at
org.apache.atlas.repository.impexp.ExportService.addGlossaryEntities(ExportService.java:299)
at
org.apache.atlas.repository.impexp.ExportService.processEntity(ExportService.java:274)
> Export/Import : Atlas export fails and throws NullPointerException.
> ---
>
> Key: ATLAS-4847
> URL: https://issues.apache.org/jira/browse/ATLAS-4847
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Priyanshi Shah
>Assignee: Priyanshi Shah
>Priority: Major
> Attachments: ATLAS-4847.patch, NullPointerException_stackTrace.txt
>
>
> Steps to reproduce:
> 1. Create a hive_table entity and assign a term to it.
> 2. Perform 1st incremental export of that entity without using changeMarker.
> 3. Without any modification on that entity perform 2nd consecutive
> incremental export with changeMarker from previous export.
> Problem is it throws NullPointerException and export is failed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[
https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanshi Shah updated ATLAS-4847:
--
Description:
Steps to reproduce:
1. Create a hive_table entity and assign a term to it.
2. Perform 1st incremental export of that entity without using changeMarker.
3. Without any modification on that entity perform 2nd consecutive incremental
export with changeMarker from previous export.
Problem is it throws NullPointerException and export is failed.
Application.log
2024-04-10 17:49:44,148 INFO - [etp370869802-458 -
76b2eeb5-22fb-4631-a99a-2567c307152a:] ~ ==> export(user=admin, from=127.0.0.1)
(ExportService:95)
2024-04-10 17:49:44,219 INFO - [etp370869802-458 -
76b2eeb5-22fb-4631-a99a-2567c307152a:] ~
export(item=AtlasObjectId\{guid='null', typeName='hive_table',
uniqueAttributes={qualifiedName:test_db.abc__hive_impala_table_1@cm}};
matchType=null, fetchType=INCREMENTAL): found 1 entities: options:
\{"itemsToExport":[{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"test_db.abc__hive_impala_table_1@cm"}}],"options":\{"fetchType":"INCREMENTAL","changeMarker":1712751459762},"fetchTypeOptionValue":"INCREMENTAL","skipLineageOptionValue":false,"omitZipResponseForEmptyExport":false,"changeTokenFromOptions":1712751459762}
(StartEntityFetchByExportRequest:123)
2024-04-10 17:49:44,242 ERROR - [etp370869802-458 -
76b2eeb5-22fb-4631-a99a-2567c307152a:] ~ Operation failed: (ExportService:103)
java.lang.{color:#de350b}NullPointerException{color}
at
org.apache.atlas.repository.impexp.ExportService$ExportContext.getEntitiesWithModifiedTimestamp(ExportService.java:445)
at
org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:332)
at
org.apache.atlas.repository.impexp.ExportService.addGlossaryEntities(ExportService.java:299)
at
org.apache.atlas.repository.impexp.ExportService.processEntity(ExportService.java:274)
was:
Steps to reproduce:
1. Create a hive_table entity and assign a term to it.
2. Perform 1st incremental export of that entity without using changeMarker.
3. Without any modification on that entity perform 2nd consecutive incremental
export with changeMarker from previous export.
Problem is it throws NullPointerException and export is failed.
> Export/Import : Atlas export fails and throws NullPointerException.
> ---
>
> Key: ATLAS-4847
> URL: https://issues.apache.org/jira/browse/ATLAS-4847
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Priyanshi Shah
>Assignee: Priyanshi Shah
>Priority: Major
> Attachments: ATLAS-4847.patch
>
>
> Steps to reproduce:
> 1. Create a hive_table entity and assign a term to it.
> 2. Perform 1st incremental export of that entity without using changeMarker.
> 3. Without any modification on that entity perform 2nd consecutive
> incremental export with changeMarker from previous export.
> Problem is it throws NullPointerException and export is failed.
>
> Application.log
> 2024-04-10 17:49:44,148 INFO - [etp370869802-458 -
> 76b2eeb5-22fb-4631-a99a-2567c307152a:] ~ ==> export(user=admin,
> from=127.0.0.1) (ExportService:95)
> 2024-04-10 17:49:44,219 INFO - [etp370869802-458 -
> 76b2eeb5-22fb-4631-a99a-2567c307152a:] ~
> export(item=AtlasObjectId\{guid='null', typeName='hive_table',
> uniqueAttributes={qualifiedName:test_db.abc__hive_impala_table_1@cm}};
> matchType=null, fetchType=INCREMENTAL): found 1 entities: options:
> \{"itemsToExport":[{"typeName":"hive_table","uniqueAttributes":{"qualifiedName":"test_db.abc__hive_impala_table_1@cm"}}],"options":\{"fetchType":"INCREMENTAL","changeMarker":1712751459762},"fetchTypeOptionValue":"INCREMENTAL","skipLineageOptionValue":false,"omitZipResponseForEmptyExport":false,"changeTokenFromOptions":1712751459762}
> (StartEntityFetchByExportRequest:123)
> 2024-04-10 17:49:44,242 ERROR - [etp370869802-458 -
> 76b2eeb5-22fb-4631-a99a-2567c307152a:] ~ Operation failed:
> (ExportService:103)
> java.lang.{color:#de350b}NullPointerException{color}
> at
> org.apache.atlas.repository.impexp.ExportService$ExportContext.getEntitiesWithModifiedTimestamp(ExportService.java:445)
> at
> org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:332)
> at
> org.apache.atlas.repository.impexp.ExportService.addGlossaryEntities(ExportService.java:299)
> at
> org.apache.atlas.repository.impexp.ExportService.processEntity(ExportService.java:274)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Attachment: (was: image-2024-04-11-15-15-59-551.png) > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: ATLAS-4847.patch > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > Problem is it throws NullPointerException and export is failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Attachment: ATLAS-4847.patch > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: ATLAS-4847.patch, image-2024-04-11-15-15-59-551.png > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > Problem is it throws NullPointerException and export is failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836457#comment-17836457 ] ASF subversion and git services commented on ATLAS-4847: Commit ec44700a318d17f6fb78c588e0d3a4a4c0f8904b in atlas's branch refs/heads/branch-2.0 from priyanshi-shah26 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ec44700a3 ] ATLAS-4847 : Export/Import : Atlas export fails and throws NullPointerException Signed-off-by: Pinal Shah > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: image-2024-04-11-15-15-59-551.png > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > Problem is it throws NullPointerException and export is failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836456#comment-17836456 ] ASF subversion and git services commented on ATLAS-4847: Commit 94083a3802dfe6f712e2c2d8cf777311ad5ca34b in atlas's branch refs/heads/master from priyanshi-shah26 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=94083a380 ] ATLAS-4847 : Export/Import : Atlas export fails and throws NullPointerException Signed-off-by: Pinal Shah > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: image-2024-04-11-15-15-59-551.png > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > Problem is it throws NullPointerException and export is failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4848) Atlas 'updateTime' parameter is not updated when term is added.
Priyanshi Shah created ATLAS-4848: - Summary: Atlas 'updateTime' parameter is not updated when term is added. Key: ATLAS-4848 URL: https://issues.apache.org/jira/browse/ATLAS-4848 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Priyanshi Shah Assignee: Priyanshi Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Description: Steps to reproduce: 1. Create a hive_table entity and assign a term to it. 2. Perform 1st incremental export of that entity without using changeMarker. 3. Without any modification on that entity perform 2nd consecutive incremental export with changeMarker from previous export. Problem is it throws NullPointerException and export is failed. was: Steps to reproduce: 1. Create a hive_table entity and assign a term to it. 2. Perform 1st incremental export of that entity without using changeMarker. 3. Without any modification on that entity perform 2nd consecutive incremental export with changeMarker from previous export. > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: image-2024-04-11-15-15-59-551.png > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > Problem is it throws NullPointerException and export is failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Description: Steps to reproduce: 1. Create a hive_table entity and assign a term to it. 2. Perform 1st incremental export of that entity without using changeMarker. 3. Without any modification on that entity perform 2nd consecutive incremental export with changeMarker from previous export. was: Steps to reproduce: 1. Create a hive_table entity and assign a term to it. 2. Perform 1st incremental export of that entity without using changeMarker. 3. Without any modification on that entity perform 2nd consecutive incremental export with changeMarker from previous export. !image-2024-04-11-15-15-59-551.png! > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: image-2024-04-11-15-15-59-551.png > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Attachment: image-2024-04-11-15-15-59-551.png > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: image-2024-04-11-15-15-59-551.png > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > Problem is it fails export and throws NullPointerException. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Description: Steps to reproduce: 1. Create a hive_table entity and assign a term to it. 2. Perform 1st incremental export of that entity without using changeMarker. 3. Without any modification on that entity perform 2nd consecutive incremental export with changeMarker from previous export. !image-2024-04-11-15-15-59-551.png! was: Steps to reproduce: 1. Create a hive_table entity and assign a term to it. 2. Perform 1st incremental export of that entity without using changeMarker. 3. Without any modification on that entity perform 2nd consecutive incremental export with changeMarker from previous export. Problem is it fails export and throws NullPointerException. > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: image-2024-04-11-15-15-59-551.png > > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > !image-2024-04-11-15-15-59-551.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Description: Steps to reproduce: 1. Create a hive_table entity and assign a term to it. 2. Perform 1st incremental export of that entity without using changeMarker. 3. Without any modification on that entity perform 2nd consecutive incremental export with changeMarker from previous export. Problem is it fails export and throws NullPointerException. > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > > Steps to reproduce: > 1. Create a hive_table entity and assign a term to it. > 2. Perform 1st incremental export of that entity without using changeMarker. > 3. Without any modification on that entity perform 2nd consecutive > incremental export with changeMarker from previous export. > Problem is it fails export and throws NullPointerException. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4845) Atlas Import is failing with fetchType: Incremental if there are no changes between two consecutive runs
[ https://issues.apache.org/jira/browse/ATLAS-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4845: -- Description: Repro steps: # First export + import with changeMarker “0” - worked as expected. # I tried to run 2nd export + import without any changes in atlas, 2nd export also worked and gave different changeMarker in output as expected. *But 2nd import failed* In other fetch Types this will work. So we also require similar behaviour in case of Incremental type also because this is very normal scenario and customer will hit this very frequently. > Atlas Import is failing with fetchType: Incremental if there are no changes > between two consecutive runs > > > Key: ATLAS-4845 > URL: https://issues.apache.org/jira/browse/ATLAS-4845 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: ATLAS-4845.patch > > > Repro steps: > # First export + import with changeMarker “0” - worked as expected. > # I tried to run 2nd export + import without any changes in atlas, 2nd > export also worked and gave different changeMarker in output as expected. > *But 2nd import failed* > In other fetch Types this will work. So we also require similar behaviour in > case of Incremental type also because this is very normal scenario and > customer will hit this very frequently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4845) Atlas Import is failing with fetchType: Incremental if there are no changes between two consecutive runs
[ https://issues.apache.org/jira/browse/ATLAS-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4845: -- Attachment: ATLAS-4845.patch > Atlas Import is failing with fetchType: Incremental if there are no changes > between two consecutive runs > > > Key: ATLAS-4845 > URL: https://issues.apache.org/jira/browse/ATLAS-4845 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: ATLAS-4845.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4847) Export/Import : Atlas export fails and throws NullPointerException.
[ https://issues.apache.org/jira/browse/ATLAS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4847: -- Summary: Export/Import : Atlas export fails and throws NullPointerException. (was: Export/Import : Atlas export fails when glossary is assigned to exported entity with fetchtype : Incremental and changeMarker value greater than lastModified time of that entity.) > Export/Import : Atlas export fails and throws NullPointerException. > --- > > Key: ATLAS-4847 > URL: https://issues.apache.org/jira/browse/ATLAS-4847 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4847) Export/Import : Atlas export fails when glossary is assigned to exported entity with fetchtype : Incremental and changeMarker value greater than lastModified time of that
Priyanshi Shah created ATLAS-4847: - Summary: Export/Import : Atlas export fails when glossary is assigned to exported entity with fetchtype : Incremental and changeMarker value greater than lastModified time of that entity. Key: ATLAS-4847 URL: https://issues.apache.org/jira/browse/ATLAS-4847 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Priyanshi Shah Assignee: Priyanshi Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4845) Atlas Import is failing with fetchType: Incremental if there are no changes between two consecutive runs
[ https://issues.apache.org/jira/browse/ATLAS-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836008#comment-17836008 ] ASF subversion and git services commented on ATLAS-4845: Commit 5d549ce92619c923da1332917baf02c08a9bed90 in atlas's branch refs/heads/branch-2.0 from priyanshi-shah26 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5d549ce92 ] ATLAS-4845 : Atlas Import is failing with fetchType: Incremental if there are no changes between two consecutive runs Signed-off-by: Pinal Shah > Atlas Import is failing with fetchType: Incremental if there are no changes > between two consecutive runs > > > Key: ATLAS-4845 > URL: https://issues.apache.org/jira/browse/ATLAS-4845 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4845) Atlas Import is failing with fetchType: Incremental if there are no changes between two consecutive runs
[ https://issues.apache.org/jira/browse/ATLAS-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836007#comment-17836007 ] ASF subversion and git services commented on ATLAS-4845: Commit 386067ebfe50b4bf8912e700933d59be44b05e39 in atlas's branch refs/heads/master from priyanshi-shah26 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=386067ebf ] ATLAS-4845 : Atlas Import is failing with fetchType: Incremental if there are no changes between two consecutive runs Signed-off-by: Pinal Shah > Atlas Import is failing with fetchType: Incremental if there are no changes > between two consecutive runs > > > Key: ATLAS-4845 > URL: https://issues.apache.org/jira/browse/ATLAS-4845 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4764) CuratorFrameWork should work only with Zookeeper HA mode
[ https://issues.apache.org/jira/browse/ATLAS-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835598#comment-17835598 ] Paresh Devalia commented on ATLAS-4764: --- Hi Team, Code review:- https://reviews.apache.org/r/74738/diff/5#index_header > CuratorFrameWork should work only with Zookeeper HA mode > > > Key: ATLAS-4764 > URL: https://issues.apache.org/jira/browse/ATLAS-4764 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > Zookeeper Non-HA mode should not run through CuratorFramework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4846) Source the atlas-env file in ATLAS import script to get all the argument
[ https://issues.apache.org/jira/browse/ATLAS-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835597#comment-17835597 ] Paresh Devalia commented on ATLAS-4846: --- Hi Team, Code review:-[https://reviews.apache.org/r/74954/] > Source the atlas-env file in ATLAS import script to get all the argument > > > Key: ATLAS-4846 > URL: https://issues.apache.org/jira/browse/ATLAS-4846 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > User has to run manually export command to get all the argument which are > set, to run the Atlas import script. > The problem is not with the Atlas service itself but with these scripts: > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-kafka.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hbase.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh > > Need to set argument before this script are being called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4845) Atlas Import is failing with fetchType: Incremental if there are no changes between two consecutive runs
[ https://issues.apache.org/jira/browse/ATLAS-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4845: -- Attachment: (was: ATLAS-4845.patch) > Atlas Import is failing with fetchType: Incremental if there are no changes > between two consecutive runs > > > Key: ATLAS-4845 > URL: https://issues.apache.org/jira/browse/ATLAS-4845 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Priyanshi Shah >Assignee: Priyanshi Shah >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4842) Export/Import: fetchType as "incremental" does full export instead of connected
[ https://issues.apache.org/jira/browse/ATLAS-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanshi Shah updated ATLAS-4842: -- Attachment: ATLAS-4842.patch > Export/Import: fetchType as "incremental" does full export instead of > connected > --- > > Key: ATLAS-4842 > URL: https://issues.apache.org/jira/browse/ATLAS-4842 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sheetal Shah >Assignee: Priyanshi Shah >Priority: Major > Attachments: ATLAS-4842.patch > > > Create two hive_tables in same database: > # create table hive1(id int); > # create table hive1_ctas as select * from hive1; > # create table hive2(name string); > Perform incremental export of hive1 with changeMarker as 0 and skipLineage > value as false. > Import the zip. > Expectation is only the requested hive_table hive1 and its related entities > should be exported, but it does full export and hive2 is also imported. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4842) Export/Import: fetchType as "incremental" does full export instead of connected
[ https://issues.apache.org/jira/browse/ATLAS-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834204#comment-17834204 ] ASF subversion and git services commented on ATLAS-4842: Commit 3aebe0cb1e1937a58f144b16b6616fe24e55f7eb in atlas's branch refs/heads/branch-2.0 from priyanshi-shah26 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3aebe0cb1 ] ATLAS-4842 : Export/Import: fetchType as incremental does full export instead of connected Signed-off-by: Pinal Shah > Export/Import: fetchType as "incremental" does full export instead of > connected > --- > > Key: ATLAS-4842 > URL: https://issues.apache.org/jira/browse/ATLAS-4842 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sheetal Shah >Assignee: Priyanshi Shah >Priority: Major > > Create two hive_tables in same database: > # create table hive1(id int); > # create table hive1_ctas as select * from hive1; > # create table hive2(name string); > Perform incremental export of hive1 with changeMarker as 0 and skipLineage > value as false. > Import the zip. > Expectation is only the requested hive_table hive1 and its related entities > should be exported, but it does full export and hive2 is also imported. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4842) Export/Import: fetchType as "incremental" does full export instead of connected
[ https://issues.apache.org/jira/browse/ATLAS-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834203#comment-17834203 ] ASF subversion and git services commented on ATLAS-4842: Commit 51691b139b8c2e22878a9bc9f3427e7215a694d6 in atlas's branch refs/heads/master from priyanshi-shah26 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=51691b139 ] ATLAS-4842 : Export/Import: fetchType as incremental does full export instead of connected Signed-off-by: Pinal Shah > Export/Import: fetchType as "incremental" does full export instead of > connected > --- > > Key: ATLAS-4842 > URL: https://issues.apache.org/jira/browse/ATLAS-4842 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sheetal Shah >Assignee: Priyanshi Shah >Priority: Major > > Create two hive_tables in same database: > # create table hive1(id int); > # create table hive1_ctas as select * from hive1; > # create table hive2(name string); > Perform incremental export of hive1 with changeMarker as 0 and skipLineage > value as false. > Import the zip. > Expectation is only the requested hive_table hive1 and its related entities > should be exported, but it does full export and hive2 is also imported. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-3891) UI: Quick search cards for ease of search and utilization of white space
[ https://issues.apache.org/jira/browse/ATLAS-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reassigned ATLAS-3891: -- Assignee: Brijesh Bhalala (was: Prasad P. Pawar) > UI: Quick search cards for ease of search and utilization of white space > > > Key: ATLAS-3891 > URL: https://issues.apache.org/jira/browse/ATLAS-3891 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Keval Bhatt >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: search_dashboard_roun...@2x.png > > > Example: > > !search_dashboard_roun...@2x.png|width=591,height=332! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4817) Change compression from 'GZ' to 'SNAPPY' in Atlas HBase tables
[ https://issues.apache.org/jira/browse/ATLAS-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833819#comment-17833819 ] ASF subversion and git services commented on ATLAS-4817: Commit 80d2ffe1fb501a6ac5585909b872b9d137494883 in atlas's branch refs/heads/branch-2.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=80d2ffe1f ] ATLAS-4817 : Change compression from 'GZ' to 'SNAPPY' in Atlas HBase tables Signed-off-by: Pinal Shah > Change compression from 'GZ' to 'SNAPPY' in Atlas HBase tables > -- > > Key: ATLAS-4817 > URL: https://issues.apache.org/jira/browse/ATLAS-4817 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4817) Change compression from 'GZ' to 'SNAPPY' in Atlas HBase tables
[ https://issues.apache.org/jira/browse/ATLAS-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833818#comment-17833818 ] ASF subversion and git services commented on ATLAS-4817: Commit ab89e78ed5737acbee409203d20c75bc10429b9d in atlas's branch refs/heads/master from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ab89e78ed ] ATLAS-4817 : Change compression from 'GZ' to 'SNAPPY' in Atlas HBase tables Signed-off-by: Pinal Shah > Change compression from 'GZ' to 'SNAPPY' in Atlas HBase tables > -- > > Key: ATLAS-4817 > URL: https://issues.apache.org/jira/browse/ATLAS-4817 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4846) Source the atlas-env file in ATLAS import script to get all the argument
Paresh Devalia created ATLAS-4846: - Summary: Source the atlas-env file in ATLAS import script to get all the argument Key: ATLAS-4846 URL: https://issues.apache.org/jira/browse/ATLAS-4846 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Paresh Devalia Assignee: Paresh Devalia User has to run manually export command to get all the argument which are set, to run the Atlas import script. The problem is not with the Atlas service itself but with these scripts: * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-kafka.sh * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hbase.sh * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh Need to set argument before this script are being called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4827) Clean Atlas application log
[ https://issues.apache.org/jira/browse/ATLAS-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833396#comment-17833396 ] ASF subversion and git services commented on ATLAS-4827: Commit b10cfcec5716bbc1bfb3b6f5824e96e58a9f4da0 in atlas's branch refs/heads/branch-2.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b10cfcec5 ] ATLAS-4827 : Clean Atlas application log Signed-off-by: Pinal Shah > Clean Atlas application log > --- > > Key: ATLAS-4827 > URL: https://issues.apache.org/jira/browse/ATLAS-4827 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Cleaning unwanted error logs from Atlas application log -- This message was sent by Atlassian Jira (v8.20.10#820010)
