[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] [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] [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] [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-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] [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] [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)
[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=17833395#comment-17833395 ] ASF subversion and git services commented on ATLAS-4827: Commit cd3ab82627761ee9ea8b44a8c7769de9bb54db11 in atlas's branch refs/heads/master from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=cd3ab8262 ] 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)
[jira] [Commented] (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:comment-tabpanel=17832773#comment-17832773
]
ASF subversion and git services commented on ATLAS-4838:
Commit 89fdbe333aba5bb771142206de76221cc362f8f0 in atlas's branch
refs/heads/branch-2.0 from priyanshi-freestoneinfotech
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=89fdbe333 ]
ATLAS-4838 : Export/Import : changeMarker is not set to entity's lastupdatetime
or its closer timestamp value
Signed-off-by: Pinal Shah
> 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
> Attachments: ATLAS-4838-V2.patch, ATLAS-4838.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] [Commented] (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:comment-tabpanel=17832770#comment-17832770
]
ASF subversion and git services commented on ATLAS-4838:
Commit f4f9d623301d49426470ff38d6a4a60ce5fc014d in atlas's branch
refs/heads/master from priyanshi-freestoneinfotech
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f4f9d6233 ]
ATLAS-4838 : Export/Import : changeMarker is not set to entity's lastupdatetime
or its closer timestamp value
Signed-off-by: Pinal Shah
> 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
> Attachments: ATLAS-4838-V2.patch, ATLAS-4838.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] [Commented] (ATLAS-4822) Relationship Search feature should be configurable
[ https://issues.apache.org/jira/browse/ATLAS-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827383#comment-17827383 ] ASF subversion and git services commented on ATLAS-4822: Commit 9a5ad2d4736577eaabe73887afc65f7b15634907 in atlas's branch refs/heads/branch-2.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9a5ad2d47 ] ATLAS-4822: Relationship Search feature should be configurable Signed-off-by: Pinal Shah > Relationship Search feature should be configurable > -- > > Key: ATLAS-4822 > URL: https://issues.apache.org/jira/browse/ATLAS-4822 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 3.0.0, 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > Attachments: > 0001-ATLAS-4822-ATLAS-UI-Relationship-Search-feature-shou.patch, > 0002-ATLAS-4822-ATLAS-UI-Relationship-Search-feature-shou.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4822) Relationship Search feature should be configurable
[ https://issues.apache.org/jira/browse/ATLAS-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827382#comment-17827382 ] ASF subversion and git services commented on ATLAS-4822: Commit b4745dcfe1799d9eddf43f62cffa162d19ad0c92 in atlas's branch refs/heads/master from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b4745dcfe ] ATLAS-4822: Relationship Search feature should be configurable Signed-off-by: Pinal Shah > Relationship Search feature should be configurable > -- > > Key: ATLAS-4822 > URL: https://issues.apache.org/jira/browse/ATLAS-4822 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 3.0.0, 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > Attachments: > 0001-ATLAS-4822-ATLAS-UI-Relationship-Search-feature-shou.patch, > 0002-ATLAS-4822-ATLAS-UI-Relationship-Search-feature-shou.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4826) Provide Liveness and Readyness probes in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826944#comment-17826944 ] ASF subversion and git services commented on ATLAS-4826: Commit 8ae65cd179cace305f22520fe4349cf2bb4e618c in atlas's branch refs/heads/branch-2.0 from Disha Talreja [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8ae65cd17 ] ATLAS-4826: Provide Liveness and Readyness probes in Atlas Signed-off-by: Pinal Shah > Provide Liveness and Readyness probes in Atlas > -- > > Key: ATLAS-4826 > URL: https://issues.apache.org/jira/browse/ATLAS-4826 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Disha Talreja >Assignee: Disha Talreja >Priority: Major > Attachments: ATLAS-4826.patch > > > In order to monitor the application health and be able to restart it if it is > unhealthy we need to check the: > 1) Liveness - if Atlas is live and running as expected > 2) Readyness - if Atlas is live and ready to accept client requests -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4826) Provide Liveness and Readyness probes in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826943#comment-17826943 ] ASF subversion and git services commented on ATLAS-4826: Commit a7d7398679691694a4fb63480f3d41bac071f965 in atlas's branch refs/heads/master from Disha Talreja [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a7d739867 ] ATLAS-4826: Provide Liveness and Readyness probes in Atlas Signed-off-by: Pinal Shah > Provide Liveness and Readyness probes in Atlas > -- > > Key: ATLAS-4826 > URL: https://issues.apache.org/jira/browse/ATLAS-4826 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Disha Talreja >Assignee: Disha Talreja >Priority: Major > Attachments: ATLAS-4826.patch > > > In order to monitor the application health and be able to restart it if it is > unhealthy we need to check the: > 1) Liveness - if Atlas is live and running as expected > 2) Readyness - if Atlas is live and ready to accept client requests -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4802) Atlas 'updateTime' parameter is not updated when business metadata, labels is edited.
[
https://issues.apache.org/jira/browse/ATLAS-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825290#comment-17825290
]
ASF subversion and git services commented on ATLAS-4802:
Commit 89c3117fc865440e8718e105f89ecd26078ab8a4 in atlas's branch
refs/heads/branch-2.0 from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=89c3117fc ]
ATLAS-4802 : Atlas 'updateTime' parameter is not updated when business
metadata, labels is edited.
Signed-off-by: Pinal Shah
> Atlas 'updateTime' parameter is not updated when business metadata, labels is
> edited.
> -
>
> Key: ATLAS-4802
> URL: https://issues.apache.org/jira/browse/ATLAS-4802
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> When updating the business metadata on an atlas entity, the 'updateTime'
> system attribute is not changed.
> Updates to other aspects, such as technical properties and user defined
> attributes does update the timestamp, but not the business metadata.
> This appears to be a issue with the core Atlas product.
> curl -u admin:hadoop12345! -X GET --header 'Content-Type:
> application/json;charset=UTF-8'
> "http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
> {"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
>
> deserializer","position":3,"type":"string","table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table"}},"guid":"5b4e426e-404f-4a10-abab-f0b3879c0acb","isIncomplete":false,"status":"ACTIVE","createdBy":"hive","updatedBy":"hive","createTime":1697203083822,"updateTime":1697203083822,"version":0,"relationshipAttributes":{"inputToProcesses":[],"pipeline":null,"schema":[],"model":null,"meanings":[],"table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table","entityStatus":"ACTIVE","displayText":"mv_creation_metadata","relationshipType":"hive_table_columns","relationshipGuid":"39f22e08-8ff2-4bd3-9a2f-9e2efce69fba","relationshipStatus":"ACTIVE","relationshipAttributes":{"typeName":"hive_table_columns"}},"outputFromProcesses":[]},"labels":[]}}
>
> After adding business metadata "text : value1" to the entity txn_list
> (hive_column),
>
> curl -u admin:hadoop12345! -X GET --header 'Content-Type:
> application/json;charset=UTF-8'
> "http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
> {"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
>
> deserializer","position":3,"type":"string","table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table"}},"guid":"5b4e426e-404f-4a10-abab-f0b3879c0acb","isIncomplete":false,"status":"ACTIVE","createdBy":"hive","updatedBy":"hive","createTime":1697203083822,"updateTime":1697203083822,"version":0,"relationshipAttributes":{"inputToProcesses":[],"pipeline":null,"schema":[],"model":null,"meanings":[],"table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table","entityStatus":"ACTIVE","displayText":"mv_creation_metadata","relationshipType":"hive_table_columns","relationshipGuid":"39f22e08-8ff2-4bd3-9a2f-9e2efce69fba","relationshipStatus":"ACTIVE","relationshipAttributes":{"typeName":"hive_table_columns"}},"outputFromProcesses":[]},"businessAttributes":{"demo":{"text":"value1"}},"labels":[]}}
>
> As seen "updateTime":1697203083822 still remains the same.
> However, if we add an user-defined property "age : 20",
>
> curl -u admin:hadoop12345! -X GET --header 'Content-Type:
> application/json;charset=UTF-8'
> "http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
> {"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
>
>
[jira] [Commented] (ATLAS-4802) Atlas 'updateTime' parameter is not updated when business metadata, labels is edited.
[
https://issues.apache.org/jira/browse/ATLAS-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825287#comment-17825287
]
ASF subversion and git services commented on ATLAS-4802:
Commit 88869d3c9c079fbe2118f5efd53a6a40c862f3e0 in atlas's branch
refs/heads/master from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=88869d3c9 ]
ATLAS-4802 : Atlas 'updateTime' parameter is not updated when business
metadata, labels is edited.
Signed-off-by: Pinal Shah
> Atlas 'updateTime' parameter is not updated when business metadata, labels is
> edited.
> -
>
> Key: ATLAS-4802
> URL: https://issues.apache.org/jira/browse/ATLAS-4802
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> When updating the business metadata on an atlas entity, the 'updateTime'
> system attribute is not changed.
> Updates to other aspects, such as technical properties and user defined
> attributes does update the timestamp, but not the business metadata.
> This appears to be a issue with the core Atlas product.
> curl -u admin:hadoop12345! -X GET --header 'Content-Type:
> application/json;charset=UTF-8'
> "http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
> {"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
>
> deserializer","position":3,"type":"string","table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table"}},"guid":"5b4e426e-404f-4a10-abab-f0b3879c0acb","isIncomplete":false,"status":"ACTIVE","createdBy":"hive","updatedBy":"hive","createTime":1697203083822,"updateTime":1697203083822,"version":0,"relationshipAttributes":{"inputToProcesses":[],"pipeline":null,"schema":[],"model":null,"meanings":[],"table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table","entityStatus":"ACTIVE","displayText":"mv_creation_metadata","relationshipType":"hive_table_columns","relationshipGuid":"39f22e08-8ff2-4bd3-9a2f-9e2efce69fba","relationshipStatus":"ACTIVE","relationshipAttributes":{"typeName":"hive_table_columns"}},"outputFromProcesses":[]},"labels":[]}}
>
> After adding business metadata "text : value1" to the entity txn_list
> (hive_column),
>
> curl -u admin:hadoop12345! -X GET --header 'Content-Type:
> application/json;charset=UTF-8'
> "http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
> {"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
>
> deserializer","position":3,"type":"string","table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table"}},"guid":"5b4e426e-404f-4a10-abab-f0b3879c0acb","isIncomplete":false,"status":"ACTIVE","createdBy":"hive","updatedBy":"hive","createTime":1697203083822,"updateTime":1697203083822,"version":0,"relationshipAttributes":{"inputToProcesses":[],"pipeline":null,"schema":[],"model":null,"meanings":[],"table":{"guid":"bb0b34ae-4de7-4d9b-b072-e1b3c47fe14a","typeName":"hive_table","entityStatus":"ACTIVE","displayText":"mv_creation_metadata","relationshipType":"hive_table_columns","relationshipGuid":"39f22e08-8ff2-4bd3-9a2f-9e2efce69fba","relationshipStatus":"ACTIVE","relationshipAttributes":{"typeName":"hive_table_columns"}},"outputFromProcesses":[]},"businessAttributes":{"demo":{"text":"value1"}},"labels":[]}}
>
> As seen "updateTime":1697203083822 still remains the same.
> However, if we add an user-defined property "age : 20",
>
> curl -u admin:hadoop12345! -X GET --header 'Content-Type:
> application/json;charset=UTF-8'
> "http://localhost:21000/api/atlas/v2/entity/guid/5b4e426e-404f-4a10-abab-f0b3879c0acb;
> {"referredEntities":{},"entity":{"typeName":"hive_column","attributes":{"owner":"hive","replicatedTo":null,"userDescription":null,"replicatedFrom":null,"qualifiedName":"sys.mv_creation_metadata.txn_list@cm","displayName":null,"name":"txn_list","description":null,"comment":"from
>
>
[jira] [Commented] (ATLAS-4824) UI: Enable/Disable Propagation window usability needs improvement
[ https://issues.apache.org/jira/browse/ATLAS-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824027#comment-17824027 ] ASF subversion and git services commented on ATLAS-4824: Commit 1e64023e40d47c97a40c485640519a29eae58d07 in atlas's branch refs/heads/branch-2.0 from Brijesh Bhalala [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1e64023e4 ] ATLAS-4824: UI: Enable/Disable Propagation window usability needs improvement Signed-off-by: Prasad Pawar > UI: Enable/Disable Propagation window usability needs improvement > -- > > Key: ATLAS-4824 > URL: https://issues.apache.org/jira/browse/ATLAS-4824 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Brijesh Bhalala >Priority: Minor > Fix For: 3.0.0 > > Attachments: 0001-ATLAS-4824.patch, 0002-ATLAS-4824.patch, > blocking_propagation2.png, image-2024-02-15-10-37-14-512.png > > > In Atlas UI, the user has the ability to access a window that enables or > disables propagation of a classification in a lineage. It looks like the > attached screenshot. > !image-2024-02-15-10-37-14-512.png! > The UI in the window could use improvement as it uses outdated UI. > Edit: The alignment is improper in the "Selection Classification" pane as > seen in this screenshot below. Also as a suggestion, keep the title of the > modal box consistent. > !blocking_propagation2.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4824) UI: Enable/Disable Propagation window usability needs improvement
[ https://issues.apache.org/jira/browse/ATLAS-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824025#comment-17824025 ] ASF subversion and git services commented on ATLAS-4824: Commit 73467212ff15e0e82006d8faa9b3601709d1d2b3 in atlas's branch refs/heads/master from Brijesh Bhalala [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=73467212f ] ATLAS-4824: UI: Enable/Disable Propagation window usability needs improvement Signed-off-by: Prasad Pawar > UI: Enable/Disable Propagation window usability needs improvement > -- > > Key: ATLAS-4824 > URL: https://issues.apache.org/jira/browse/ATLAS-4824 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Brijesh Bhalala >Priority: Minor > Fix For: 3.0.0 > > Attachments: 0001-ATLAS-4824.patch, 0002-ATLAS-4824.patch, > blocking_propagation2.png, image-2024-02-15-10-37-14-512.png > > > In Atlas UI, the user has the ability to access a window that enables or > disables propagation of a classification in a lineage. It looks like the > attached screenshot. > !image-2024-02-15-10-37-14-512.png! > The UI in the window could use improvement as it uses outdated UI. > Edit: The alignment is improper in the "Selection Classification" pane as > seen in this screenshot below. Also as a suggestion, keep the title of the > modal box consistent. > !blocking_propagation2.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4806) Upgrade netty to 4.1.100.Final due to CVE-2023-44487
[ https://issues.apache.org/jira/browse/ATLAS-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815783#comment-17815783 ] ASF subversion and git services commented on ATLAS-4806: Commit 04645652d7918ad96911fde06a06b6a142befa64 in atlas's branch refs/heads/branch-2.0 from Disha Talreja [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=04645652d ] ATLAS-4806: Upgrade netty to 4.1.100.Final due to CVE-2023-44487 Signed-off-by: radhikakundam (cherry picked from commit f9df3293d74e10894ab4730ad2b8ccc593d8bc04) > Upgrade netty to 4.1.100.Final due to CVE-2023-44487 > > > Key: ATLAS-4806 > URL: https://issues.apache.org/jira/browse/ATLAS-4806 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Disha Talreja >Assignee: Disha Talreja >Priority: Major > Attachments: ATLAS-4806.patch > > > CVE-2023-44487 > The HTTP/2 protocol allows a denial of service (server resource consumption) > because request cancellation can reset many streams quickly, as exploited in > the wild in August through October 2023. > *Base Score:* [7.5 > HIGH|https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?name=CVE-2023-44487=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H=3.1=NIST] > There is a known exploit for this vulnerability, so we need to prioritise > this despite it being a High severity CVE and not a critical. > [https://github.com/netty/netty/security/advisories/GHSA-xpw8-rcwv-8f8p] > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4806) Upgrade netty to 4.1.100.Final due to CVE-2023-44487
[ https://issues.apache.org/jira/browse/ATLAS-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815782#comment-17815782 ] ASF subversion and git services commented on ATLAS-4806: Commit f9df3293d74e10894ab4730ad2b8ccc593d8bc04 in atlas's branch refs/heads/master from Disha Talreja [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f9df3293d ] ATLAS-4806: Upgrade netty to 4.1.100.Final due to CVE-2023-44487 Signed-off-by: radhikakundam > Upgrade netty to 4.1.100.Final due to CVE-2023-44487 > > > Key: ATLAS-4806 > URL: https://issues.apache.org/jira/browse/ATLAS-4806 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Disha Talreja >Assignee: Disha Talreja >Priority: Major > Attachments: ATLAS-4806.patch > > > CVE-2023-44487 > The HTTP/2 protocol allows a denial of service (server resource consumption) > because request cancellation can reset many streams quickly, as exploited in > the wild in August through October 2023. > *Base Score:* [7.5 > HIGH|https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?name=CVE-2023-44487=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H=3.1=NIST] > There is a known exploit for this vulnerability, so we need to prioritise > this despite it being a High severity CVE and not a critical. > [https://github.com/netty/netty/security/advisories/GHSA-xpw8-rcwv-8f8p] > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4765) Atlas - Upgrade Spring Security to 5.8.5
[ https://issues.apache.org/jira/browse/ATLAS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17802895#comment-17802895 ] ASF subversion and git services commented on ATLAS-4765: Commit 3f6a1ce65edd1c919e22e5764eddfbf9346c6086 in atlas's branch refs/heads/branch-2.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3f6a1ce65 ] ATLAS-4765 : Upgrade Spring Security to 5.8.5 Signed-off-by: Pinal Shah > Atlas - Upgrade Spring Security to 5.8.5 > > > Key: ATLAS-4765 > URL: https://issues.apache.org/jira/browse/ATLAS-4765 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > Fix For: 3.0.0 > > > Currently atlas is using spring security version 5.7.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4765) Atlas - Upgrade Spring Security to 5.8.5
[ https://issues.apache.org/jira/browse/ATLAS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17802893#comment-17802893 ] ASF subversion and git services commented on ATLAS-4765: Commit d8cf1e34a696da6100127c38cf42b922e177a314 in atlas's branch refs/heads/master from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d8cf1e34a ] ATLAS-4765 : Upgrade Spring Security to 5.8.5 Signed-off-by: Pinal Shah > Atlas - Upgrade Spring Security to 5.8.5 > > > Key: ATLAS-4765 > URL: https://issues.apache.org/jira/browse/ATLAS-4765 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > Fix For: 3.0.0 > > > Currently atlas is using spring security version 5.7.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4754) Download Search with Basic Search gives java.io.FileNotFoundException
[
https://issues.apache.org/jira/browse/ATLAS-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801685#comment-17801685
]
ASF subversion and git services commented on ATLAS-4754:
Commit 5526b86aded88b5e89884e13a9ef0cac2a10 in atlas's branch
refs/heads/branch-2.0 from Mandar Ambawane
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5526b86ad ]
ATLAS-4754 : Download Search with Basic Search gives
java.io.FileNotFoundException
Signed-off-by: Mandar Ambawane
(cherry picked from commit 531fea4d76717093c8d1ff22f65d7bd3606ba51b)
> Download Search with Basic Search gives java.io.FileNotFoundException
> -
>
> Key: ATLAS-4754
> URL: https://issues.apache.org/jira/browse/ATLAS-4754
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Abhishek Pal
>Assignee: Mandar Ambawane
>Priority: Major
>
> Currently when trying to download search results, the download task is stuck
> on pending.
> Upon checking the logs the following error is being seen:
> {code:java|title=application.log}
> 2023-05-17 22:09:47,321 INFO - [etp1158258131-199 -
> a6302f98-7e3d-4cbc-bd06-883fbfa21d11:] ~ TaskManagement: Processing stats:
> total=1, sinceLastStatsReport=2 completedWithErrors=1, succeded=0
> (TaskExecutor$TaskLogger:166)
> 2023-05-17 22:09:47,330 ERROR - [atlas-task-0-etp1158258131-282 -
> b9a5a4ef-6e3f-440c-9f65-d446a6da9720:] ~ Task:
> f4e26459-746f-4f31-90db-144c31a9696f: Error performing task!
> (SearchResultDownloadTask:126)
> java.io.FileNotFoundException:
> /search_result_downloads//.csv (No such file
> or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:237)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:187)
> at java.base/java.io.FileWriter.(FileWriter.java:96)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.generateCSVFileFromSearchResult(SearchResultDownloadTask.java:185)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.run(SearchResultDownloadTask.java:163)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.perform(SearchResultDownloadTask.java:122)
> at org.apache.atlas.tasks.AbstractTask.run(AbstractTask.java:33)
> at
> org.apache.atlas.tasks.TaskExecutor$TaskConsumer.performTask(TaskExecutor.java:150)
> at org.apache.atlas.tasks.TaskExecutor$TaskConsumer.run(TaskExecutor.java:109)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834){code}
> h2. Steps to Reproduce:
> h4. Create type: test_download_entity
> {code:java|title=/api/atlas/v2/types/typedefs}
> {
> "enumDefs": [],
> "structDefs": [],
> "classificationDefs": [],
> "entityDefs": [
> {
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name": "type_str",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> }
> ],
> "description": "description",
> "name": "test_download_entity",
> "guid": "-32062751815011",
> "category": "ENTITY",
> "superTypes": []
> }
> ],
> "relationshipDefs": [],
> "businessMetadataDefs": []
> }
> {code}
> h4. Create entity of type: test_download_entity
> {code:java|title=/api/atlas/v2/entity/bulk}
> {
> "entities": [{
> "typeName": "test_download_entity",
> "attributes": {
> "name": "downloadable_entity_1",
> "type_str": "str1"
> },
> "guid":
[jira] [Commented] (ATLAS-4754) Download Search with Basic Search gives java.io.FileNotFoundException
[
https://issues.apache.org/jira/browse/ATLAS-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801682#comment-17801682
]
ASF subversion and git services commented on ATLAS-4754:
Commit 531fea4d76717093c8d1ff22f65d7bd3606ba51b in atlas's branch
refs/heads/master from Mandar Ambawane
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=531fea4d7 ]
ATLAS-4754 : Download Search with Basic Search gives
java.io.FileNotFoundException
Signed-off-by: Mandar Ambawane
> Download Search with Basic Search gives java.io.FileNotFoundException
> -
>
> Key: ATLAS-4754
> URL: https://issues.apache.org/jira/browse/ATLAS-4754
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Abhishek Pal
>Assignee: Mandar Ambawane
>Priority: Major
>
> Currently when trying to download search results, the download task is stuck
> on pending.
> Upon checking the logs the following error is being seen:
> {code:java|title=application.log}
> 2023-05-17 22:09:47,321 INFO - [etp1158258131-199 -
> a6302f98-7e3d-4cbc-bd06-883fbfa21d11:] ~ TaskManagement: Processing stats:
> total=1, sinceLastStatsReport=2 completedWithErrors=1, succeded=0
> (TaskExecutor$TaskLogger:166)
> 2023-05-17 22:09:47,330 ERROR - [atlas-task-0-etp1158258131-282 -
> b9a5a4ef-6e3f-440c-9f65-d446a6da9720:] ~ Task:
> f4e26459-746f-4f31-90db-144c31a9696f: Error performing task!
> (SearchResultDownloadTask:126)
> java.io.FileNotFoundException:
> /search_result_downloads//.csv (No such file
> or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:237)
> at java.base/java.io.FileOutputStream.(FileOutputStream.java:187)
> at java.base/java.io.FileWriter.(FileWriter.java:96)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.generateCSVFileFromSearchResult(SearchResultDownloadTask.java:185)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.run(SearchResultDownloadTask.java:163)
> at
> org.apache.atlas.repository.store.graph.v2.tasks.searchdownload.SearchResultDownloadTask.perform(SearchResultDownloadTask.java:122)
> at org.apache.atlas.tasks.AbstractTask.run(AbstractTask.java:33)
> at
> org.apache.atlas.tasks.TaskExecutor$TaskConsumer.performTask(TaskExecutor.java:150)
> at org.apache.atlas.tasks.TaskExecutor$TaskConsumer.run(TaskExecutor.java:109)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834){code}
> h2. Steps to Reproduce:
> h4. Create type: test_download_entity
> {code:java|title=/api/atlas/v2/types/typedefs}
> {
> "enumDefs": [],
> "structDefs": [],
> "classificationDefs": [],
> "entityDefs": [
> {
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name": "type_str",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> }
> ],
> "description": "description",
> "name": "test_download_entity",
> "guid": "-32062751815011",
> "category": "ENTITY",
> "superTypes": []
> }
> ],
> "relationshipDefs": [],
> "businessMetadataDefs": []
> }
> {code}
> h4. Create entity of type: test_download_entity
> {code:java|title=/api/atlas/v2/entity/bulk}
> {
> "entities": [{
> "typeName": "test_download_entity",
> "attributes": {
> "name": "downloadable_entity_1",
> "type_str": "str1"
> },
> "guid": "-08727943682221"
> },
> {
>
[jira] [Commented] (ATLAS-4820) Atlas UI: Change the alignment of the Download Search button on the Classic UI search page.
[ https://issues.apache.org/jira/browse/ATLAS-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796731#comment-17796731 ] ASF subversion and git services commented on ATLAS-4820: Commit c29e92a0c262e830955bbce47c4b1e0719045f59 in atlas's branch refs/heads/branch-2.0 from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c29e92a0c ] ATLAS-4820: Atlas UI: Change the alignment of the Download Search button on the Classic UI search page. Signed-off-by: Prasad Pawar > Atlas UI: Change the alignment of the Download Search button on the Classic > UI search page. > --- > > Key: ATLAS-4820 > URL: https://issues.apache.org/jira/browse/ATLAS-4820 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4820) Atlas UI: Change the alignment of the Download Search button on the Classic UI search page.
[ https://issues.apache.org/jira/browse/ATLAS-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796730#comment-17796730 ] ASF subversion and git services commented on ATLAS-4820: Commit 685845db8a347d0dd015da4e70a61e9994e129b7 in atlas's branch refs/heads/master from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=685845db8 ] ATLAS-4820: Atlas UI: Change the alignment of the Download Search button on the Classic UI search page. Signed-off-by: Prasad Pawar > Atlas UI: Change the alignment of the Download Search button on the Classic > UI search page. > --- > > Key: ATLAS-4820 > URL: https://issues.apache.org/jira/browse/ATLAS-4820 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4815) Python client: incorrect method name in EntityClient.remove_classification()
[ https://issues.apache.org/jira/browse/ATLAS-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796371#comment-17796371 ] ASF subversion and git services commented on ATLAS-4815: Commit 2c920afb5f4bc221e78399b1e8a163e3591864b1 in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2c920afb5 ] ATLAS-4815: publish Python client library with the fix from previous commit (cherry picked from commit e86406906ebdf21056952f238478d2b5a9d48441) > Python client: incorrect method name in EntityClient.remove_classification() > > > Key: ATLAS-4815 > URL: https://issues.apache.org/jira/browse/ATLAS-4815 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 2.4.0 > > > This Jira tracks pull request #232 https://github.com/apache/atlas/pull/232/. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4815) Python client: incorrect method name in EntityClient.remove_classification()
[ https://issues.apache.org/jira/browse/ATLAS-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796370#comment-17796370 ] ASF subversion and git services commented on ATLAS-4815: Commit e86406906ebdf21056952f238478d2b5a9d48441 in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e86406906 ] ATLAS-4815: publish Python client library with the fix from previous commit > Python client: incorrect method name in EntityClient.remove_classification() > > > Key: ATLAS-4815 > URL: https://issues.apache.org/jira/browse/ATLAS-4815 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 2.4.0 > > > This Jira tracks pull request #232 https://github.com/apache/atlas/pull/232/. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4768) Implement aging for audits stored by Atlas.
[ https://issues.apache.org/jira/browse/ATLAS-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793904#comment-17793904 ] ASF subversion and git services commented on ATLAS-4768: Commit f944f813a04ae91aba94f3622e1213da34dab30a in atlas's branch refs/heads/branch-2.0 from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f944f813a ] ATLAS-4768: Implement aging for audits stored by Atlas. Signed-off-by: radhikakundam (cherry picked from commit 79ef3cce1be4874c17b296aff8b200c9edb42bcb) > Implement aging for audits stored by Atlas. > --- > > Key: ATLAS-4768 > URL: https://issues.apache.org/jira/browse/ATLAS-4768 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > Attachments: Atlas Audit Reduction - Audit Aging - Apache.pdf > > > Currently, there is no aging of the audits stored in Atlas. > Scope of this Jira to implement below. > # Implement logic to age out and delete the audits stored in HBase. > ## It could be as simple as leveraging TTL capability of Hbase or a customer > implementation in Atlas. > # There should be a configuration that controls the duration for which Atlas > holds the audits for. > ## We should be have a default value which could be few months. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4768) Implement aging for audits stored by Atlas.
[ https://issues.apache.org/jira/browse/ATLAS-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793901#comment-17793901 ] ASF subversion and git services commented on ATLAS-4768: Commit 79ef3cce1be4874c17b296aff8b200c9edb42bcb in atlas's branch refs/heads/master from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=79ef3cce1 ] ATLAS-4768: Implement aging for audits stored by Atlas. Signed-off-by: radhikakundam > Implement aging for audits stored by Atlas. > --- > > Key: ATLAS-4768 > URL: https://issues.apache.org/jira/browse/ATLAS-4768 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > Attachments: Atlas Audit Reduction - Audit Aging - Apache.pdf > > > Currently, there is no aging of the audits stored in Atlas. > Scope of this Jira to implement below. > # Implement logic to age out and delete the audits stored in HBase. > ## It could be as simple as leveraging TTL capability of Hbase or a customer > implementation in Atlas. > # There should be a configuration that controls the duration for which Atlas > holds the audits for. > ## We should be have a default value which could be few months. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4815) Python client: incorrect method name in EntityClient.remove_classification()
[ https://issues.apache.org/jira/browse/ATLAS-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791432#comment-17791432 ] ASF subversion and git services commented on ATLAS-4815: Commit 5f38e925590d6ea4b8a9438fef44302d9284c16f in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5f38e9255 ] Merge pull request #232 from itsjoaoduque/patch-1 ATLAS-4815: fixed incorrect method name in EntityClient.remove_classification() > Python client: incorrect method name in EntityClient.remove_classification() > > > Key: ATLAS-4815 > URL: https://issues.apache.org/jira/browse/ATLAS-4815 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Madhan Neethiraj >Priority: Major > > This Jira tracks pull request #232 https://github.com/apache/atlas/pull/232/. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4803) Optimize Edge fetch
[ https://issues.apache.org/jira/browse/ATLAS-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790415#comment-17790415 ] ASF subversion and git services commented on ATLAS-4803: Commit 144ca0a51f7b01e50e026f8d28302016c2c5c8ad in atlas's branch refs/heads/branch-2.0 from pareshD [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=144ca0a51 ] ATLAS-4803: Optimize Relationship Edge fetch Signed-off-by: Pinal Shah > Optimize Edge fetch > --- > > Key: ATLAS-4803 > URL: https://issues.apache.org/jira/browse/ATLAS-4803 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > CU kafka lag was not decreasing for ATLAS_HOOK topics, create Entity API was > taking 50-60 sec per request. > Hive_table count was 10mn record. > Impala_lineage_column count was 26mn count. > Able to reproduce the issue on in-house cluster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4803) Optimize Edge fetch
[ https://issues.apache.org/jira/browse/ATLAS-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790412#comment-17790412 ] ASF subversion and git services commented on ATLAS-4803: Commit 12b81d79e7284c890a50a6043e6890a1acc9fba8 in atlas's branch refs/heads/master from pareshD [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=12b81d79e ] ATLAS-4803: Optimize Relationship Edge fetch Signed-off-by: Pinal Shah > Optimize Edge fetch > --- > > Key: ATLAS-4803 > URL: https://issues.apache.org/jira/browse/ATLAS-4803 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > CU kafka lag was not decreasing for ATLAS_HOOK topics, create Entity API was > taking 50-60 sec per request. > Hive_table count was 10mn record. > Impala_lineage_column count was 26mn count. > Able to reproduce the issue on in-house cluster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4809) Atlas - Exclude amqp-client jar from janusgraph-core
[ https://issues.apache.org/jira/browse/ATLAS-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789017#comment-17789017 ] ASF subversion and git services commented on ATLAS-4809: Commit 75053b58cc92b9e620bfb7d55e92a6830a916032 in atlas's branch refs/heads/branch-2.0 from sheetal.shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=75053b58c ] ATLAS-4809 : Exclude amqp-client from janusgraph-core Signed-off-by: Pinal Shah > Atlas - Exclude amqp-client jar from janusgraph-core > > > Key: ATLAS-4809 > URL: https://issues.apache.org/jira/browse/ATLAS-4809 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: Sheetal Shah >Assignee: Sheetal Shah >Priority: Major > > Exclude amqp-client jar from janusgraph-core > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4809) Atlas - Exclude amqp-client jar from janusgraph-core
[ https://issues.apache.org/jira/browse/ATLAS-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789015#comment-17789015 ] ASF subversion and git services commented on ATLAS-4809: Commit 8bc7a29055613c6586cb37bd587625f7edbe7e78 in atlas's branch refs/heads/master from sheetal.shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8bc7a2905 ] ATLAS-4809 : Exclude amqp-client from janusgraph-core Signed-off-by: Pinal Shah > Atlas - Exclude amqp-client jar from janusgraph-core > > > Key: ATLAS-4809 > URL: https://issues.apache.org/jira/browse/ATLAS-4809 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: Sheetal Shah >Assignee: Sheetal Shah >Priority: Major > > Exclude amqp-client jar from janusgraph-core > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4814) CI build fails in distro module with error: Cannot run program "python"
[
https://issues.apache.org/jira/browse/ATLAS-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788840#comment-17788840
]
ASF subversion and git services commented on ATLAS-4814:
Commit 204a39cb3aee39c71d2706db706d62241708652e in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=204a39cb3 ]
ATLAS-4814: updated build/python scripts to replace references to python with
python3
> CI build fails in distro module with error: Cannot run program "python"
> ---
>
> Key: ATLAS-4814
> URL: https://issues.apache.org/jira/browse/ATLAS-4814
> Project: Atlas
> Issue Type: Bug
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4184.patch
>
>
> Atlas CI build (Atlas-master-IntegrationTests) fails with the following
> error, which is likely due to the build machine not having python2 installed.
>
> {noformat}
> [INFO] Apache Atlas Couchbase Bridge .. SUCCESS [ 24.697
> s]
> [INFO] Apache Atlas Distribution .. FAILURE [ 9.103 s]
> [INFO] atlas-examples . SKIPPED
> [INFO] sample-app . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:56 h
> [INFO] Finished at: 2023-11-21T20:44:37Z
> [INFO]
>
> Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (python-test) on project
> atlas-distro: Command execution failed. Cannot run program "python" (in
> directory
> "/home/jenkins/jenkins-agent/workspace/Atlas/Atlas-master-IntegrationTests/distro/src/test/python"):
> error=2, No such file or directory -> [Help 1][ERROR] [ERROR] To see the
> full stack trace of the errors, re-run Maven with the -e switch.[ERROR]
> Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR]
> For more information about the errors and possible solutions, please read the
> following articles:[ERROR] [Help 1]
> [http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException][ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command[ERROR] mvn -rf :atlas-distrochannel stopped
> Exception: java.lang.LinkageError thrown from the UncaughtExceptionHandler in
> thread "Thread-942"
> Finished: FAILURE
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4184) [Atlas] Need a way to perform bulk delete typedef when knox proxy is enabled
[
https://issues.apache.org/jira/browse/ATLAS-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788839#comment-17788839
]
ASF subversion and git services commented on ATLAS-4184:
Commit 483ba3ea23c0b329a30b58460d4450f72f166e62 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=483ba3ea2 ]
Revert "ATLAS-4184: updated build/python scripts to replace references to
python with python3"
incorrect JIRA number in commit message
This reverts commit 0f331aa63095bae010f2c4cb0a76e58eb5606e1b.
> [Atlas] Need a way to perform bulk delete typedef when knox proxy is enabled
>
>
> Key: ATLAS-4184
> URL: https://issues.apache.org/jira/browse/ATLAS-4184
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
>
> While performing bulk delete operation on typedef, NullPointerException is
> thrown
> {code:java}
> 2021-03-04 08:04:09,523 INFO - [etp1020520290-753 -
> a28b425d-7409-4891-b440-6cc41daf3a16:knox:DELETE/api/atlas/v2/types/typedefs]
> ~ GraphTransaction intercept for
> org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.deleteTypesDef
> (GraphTransactionAdvisor$1:41)
> 2021-03-04 08:04:09,526 ERROR - [etp1020520290-753 -
> a28b425d-7409-4891-b440-6cc41daf3a16:knox:DELETE/api/atlas/v2/types/typedefs]
> ~ graph rollback due to exception (GraphTransactionInterceptor:192)
> java.lang.NullPointerException
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.deleteTypesDef(AtlasTypeDefGraphStore.java:565)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySpringCGLIB$$5226c80b.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:737)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:540)
> at
> org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:395)
> at
> org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2021-03-04 08:04:03,989 INFO - [etp1020520290-753:] ~ Logged into Atlas as =
> HTTP (AtlasAuthenticationFilter$KerberosFilterChainWrapper:726){code}
> Delete call body:
> {code:java}
> {"businessMetadataDefs": [{"name": "bm_xvsym_1"}, {"name": "bm_xvsym_2"}]}
> {code}
> This is used to perform bulk create and perform bulk delete.
> While knox proxy is enabled, NullPointerException is thrown
> Need an alternate way to perform bulk delete with knox enabled
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4814) CI build fails in distro module with error: Cannot run program "python"
[
https://issues.apache.org/jira/browse/ATLAS-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788837#comment-17788837
]
ASF subversion and git services commented on ATLAS-4814:
Commit f72f5ec58f8da843fed072d2b94f3abd948a4716 in atlas's branch
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f72f5ec58 ]
ATLAS-4814: updated build/python scripts to replace references to python with
python3
(cherry picked from commit 0f331aa63095bae010f2c4cb0a76e58eb5606e1b)
> CI build fails in distro module with error: Cannot run program "python"
> ---
>
> Key: ATLAS-4814
> URL: https://issues.apache.org/jira/browse/ATLAS-4814
> Project: Atlas
> Issue Type: Bug
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4184.patch
>
>
> Atlas CI build (Atlas-master-IntegrationTests) fails with the following
> error, which is likely due to the build machine not having python2 installed.
>
> {noformat}
> [INFO] Apache Atlas Couchbase Bridge .. SUCCESS [ 24.697
> s]
> [INFO] Apache Atlas Distribution .. FAILURE [ 9.103 s]
> [INFO] atlas-examples . SKIPPED
> [INFO] sample-app . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:56 h
> [INFO] Finished at: 2023-11-21T20:44:37Z
> [INFO]
>
> Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (python-test) on project
> atlas-distro: Command execution failed. Cannot run program "python" (in
> directory
> "/home/jenkins/jenkins-agent/workspace/Atlas/Atlas-master-IntegrationTests/distro/src/test/python"):
> error=2, No such file or directory -> [Help 1][ERROR] [ERROR] To see the
> full stack trace of the errors, re-run Maven with the -e switch.[ERROR]
> Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR]
> For more information about the errors and possible solutions, please read the
> following articles:[ERROR] [Help 1]
> [http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException][ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command[ERROR] mvn -rf :atlas-distrochannel stopped
> Exception: java.lang.LinkageError thrown from the UncaughtExceptionHandler in
> thread "Thread-942"
> Finished: FAILURE
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4184) [Atlas] Need a way to perform bulk delete typedef when knox proxy is enabled
[
https://issues.apache.org/jira/browse/ATLAS-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788836#comment-17788836
]
ASF subversion and git services commented on ATLAS-4184:
Commit 87fb3a4a4e3eae1b89909ac052139be1e0f164ee in atlas's branch
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=87fb3a4a4 ]
ATLAS-4184: updated build/python scripts to replace references to python with
python3
(cherry picked from commit 0f331aa63095bae010f2c4cb0a76e58eb5606e1b)
> [Atlas] Need a way to perform bulk delete typedef when knox proxy is enabled
>
>
> Key: ATLAS-4184
> URL: https://issues.apache.org/jira/browse/ATLAS-4184
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
>
> While performing bulk delete operation on typedef, NullPointerException is
> thrown
> {code:java}
> 2021-03-04 08:04:09,523 INFO - [etp1020520290-753 -
> a28b425d-7409-4891-b440-6cc41daf3a16:knox:DELETE/api/atlas/v2/types/typedefs]
> ~ GraphTransaction intercept for
> org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.deleteTypesDef
> (GraphTransactionAdvisor$1:41)
> 2021-03-04 08:04:09,526 ERROR - [etp1020520290-753 -
> a28b425d-7409-4891-b440-6cc41daf3a16:knox:DELETE/api/atlas/v2/types/typedefs]
> ~ graph rollback due to exception (GraphTransactionInterceptor:192)
> java.lang.NullPointerException
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.deleteTypesDef(AtlasTypeDefGraphStore.java:565)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySpringCGLIB$$5226c80b.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:737)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:540)
> at
> org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:395)
> at
> org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2021-03-04 08:04:03,989 INFO - [etp1020520290-753:] ~ Logged into Atlas as =
> HTTP (AtlasAuthenticationFilter$KerberosFilterChainWrapper:726){code}
> Delete call body:
> {code:java}
> {"businessMetadataDefs": [{"name": "bm_xvsym_1"}, {"name": "bm_xvsym_2"}]}
> {code}
> This is used to perform bulk create and perform bulk delete.
> While knox proxy is enabled, NullPointerException is thrown
> Need an alternate way to perform bulk delete with knox enabled
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4184) [Atlas] Need a way to perform bulk delete typedef when knox proxy is enabled
[
https://issues.apache.org/jira/browse/ATLAS-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788835#comment-17788835
]
ASF subversion and git services commented on ATLAS-4184:
Commit 0f331aa63095bae010f2c4cb0a76e58eb5606e1b in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=0f331aa63 ]
ATLAS-4184: updated build/python scripts to replace references to python with
python3
> [Atlas] Need a way to perform bulk delete typedef when knox proxy is enabled
>
>
> Key: ATLAS-4184
> URL: https://issues.apache.org/jira/browse/ATLAS-4184
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
>
> While performing bulk delete operation on typedef, NullPointerException is
> thrown
> {code:java}
> 2021-03-04 08:04:09,523 INFO - [etp1020520290-753 -
> a28b425d-7409-4891-b440-6cc41daf3a16:knox:DELETE/api/atlas/v2/types/typedefs]
> ~ GraphTransaction intercept for
> org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.deleteTypesDef
> (GraphTransactionAdvisor$1:41)
> 2021-03-04 08:04:09,526 ERROR - [etp1020520290-753 -
> a28b425d-7409-4891-b440-6cc41daf3a16:knox:DELETE/api/atlas/v2/types/typedefs]
> ~ graph rollback due to exception (GraphTransactionInterceptor:192)
> java.lang.NullPointerException
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.deleteTypesDef(AtlasTypeDefGraphStore.java:565)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySpringCGLIB$$5226c80b.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:737)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:540)
> at
> org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:395)
> at
> org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2021-03-04 08:04:03,989 INFO - [etp1020520290-753:] ~ Logged into Atlas as =
> HTTP (AtlasAuthenticationFilter$KerberosFilterChainWrapper:726){code}
> Delete call body:
> {code:java}
> {"businessMetadataDefs": [{"name": "bm_xvsym_1"}, {"name": "bm_xvsym_2"}]}
> {code}
> This is used to perform bulk create and perform bulk delete.
> While knox proxy is enabled, NullPointerException is thrown
> Need an alternate way to perform bulk delete with knox enabled
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4789) Add Couchbase bridge
[ https://issues.apache.org/jira/browse/ATLAS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788563#comment-17788563 ] ASF subversion and git services commented on ATLAS-4789: Commit abafe2b113e372d48ca23f03ccbd4b6f92335dd8 in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=abafe2b11 ] ATLAS-4789: added couchbase bridge #2 - fixed incorrect parent.version in pom.xml > Add Couchbase bridge > > > Key: ATLAS-4789 > URL: https://issues.apache.org/jira/browse/ATLAS-4789 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Dmitrii Chechetkin >Assignee: Dmitrii Chechetkin >Priority: Major > Attachments: ATLAS-4789.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > We at couchbase developed a bridge for Atlas that connectes to our database > and decided to release it into open-source. Needed to create the ticket to > open the pull request. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4810) Atlas UI Basic Searching result sorting option not available on all Columns
[ https://issues.apache.org/jira/browse/ATLAS-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788432#comment-17788432 ] ASF subversion and git services commented on ATLAS-4810: Commit 62d89cbbd80faa527529939e75c5170ef2a9adc8 in atlas's branch refs/heads/branch-2.0 from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=62d89cbbd ] ATLAS-4810: Atlas UI Basic Searching result sorting option not available on all Columns Signed-off-by: Prasad Pawar > Atlas UI Basic Searching result sorting option not available on all Columns > --- > > Key: ATLAS-4810 > URL: https://issues.apache.org/jira/browse/ATLAS-4810 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4810-Atlas-UI-Basic-Searching-result-sorting-o.patch, Atlas > Advanced Searching result sorting.png, Atlas Basic Searching result > sorting.png, advanced-search.PNG, basic-search.PNG > > > Basically in Basic search (hive_column as an example), we can add the Columns > from the right side for the results, but those added Columns don't have the > sorting option (Ascending/Descending) on the UI , only 4 default Columns > (Name, Owner, Description and Type) has sorting option. > However if using Advanced reaching, we query the same Column name "from > hive_column select position", that "position" has the sort errors next to it. > Same Column "position" in Basic Searching doesn't have the sort function. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4810) Atlas UI Basic Searching result sorting option not available on all Columns
[ https://issues.apache.org/jira/browse/ATLAS-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788431#comment-17788431 ] ASF subversion and git services commented on ATLAS-4810: Commit cef591433939ca9254971976362b99883ebec8c6 in atlas's branch refs/heads/master from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=cef591433 ] ATLAS-4810: Atlas UI Basic Searching result sorting option not available on all Columns Signed-off-by: Prasad Pawar > Atlas UI Basic Searching result sorting option not available on all Columns > --- > > Key: ATLAS-4810 > URL: https://issues.apache.org/jira/browse/ATLAS-4810 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4810-Atlas-UI-Basic-Searching-result-sorting-o.patch, Atlas > Advanced Searching result sorting.png, Atlas Basic Searching result > sorting.png, advanced-search.PNG, basic-search.PNG > > > Basically in Basic search (hive_column as an example), we can add the Columns > from the right side for the results, but those added Columns don't have the > sorting option (Ascending/Descending) on the UI , only 4 default Columns > (Name, Owner, Description and Type) has sorting option. > However if using Advanced reaching, we query the same Column name "from > hive_column select position", that "position" has the sort errors next to it. > Same Column "position" in Basic Searching doesn't have the sort function. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4738) Dynamic Index Recovery issues and improvements
[
https://issues.apache.org/jira/browse/ATLAS-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786965#comment-17786965
]
ASF subversion and git services commented on ATLAS-4738:
Commit 52aaf934bc0a3a6d079fe7b1722fe49b16b3f666 in atlas's branch
refs/heads/branch-2.0 from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=52aaf934b ]
ATLAS-4738: Dynamic Index Recovery issues and improvements
Signed-off-by: radhikakundam
(cherry picked from commit 882954e2969d6018d2bc8977f9dc18a6e3d1d5ce)
> Dynamic Index Recovery issues and improvements
> --
>
> Key: ATLAS-4738
> URL: https://issues.apache.org/jira/browse/ATLAS-4738
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> # Though there is no issues with SOLR, on Atlas startup Index recovery is
> getting started as it's considering 1970-01-01T00:00:00Z as default recovery
> start time.
> When no index recovery data is available by default it'll consider
> recovery start time based on TTL i.e., (current time - tx.log TTL).
> By default SOLR tx.log default ttl is configured as 10days.
> 2. Custom start time configuration atlas.graph.index.recovery.start.time is
> not working as it conflicts with janusgraph internal configurations. This
> config should be updated to *atlas.index.recovery.start.time*
> 3. When SOLR went down with existing architecture we note down start time
> with a buffer of solr health checkup frequency which will be (current time -
> retrytime of solr health). To avoid any possible corner case scenarios
> updating the buffer two times of retry time so next recovery start time
> should be (current time - 2 * retry time)
> 4. Added REST support for index recovery which can give more flexibility to
> the customer to start index recovery on-demand and will be valubale feature.
> a. Get index recovery timing details
> API: GET api/atlas/v2/indexrecovery/
> Response:
> { "Latest start time": "2023-03-25T20:34:59.704Z", => Start
> time of recent/upcoming Index recovery
> "On-demand start time":
> "2023-03-24T06:17:23.656Z", => Start time of index recovery requested through
> REST API
> "Previous start time":
> "2023-03-25T20:24:51.583Z" => Start time of previous index recovery
> }
> b. Start index recovery at a specific time
> API: POST
> api/atlas/v2/indexrecovery/start?startTime=2023-03-24T06:17:23.656Z
> Response:
> On success => 200 OK
> On empty start Time => 400 Bad request
> On Index recovery failure => 500 Internal Server Error
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4738) Dynamic Index Recovery issues and improvements
[
https://issues.apache.org/jira/browse/ATLAS-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786964#comment-17786964
]
ASF subversion and git services commented on ATLAS-4738:
Commit 882954e2969d6018d2bc8977f9dc18a6e3d1d5ce in atlas's branch
refs/heads/master from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=882954e29 ]
ATLAS-4738: Dynamic Index Recovery issues and improvements
Signed-off-by: radhikakundam
> Dynamic Index Recovery issues and improvements
> --
>
> Key: ATLAS-4738
> URL: https://issues.apache.org/jira/browse/ATLAS-4738
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> # Though there is no issues with SOLR, on Atlas startup Index recovery is
> getting started as it's considering 1970-01-01T00:00:00Z as default recovery
> start time.
> When no index recovery data is available by default it'll consider
> recovery start time based on TTL i.e., (current time - tx.log TTL).
> By default SOLR tx.log default ttl is configured as 10days.
> 2. Custom start time configuration atlas.graph.index.recovery.start.time is
> not working as it conflicts with janusgraph internal configurations. This
> config should be updated to *atlas.index.recovery.start.time*
> 3. When SOLR went down with existing architecture we note down start time
> with a buffer of solr health checkup frequency which will be (current time -
> retrytime of solr health). To avoid any possible corner case scenarios
> updating the buffer two times of retry time so next recovery start time
> should be (current time - 2 * retry time)
> 4. Added REST support for index recovery which can give more flexibility to
> the customer to start index recovery on-demand and will be valubale feature.
> a. Get index recovery timing details
> API: GET api/atlas/v2/indexrecovery/
> Response:
> { "Latest start time": "2023-03-25T20:34:59.704Z", => Start
> time of recent/upcoming Index recovery
> "On-demand start time":
> "2023-03-24T06:17:23.656Z", => Start time of index recovery requested through
> REST API
> "Previous start time":
> "2023-03-25T20:24:51.583Z" => Start time of previous index recovery
> }
> b. Start index recovery at a specific time
> API: POST
> api/atlas/v2/indexrecovery/start?startTime=2023-03-24T06:17:23.656Z
> Response:
> On success => 200 OK
> On empty start Time => 400 Bad request
> On Index recovery failure => 500 Internal Server Error
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4788) Kafka password is in clear text in application.properties
[ https://issues.apache.org/jira/browse/ATLAS-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783234#comment-17783234 ] ASF subversion and git services commented on ATLAS-4788: Commit 55519c0c13e19187ef3496d5f9f775e90cd6dbb0 in atlas's branch refs/heads/branch-2.0 from chaitali [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=55519c0c1 ] ATLAS-4788 : Kafka password is in clear text in application.properties Signed-off-by: Pinal Shah > Kafka password is in clear text in application.properties > - > > Key: ATLAS-4788 > URL: https://issues.apache.org/jira/browse/ATLAS-4788 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > atlas.jaas.KafkaClient.option.username=username > atlas.jaas.KafkaClient.option.password= > We have to encrypt this passsword using jceks file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4788) Kafka password is in clear text in application.properties
[ https://issues.apache.org/jira/browse/ATLAS-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783233#comment-17783233 ] ASF subversion and git services commented on ATLAS-4788: Commit 14adbad94a0de95f6d390b2d8c80d9bd914c0438 in atlas's branch refs/heads/master from chaitali [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=14adbad94 ] ATLAS-4788 : Kafka password is in clear text in application.properties Signed-off-by: Pinal Shah > Kafka password is in clear text in application.properties > - > > Key: ATLAS-4788 > URL: https://issues.apache.org/jira/browse/ATLAS-4788 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > atlas.jaas.KafkaClient.option.username=username > atlas.jaas.KafkaClient.option.password= > We have to encrypt this passsword using jceks file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4804) set name field with qualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782486#comment-17782486
]
ASF subversion and git services commented on ATLAS-4804:
Commit ec001a8e9200cc90f361351220ad17c102c0a793 in atlas's branch
refs/heads/branch-2.0 from pareshD
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ec001a8e9 ]
ATLAS-4804: Set name field with qualifiedName for impala_process and
impala_process_execution
Signed-off-by: Pinal Shah
> set name field with qualifiedName for impala_process and
> impala_process_execution
> -
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
> Attachments:
> ATLAS-4804-Migrated-Data-Process-Entity-Name-not-set.patch
>
>
> *Background*
> In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as
> the name. Latest version onwards where _name_ and _qualifiedName_ are same.
> *Solution*
> Add Java patch that updates the name property.
> *Impact of Not Doing this Update*
> The _queryText_ in _impala_process_ and impala_process_execution entities
> tends to be large. The name field is part of {_}AtlasEntityHeader{_}. When
> fetching search results, lineage display are some of the flows that have
> these entities.
> *Issue* *occurred*
> Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
> Error from server at
> [http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
> Exception writing document id muydq8 to the index; possible analysis error:
> Document contains at least one immense term in field="cgsl_s" (whose UTF8
> encoding is longer than the max length 32766), all of which were skipped.
> Please correct the analyzer to not produce such terms. The prefix of the
> first immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116,
> 111, 32, 103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103,
> 105, 103, 121]...', original message: bytes can be at most 32766 in length;
> got 41069. Perhaps the document has an indexed string field (solr.StrField)
> which is too large at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
> at
> org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
> at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
> ... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4804) set name field with qualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782485#comment-17782485
]
ASF subversion and git services commented on ATLAS-4804:
Commit 3574a60fd2fad0e12454893d754f3c6ab009717a in atlas's branch
refs/heads/master from pareshD
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3574a60fd ]
ATLAS-4804: Set name field with qualifiedName for impala_process and
impala_process_execution
Signed-off-by: Pinal Shah
> set name field with qualifiedName for impala_process and
> impala_process_execution
> -
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
> Attachments:
> ATLAS-4804-Migrated-Data-Process-Entity-Name-not-set.patch
>
>
> *Background*
> In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as
> the name. Latest version onwards where _name_ and _qualifiedName_ are same.
> *Solution*
> Add Java patch that updates the name property.
> *Impact of Not Doing this Update*
> The _queryText_ in _impala_process_ and impala_process_execution entities
> tends to be large. The name field is part of {_}AtlasEntityHeader{_}. When
> fetching search results, lineage display are some of the flows that have
> these entities.
> *Issue* *occurred*
> Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
> Error from server at
> [http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
> Exception writing document id muydq8 to the index; possible analysis error:
> Document contains at least one immense term in field="cgsl_s" (whose UTF8
> encoding is longer than the max length 32766), all of which were skipped.
> Please correct the analyzer to not produce such terms. The prefix of the
> first immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116,
> 111, 32, 103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103,
> 105, 103, 121]...', original message: bytes can be at most 32766 in length;
> got 41069. Perhaps the document has an indexed string field (solr.StrField)
> which is too large at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
> at
> org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
> at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
> ... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4789) Add Couchbase bridge
[ https://issues.apache.org/jira/browse/ATLAS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782290#comment-17782290 ] ASF subversion and git services commented on ATLAS-4789: Commit fd0d3a69fe97867b3565d0a2f497da6362ce5ef4 in atlas's branch refs/heads/master from Dmitrii Chechetkin [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fd0d3a69f ] ATLAS-4789: added couchbase bridge Signed-off-by: Madhan Neethiraj > Add Couchbase bridge > > > Key: ATLAS-4789 > URL: https://issues.apache.org/jira/browse/ATLAS-4789 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Dmitrii Chechetkin >Priority: Major > Attachments: ATLAS-4789.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > We at couchbase developed a bridge for Atlas that connectes to our database > and decided to release it into open-source. Needed to create the ticket to > open the pull request. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4789) Add Couchbase bridge
[ https://issues.apache.org/jira/browse/ATLAS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782291#comment-17782291 ] ASF subversion and git services commented on ATLAS-4789: Commit b4d06290e5281dd6afbfe3240e06928a8bd1d6bf in atlas's branch refs/heads/branch-2.0 from Dmitrii Chechetkin [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b4d06290e ] ATLAS-4789: added couchbase bridge Signed-off-by: Madhan Neethiraj (cherry picked from commit fd0d3a69fe97867b3565d0a2f497da6362ce5ef4) > Add Couchbase bridge > > > Key: ATLAS-4789 > URL: https://issues.apache.org/jira/browse/ATLAS-4789 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Dmitrii Chechetkin >Priority: Major > Attachments: ATLAS-4789.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > We at couchbase developed a bridge for Atlas that connectes to our database > and decided to release it into open-source. Needed to create the ticket to > open the pull request. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4801) Atlas - Upgrade Okio to 3.4.0 due to CVE-2023-3635
[ https://issues.apache.org/jira/browse/ATLAS-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782279#comment-17782279 ] ASF subversion and git services commented on ATLAS-4801: Commit 60b861512b27126932ad4298d675d1006a290eee in atlas's branch refs/heads/branch-2.0 from Disha Talreja [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=60b861512 ] ATLAS-4801: Atlas - Upgrade Okio to 3.4.0 due to CVE-2023-3635 Signed-off-by: radhikakundam (cherry picked from commit 830521b846619217bdad563f8b69ba5dd58a35d1) > Atlas - Upgrade Okio to 3.4.0 due to CVE-2023-3635 > -- > > Key: ATLAS-4801 > URL: https://issues.apache.org/jira/browse/ATLAS-4801 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Disha Talreja >Assignee: Disha Talreja >Priority: Major > Attachments: ATLAS-4801.patch > > > GzipSource does not handle an exception that might be raised when parsing a > malformed gzip buffer. This may lead to denial of service of the Okio client > when handling a crafted GZIP archive, by using the GzipSource class. > CVSSv3 Score:- 7.5(High) > [https://nvd.nist.gov/vuln/detail/CVE-2023-3635] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4800) Atlas - Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751
[ https://issues.apache.org/jira/browse/ATLAS-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782278#comment-17782278 ] ASF subversion and git services commented on ATLAS-4800: Commit bd35d3fd1ddb98920917195ef5129118dc99bd11 in atlas's branch refs/heads/branch-2.0 from Disha Talreja [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=bd35d3fd1 ] ATLAS-4800: Atlas - Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751 Signed-off-by: radhikakundam (cherry picked from commit 7e1286266ebd876c78d9130e057e25d58ebed052) > Atlas - Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751 > - > > Key: ATLAS-4800 > URL: https://issues.apache.org/jira/browse/ATLAS-4800 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Disha Talreja >Assignee: Disha Talreja >Priority: Major > Attachments: ATLAS-4800.patch > > > Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751 > Improper Restriction of XML External Entity Reference, XML Injection (aka > Blind XPath Injection) vulnerability in Apache Software Foundation Apache > Ivy.This issue affects any version of Apache Ivy prior to 2.5.2. When Apache > Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files > or Apache Maven POMs - it will allow downloading external document type > definitions and expand any entity references contained therein when used. > This can be used to exfiltrate data, access resources only the machine > running Ivy has access to or disturb the execution of Ivy in different ways. > CVSSv3 Score:- 8.2(High) > [https://nvd.nist.gov/vuln/detail/CVE-2022-46751] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4801) Atlas - Upgrade Okio to 3.4.0 due to CVE-2023-3635
[ https://issues.apache.org/jira/browse/ATLAS-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782273#comment-17782273 ] ASF subversion and git services commented on ATLAS-4801: Commit 830521b846619217bdad563f8b69ba5dd58a35d1 in atlas's branch refs/heads/master from Disha Talreja [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=830521b84 ] ATLAS-4801: Atlas - Upgrade Okio to 3.4.0 due to CVE-2023-3635 Signed-off-by: radhikakundam > Atlas - Upgrade Okio to 3.4.0 due to CVE-2023-3635 > -- > > Key: ATLAS-4801 > URL: https://issues.apache.org/jira/browse/ATLAS-4801 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Disha Talreja >Assignee: Disha Talreja >Priority: Major > Attachments: ATLAS-4801.patch > > > GzipSource does not handle an exception that might be raised when parsing a > malformed gzip buffer. This may lead to denial of service of the Okio client > when handling a crafted GZIP archive, by using the GzipSource class. > CVSSv3 Score:- 7.5(High) > [https://nvd.nist.gov/vuln/detail/CVE-2023-3635] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4800) Atlas - Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751
[ https://issues.apache.org/jira/browse/ATLAS-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782265#comment-17782265 ] ASF subversion and git services commented on ATLAS-4800: Commit 7e1286266ebd876c78d9130e057e25d58ebed052 in atlas's branch refs/heads/master from Disha Talreja [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7e1286266 ] ATLAS-4800: Atlas - Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751 Signed-off-by: radhikakundam > Atlas - Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751 > - > > Key: ATLAS-4800 > URL: https://issues.apache.org/jira/browse/ATLAS-4800 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Disha Talreja >Assignee: Disha Talreja >Priority: Major > Attachments: ATLAS-4800.patch > > > Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751 > Improper Restriction of XML External Entity Reference, XML Injection (aka > Blind XPath Injection) vulnerability in Apache Software Foundation Apache > Ivy.This issue affects any version of Apache Ivy prior to 2.5.2. When Apache > Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files > or Apache Maven POMs - it will allow downloading external document type > definitions and expand any entity references contained therein when used. > This can be used to exfiltrate data, access resources only the machine > running Ivy has access to or disturb the execution of Ivy in different ways. > CVSSv3 Score:- 8.2(High) > [https://nvd.nist.gov/vuln/detail/CVE-2022-46751] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4807) Fix IT test related to Labels
[ https://issues.apache.org/jira/browse/ATLAS-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781688#comment-17781688 ] ASF subversion and git services commented on ATLAS-4807: Commit 123f7619aabd630464e17a3e4457fcd77bedc74d in atlas's branch refs/heads/branch-2.0 from Pinal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=123f7619a ] ATLAS-4807: Fix IT test related to Labels Signed-off-by: Pinal Shah > Fix IT test related to Labels > - > > Key: ATLAS-4807 > URL: https://issues.apache.org/jira/browse/ATLAS-4807 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > testSetLabelsByTypeName(org.apache.atlas.web.integration.EntityV2JerseyResourceIT) > test is failing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4807) Fix IT test related to Labels
[ https://issues.apache.org/jira/browse/ATLAS-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781687#comment-17781687 ] ASF subversion and git services commented on ATLAS-4807: Commit 55d79065b352fc623bd5bad14324ffc043dd5fcd in atlas's branch refs/heads/master from Pinal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=55d79065b ] ATLAS-4807: Fix IT test related to Labels Signed-off-by: Pinal Shah > Fix IT test related to Labels > - > > Key: ATLAS-4807 > URL: https://issues.apache.org/jira/browse/ATLAS-4807 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > testSetLabelsByTypeName(org.apache.atlas.web.integration.EntityV2JerseyResourceIT) > test is failing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4805) UI: Text editor improvements and code clean up.
[ https://issues.apache.org/jira/browse/ATLAS-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781344#comment-17781344 ] ASF subversion and git services commented on ATLAS-4805: Commit 30e5613ae6e2b0f623a4c88c899a84edd2b5cf4b in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=30e5613ae ] ATLAS-4805: (UI)Text editor improvements and code clean up Signed-off-by: Prasad Pawar > UI: Text editor improvements and code clean up. > --- > > Key: ATLAS-4805 > URL: https://issues.apache.org/jira/browse/ATLAS-4805 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4805-UI-Text-editor-improvements-and-code-clea.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4805) UI: Text editor improvements and code clean up.
[ https://issues.apache.org/jira/browse/ATLAS-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781341#comment-17781341 ] ASF subversion and git services commented on ATLAS-4805: Commit 35ce839f0a24f8080ca5d0f6841e261c8becb347 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=35ce839f0 ] ATLAS-4805: (UI)Text editor improvements and code clean up Signed-off-by: Prasad Pawar > UI: Text editor improvements and code clean up. > --- > > Key: ATLAS-4805 > URL: https://issues.apache.org/jira/browse/ATLAS-4805 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4805-UI-Text-editor-improvements-and-code-clea.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4732) UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date entries
[
https://issues.apache.org/jira/browse/ATLAS-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770331#comment-17770331
]
ASF subversion and git services commented on ATLAS-4732:
Commit f2afb2919e23369e64112599cea19136b3225a8b in atlas's branch
refs/heads/branch-2.0 from Prasad Pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f2afb2919 ]
ATLAS-4732:UI: Setting 'atlas.ui.date.format' to certain value creates
incorrect date entries
Signed-off-by: Prasad Pawar
> UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date
> entries
> --
>
> Key: ATLAS-4732
> URL: https://issues.apache.org/jira/browse/ATLAS-4732
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4732-UI-Setting-atlas.ui.date.format-to-certai.patch
>
>
> Pre-conditions:
> In atlas-application.properties, set the following:-
> {code:java}
> atlas.ui.date.format=DD/MM/ hh:mm:ss{code}
> Steps:
> 1. Create Business Metadata with a date type and assign to a Type (e.g.
> hdfs_path)
> 2. Create an entity for the assigned Type (hdfs_path).
> 3. Add Business Metadata and select the created date type.
> 4. Populate this value with a date in DD/MM/ format, i.e. (06/03/2023)
> 5. Click Apply.
> 6. Click Save.
> The date changes to 03/06/2023 which is a completely different date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4732) UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date entries
[
https://issues.apache.org/jira/browse/ATLAS-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770330#comment-17770330
]
ASF subversion and git services commented on ATLAS-4732:
Commit 6b36c59a93b9963b7a9797f3f7fec25284f7af96 in atlas's branch
refs/heads/master from Prasad Pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=6b36c59a9 ]
ATLAS-4732:UI: Setting 'atlas.ui.date.format' to certain value creates
incorrect date entries
Signed-off-by: Prasad Pawar
> UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date
> entries
> --
>
> Key: ATLAS-4732
> URL: https://issues.apache.org/jira/browse/ATLAS-4732
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4732-UI-Setting-atlas.ui.date.format-to-certai.patch
>
>
> Pre-conditions:
> In atlas-application.properties, set the following:-
> {code:java}
> atlas.ui.date.format=DD/MM/ hh:mm:ss{code}
> Steps:
> 1. Create Business Metadata with a date type and assign to a Type (e.g.
> hdfs_path)
> 2. Create an entity for the assigned Type (hdfs_path).
> 3. Add Business Metadata and select the created date type.
> 4. Populate this value with a date in DD/MM/ format, i.e. (06/03/2023)
> 5. Click Apply.
> 6. Click Save.
> The date changes to 03/06/2023 which is a completely different date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4799) UI: Enum type Business metadata attribute shows incorrect data when specific string is in attribute name.
[ https://issues.apache.org/jira/browse/ATLAS-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769925#comment-17769925 ] ASF subversion and git services commented on ATLAS-4799: Commit e4c9c1e69f7bcb650f59848fe588105fac5bfc23 in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e4c9c1e69 ] ATLAS-4799 : (UI)Enum type Business metadata attribute shows incorrect data when specific string is in attribute name Signed-off-by: Pinal Shah > UI: Enum type Business metadata attribute shows incorrect data when specific > string is in attribute name. > - > > Key: ATLAS-4799 > URL: https://issues.apache.org/jira/browse/ATLAS-4799 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0, 2.3.0 >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-ATLAS-4799-UI-Enum-type-Business-metadata-attribute-.patch > > > 1. Create a enum such that its enum name contains the word 'date' (for > example, 'updatetest') with the following values: > v1,v2 > And then create a business metadata attribute whose type is the enum which we > have just now created. > 2. After assigning a enum value (v1 or v2) to the entity with this attribute, > it is observed that it displays some dates rather than 'v1' or 'v2'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4799) UI: Enum type Business metadata attribute shows incorrect data when specific string is in attribute name.
[ https://issues.apache.org/jira/browse/ATLAS-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769924#comment-17769924 ] ASF subversion and git services commented on ATLAS-4799: Commit a2e05cdb9319f22876e761200c006a1e7ab09437 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a2e05cdb9 ] ATLAS-4799 : (UI)Enum type Business metadata attribute shows incorrect data when specific string is in attribute name Signed-off-by: Pinal Shah > UI: Enum type Business metadata attribute shows incorrect data when specific > string is in attribute name. > - > > Key: ATLAS-4799 > URL: https://issues.apache.org/jira/browse/ATLAS-4799 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0, 2.3.0 >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-ATLAS-4799-UI-Enum-type-Business-metadata-attribute-.patch > > > 1. Create a enum such that its enum name contains the word 'date' (for > example, 'updatetest') with the following values: > v1,v2 > And then create a business metadata attribute whose type is the enum which we > have just now created. > 2. After assigning a enum value (v1 or v2) to the entity with this attribute, > it is observed that it displays some dates rather than 'v1' or 'v2'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4793) UI: Search Issues
[ https://issues.apache.org/jira/browse/ATLAS-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765018#comment-17765018 ] ASF subversion and git services commented on ATLAS-4793: Commit 4a0b9092e92dd9d989b4f98e3612aaaff120df9d in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4a0b9092e ] ATLAS-4793: (UI) Search Issues Signed-off-by: Prasad Pawar > UI: Search Issues > - > > Key: ATLAS-4793 > URL: https://issues.apache.org/jira/browse/ATLAS-4793 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Attachments: 0001-ATLAS-4793-UI-Search-Issues.patch > > > 1. Usually when a user enters a string in the quick search bar and presses > Enter, Atlas should trigger the search for the same. But instead user is > taken to a page with nothing displayed. > 2. When user clicks on the suggestions listed in the quick search dropdown, > user is taken to a page with nothing displayed. > 3. When user attempts to select _ALL_ENTITY_TYPES in the basic search > functionality, user is taken to a page with nothing displayed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4793) UI: Search Issues
[ https://issues.apache.org/jira/browse/ATLAS-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765017#comment-17765017 ] ASF subversion and git services commented on ATLAS-4793: Commit 4c0b47a476c563c4243e491e31d1da2fc04133c4 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4c0b47a47 ] ATLAS-4793: (UI) Search Issues Signed-off-by: Prasad Pawar > UI: Search Issues > - > > Key: ATLAS-4793 > URL: https://issues.apache.org/jira/browse/ATLAS-4793 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Attachments: 0001-ATLAS-4793-UI-Search-Issues.patch > > > 1. Usually when a user enters a string in the quick search bar and presses > Enter, Atlas should trigger the search for the same. But instead user is > taken to a page with nothing displayed. > 2. When user clicks on the suggestions listed in the quick search dropdown, > user is taken to a page with nothing displayed. > 3. When user attempts to select _ALL_ENTITY_TYPES in the basic search > functionality, user is taken to a page with nothing displayed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4783) Atlas fails to start if indexing backend isn't set to Solr
[
https://issues.apache.org/jira/browse/ATLAS-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763937#comment-17763937
]
ASF subversion and git services commented on ATLAS-4783:
Commit fad2746dca0b3fe534483fc6037443a4cae127f5 in atlas's branch
refs/heads/branch-2.0 from szymonorz
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fad2746dc ]
ATLAS-4783: Fix NoSuchElementException when running different indexing backend
than Solr
Signed-off-by: Madhan Neethiraj
(cherry picked from commit 33a2a55899109e2ebe82766d4ba1f3fd82962610)
> Atlas fails to start if indexing backend isn't set to Solr
> --
>
> Key: ATLAS-4783
> URL: https://issues.apache.org/jira/browse/ATLAS-4783
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Szymon Orzechowski
>Priority: Major
> Attachments: ATLAS-4783.patch
>
>
> If atlas.graph.index.search.backend is set to elasticsearch (which is in tech
> preview) and atlas.graph.index.search.solr.wait-searcher isn't set then Atlas
> fails to start and errors with
> {code:java}
> Caused by: java.util.NoSuchElementException:
> 'atlas.graph.index.search.solr.wait-searcher' doesn't map to an existing
> object
> at
> org.apache.commons.configuration.AbstractConfiguration.getBoolean(AbstractConfiguration.java:644)
> ~[?:?]
> at
> org.apache.atlas.ApplicationProperties.setDefaults(ApplicationProperties.java:374)
> ~[?:?]
> at
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:146)
> ~[?:?]
> ... 35 more
> {code}
> This property shouldn't be required in atlas-application.properties when
> elasticsearch is used
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4783) Atlas fails to start if indexing backend isn't set to Solr
[
https://issues.apache.org/jira/browse/ATLAS-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763936#comment-17763936
]
ASF subversion and git services commented on ATLAS-4783:
Commit 33a2a55899109e2ebe82766d4ba1f3fd82962610 in atlas's branch
refs/heads/master from szymonorz
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=33a2a5589 ]
ATLAS-4783: Fix NoSuchElementException when running different indexing backend
than Solr
Signed-off-by: Madhan Neethiraj
> Atlas fails to start if indexing backend isn't set to Solr
> --
>
> Key: ATLAS-4783
> URL: https://issues.apache.org/jira/browse/ATLAS-4783
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Szymon Orzechowski
>Priority: Major
> Attachments: ATLAS-4783.patch
>
>
> If atlas.graph.index.search.backend is set to elasticsearch (which is in tech
> preview) and atlas.graph.index.search.solr.wait-searcher isn't set then Atlas
> fails to start and errors with
> {code:java}
> Caused by: java.util.NoSuchElementException:
> 'atlas.graph.index.search.solr.wait-searcher' doesn't map to an existing
> object
> at
> org.apache.commons.configuration.AbstractConfiguration.getBoolean(AbstractConfiguration.java:644)
> ~[?:?]
> at
> org.apache.atlas.ApplicationProperties.setDefaults(ApplicationProperties.java:374)
> ~[?:?]
> at
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:146)
> ~[?:?]
> ... 35 more
> {code}
> This property shouldn't be required in atlas-application.properties when
> elasticsearch is used
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4795) Docker setup: support Apple M1 chip env
[
https://issues.apache.org/jira/browse/ATLAS-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763890#comment-17763890
]
ASF subversion and git services commented on ATLAS-4795:
Commit 368c90dfe35cf552e619dc1c69e9caa4c64b9497 in atlas's branch
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=368c90dfe ]
ATLAS-4795: docker setup updated to support Apple M1
(cherry picked from commit 3786524112d02951ac6a059085d303de2649e835)
> Docker setup: support Apple M1 chip env
> ---
>
> Key: ATLAS-4795
> URL: https://issues.apache.org/jira/browse/ATLAS-4795
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Attachments: ATLAS-4795.patch
>
>
> Docker setup scripts to build and run Atlas fails in environments that use
> Apple M1 chip:
>
> {noformat}
> atlas-base exited with code 0
> atlas-build | Building from /home/atlas/src
> atlas-build | The JAVA_HOME environment variable is not defined correctly
> atlas-build | This environment variable is needed to run this program
> atlas-build | NB: JAVA_HOME should point to a JDK not a JRE
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4794) HBase hook initialization failure: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.Layout
[
https://issues.apache.org/jira/browse/ATLAS-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763889#comment-17763889
]
ASF subversion and git services commented on ATLAS-4794:
Commit 8e2ff2797474c34b09f47875149762584b81138a in atlas's branch
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8e2ff2797 ]
ATLAS-4794: fixed initialization failure in HBase and Hive hooks
(cherry picked from commit dc5db3b6c1cf1929543d7c64c5b0d7d986f1cdd9)
> HBase hook initialization failure: java.lang.ClassNotFoundException:
> org.apache.logging.log4j.core.Layout
> -
>
> Key: ATLAS-4794
> URL: https://issues.apache.org/jira/browse/ATLAS-4794
> Project: Atlas
> Issue Type: Bug
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4794.patch
>
>
> Atlas Hbase hook fails during initialization with the following error in
> hbase-hbase-master-atlas-hbase.example.com.log:
> {noformat}
> 2023-09-08 19:12:04,599 ERROR [master/atlas-hbase:16000:becomeActiveMaster]
> coprocessor.CoprocessorHost: The coprocessor
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor threw java.io.IOException:
> java.lang.InstantiationException:
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor
> java.io.IOException: java.lang.InstantiationException:
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.checkAndLoadInstance(CoprocessorHost.java:280)
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors(CoprocessorHost.java:169)
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost.(MasterCoprocessorHost.java:157)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:1011)
> at
> org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2239)
> at
> org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:621)
> at java.lang.Thread.run(Thread.java:750)
> Caused by: java.lang.InstantiationException:
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost.checkAndGetInstance(MasterCoprocessorHost.java:191)
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost.checkAndGetInstance(MasterCoprocessorHost.java:71)
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.checkAndLoadInstance(CoprocessorHost.java:274)
> ... 6 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost.checkAndGetInstance(MasterCoprocessorHost.java:178)
> ... 8 more
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/logging/log4j/core/Layout
> at org.apache.atlas.hook.AtlasHook.(AtlasHook.java:96)
> at
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor.(HBaseAtlasCoprocessor.java:46)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor.init(HBaseAtlasCoprocessor.java:80)
> at
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor.(HBaseAtlasCoprocessor.java:60)
> ... 13 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.logging.log4j.core.Layout
> at java.lang.ClassLoader.findClass(ClassLoader.java:523)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(AtlasPluginClassLoader.java:347)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader.loadClass(AtlasPluginClassLoader.java:144)
> ... 22 more
> 2023-09-08 19:12:04,601 ERROR [master/atlas-hbase:16000:becomeActiveMaster]
>
[jira] [Commented] (ATLAS-4795) Docker setup: support Apple M1 chip env
[
https://issues.apache.org/jira/browse/ATLAS-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763877#comment-17763877
]
ASF subversion and git services commented on ATLAS-4795:
Commit 3786524112d02951ac6a059085d303de2649e835 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=378652411 ]
ATLAS-4795: docker setup updated to support Apple M1
> Docker setup: support Apple M1 chip env
> ---
>
> Key: ATLAS-4795
> URL: https://issues.apache.org/jira/browse/ATLAS-4795
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Attachments: ATLAS-4795.patch
>
>
> Docker setup scripts to build and run Atlas fails in environments that use
> Apple M1 chip:
>
> {noformat}
> atlas-base exited with code 0
> atlas-build | Building from /home/atlas/src
> atlas-build | The JAVA_HOME environment variable is not defined correctly
> atlas-build | This environment variable is needed to run this program
> atlas-build | NB: JAVA_HOME should point to a JDK not a JRE
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4794) HBase hook initialization failure: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.Layout
[
https://issues.apache.org/jira/browse/ATLAS-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763876#comment-17763876
]
ASF subversion and git services commented on ATLAS-4794:
Commit dc5db3b6c1cf1929543d7c64c5b0d7d986f1cdd9 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=dc5db3b6c ]
ATLAS-4794: fixed initialization failure in HBase and Hive hooks
> HBase hook initialization failure: java.lang.ClassNotFoundException:
> org.apache.logging.log4j.core.Layout
> -
>
> Key: ATLAS-4794
> URL: https://issues.apache.org/jira/browse/ATLAS-4794
> Project: Atlas
> Issue Type: Bug
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4794.patch
>
>
> Atlas Hbase hook fails during initialization with the following error in
> hbase-hbase-master-atlas-hbase.example.com.log:
> {noformat}
> 2023-09-08 19:12:04,599 ERROR [master/atlas-hbase:16000:becomeActiveMaster]
> coprocessor.CoprocessorHost: The coprocessor
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor threw java.io.IOException:
> java.lang.InstantiationException:
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor
> java.io.IOException: java.lang.InstantiationException:
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.checkAndLoadInstance(CoprocessorHost.java:280)
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors(CoprocessorHost.java:169)
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost.(MasterCoprocessorHost.java:157)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:1011)
> at
> org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2239)
> at
> org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:621)
> at java.lang.Thread.run(Thread.java:750)
> Caused by: java.lang.InstantiationException:
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost.checkAndGetInstance(MasterCoprocessorHost.java:191)
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost.checkAndGetInstance(MasterCoprocessorHost.java:71)
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.checkAndLoadInstance(CoprocessorHost.java:274)
> ... 6 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost.checkAndGetInstance(MasterCoprocessorHost.java:178)
> ... 8 more
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/logging/log4j/core/Layout
> at org.apache.atlas.hook.AtlasHook.(AtlasHook.java:96)
> at
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor.(HBaseAtlasCoprocessor.java:46)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor.init(HBaseAtlasCoprocessor.java:80)
> at
> org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor.(HBaseAtlasCoprocessor.java:60)
> ... 13 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.logging.log4j.core.Layout
> at java.lang.ClassLoader.findClass(ClassLoader.java:523)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(AtlasPluginClassLoader.java:347)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader.loadClass(AtlasPluginClassLoader.java:144)
> ... 22 more
> 2023-09-08 19:12:04,601 ERROR [master/atlas-hbase:16000:becomeActiveMaster]
> master.HMaster: * ABORTING master
>
[jira] [Commented] (ATLAS-4792) build failure in Apple M1 env
[
https://issues.apache.org/jira/browse/ATLAS-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762956#comment-17762956
]
ASF subversion and git services commented on ATLAS-4792:
Commit 9b13490785b112b0879ed32c88898aa21459 in atlas's branch
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9b1349078 ]
ATLAS-4792: fix to address build failure in Pro with Apple M1 chip
(cherry picked from commit d67cd509e5c8f9779026bcf992549a1901c92229)
> build failure in Apple M1 env
> -
>
> Key: ATLAS-4792
> URL: https://issues.apache.org/jira/browse/ATLAS-4792
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4792.patch
>
>
> Building Atlas master branch fails in MacBook Pro with Apple M1 chip, with
> the following:
> {noformat}
> [INFO] --- frontend-maven-plugin:1.4:install-node-and-npm (install node and
> npm) @ atlas-dashboardv2 ---
> [INFO] Installing node version v12.16.0
> [INFO] Downloading
> https://nodejs.org/dist/v12.16.0/node-v12.16.0-darwin-arm64.tar.gz to
> ~/.m2/repository/com/github/eirslett/node/12.16.0/node-12.16.0-darwin-arm64.tar.gz
> [INFO] No proxies configured
> [INFO] No proxy was configured, downloading directly
> [INFO]
>
> [INFO] Reactor Summary for apache-atlas 3.0.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Atlas Server Build Tools SUCCESS [ 1.056
> s]
> [INFO] apache-atlas ... SUCCESS [ 7.362
> s]
> [INFO] Apache Atlas Integration ... SUCCESS [ 22.299
> s]
> [INFO] Apache Atlas Test Utility Tools SUCCESS [ 8.182
> s]
> [INFO] Apache Atlas Common SUCCESS [ 9.194
> s]
> [INFO] Apache Atlas Client SUCCESS [ 0.410
> s]
> [INFO] atlas-client-common SUCCESS [ 3.962
> s]
> [INFO] atlas-client-v1 SUCCESS [ 4.495
> s]
> [INFO] Apache Atlas Server API SUCCESS [ 6.009
> s]
> [INFO] atlas-client-v2 SUCCESS [ 3.849
> s]
> [INFO] Apache Atlas Notification .. SUCCESS [ 11.231
> s]
> [INFO] Apache Atlas Graph Database Projects ... SUCCESS [ 0.355
> s]
> [INFO] Apache Atlas Graph Database API SUCCESS [ 3.687
> s]
> [INFO] Graph Database Common Code . SUCCESS [ 3.410
> s]
> [INFO] Apache Atlas JanusGraph-HBase2 Module .. SUCCESS [ 4.272
> s]
> [INFO] Apache Atlas JanusGraph DB Impl SUCCESS [ 17.223
> s]
> [INFO] Apache Atlas Graph Database Implementation Dependencies SUCCESS [
> 2.734 s]
> [INFO] Apache Atlas Authorization . SUCCESS [ 7.162
> s]
> [INFO] Apache Atlas Repository SUCCESS [ 38.694
> s]
> [INFO] Apache Atlas UI FAILURE [ 35.820
> s]
> [INFO] Apache Atlas New UI SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas FileSystem Model .. SKIPPED
> [INFO] Apache Atlas Plugin Classloader SKIPPED
> [INFO] Apache Atlas Hive Bridge Shim .. SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO] Apache Atlas Falcon Bridge Shim SKIPPED
> [INFO] Apache Atlas Falcon Bridge . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge Shim . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge .. SKIPPED
> [INFO] Apache Atlas Storm Bridge Shim . SKIPPED
> [INFO] Apache Atlas Storm Bridge .. SKIPPED
> [INFO] Apache Atlas Hbase Bridge Shim . SKIPPED
> [INFO] Apache Atlas Hbase Bridge .. SKIPPED
> [INFO] Apache HBase - Testing Util SKIPPED
> [INFO] Apache Atlas Kafka Bridge .. SKIPPED
> [INFO] Apache Atlas classification updater SKIPPED
> [INFO] Apache Atlas index repair tool . SKIPPED
> [INFO] Apache Atlas Impala Hook API ... SKIPPED
> [INFO] Apache Atlas Impala Bridge Shim SKIPPED
> [INFO] Apache Atlas Impala Bridge . SKIPPED
> [INFO] Apache Atlas Distribution
[jira] [Commented] (ATLAS-4792) build failure in Apple M1 env
[
https://issues.apache.org/jira/browse/ATLAS-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762955#comment-17762955
]
ASF subversion and git services commented on ATLAS-4792:
Commit d67cd509e5c8f9779026bcf992549a1901c92229 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d67cd509e ]
ATLAS-4792: fix to address build failure in Pro with Apple M1 chip
> build failure in Apple M1 env
> -
>
> Key: ATLAS-4792
> URL: https://issues.apache.org/jira/browse/ATLAS-4792
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4792.patch
>
>
> Building Atlas master branch fails in MacBook Pro with Apple M1 chip, with
> the following:
> {noformat}
> [INFO] --- frontend-maven-plugin:1.4:install-node-and-npm (install node and
> npm) @ atlas-dashboardv2 ---
> [INFO] Installing node version v12.16.0
> [INFO] Downloading
> https://nodejs.org/dist/v12.16.0/node-v12.16.0-darwin-arm64.tar.gz to
> ~/.m2/repository/com/github/eirslett/node/12.16.0/node-12.16.0-darwin-arm64.tar.gz
> [INFO] No proxies configured
> [INFO] No proxy was configured, downloading directly
> [INFO]
>
> [INFO] Reactor Summary for apache-atlas 3.0.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Atlas Server Build Tools SUCCESS [ 1.056
> s]
> [INFO] apache-atlas ... SUCCESS [ 7.362
> s]
> [INFO] Apache Atlas Integration ... SUCCESS [ 22.299
> s]
> [INFO] Apache Atlas Test Utility Tools SUCCESS [ 8.182
> s]
> [INFO] Apache Atlas Common SUCCESS [ 9.194
> s]
> [INFO] Apache Atlas Client SUCCESS [ 0.410
> s]
> [INFO] atlas-client-common SUCCESS [ 3.962
> s]
> [INFO] atlas-client-v1 SUCCESS [ 4.495
> s]
> [INFO] Apache Atlas Server API SUCCESS [ 6.009
> s]
> [INFO] atlas-client-v2 SUCCESS [ 3.849
> s]
> [INFO] Apache Atlas Notification .. SUCCESS [ 11.231
> s]
> [INFO] Apache Atlas Graph Database Projects ... SUCCESS [ 0.355
> s]
> [INFO] Apache Atlas Graph Database API SUCCESS [ 3.687
> s]
> [INFO] Graph Database Common Code . SUCCESS [ 3.410
> s]
> [INFO] Apache Atlas JanusGraph-HBase2 Module .. SUCCESS [ 4.272
> s]
> [INFO] Apache Atlas JanusGraph DB Impl SUCCESS [ 17.223
> s]
> [INFO] Apache Atlas Graph Database Implementation Dependencies SUCCESS [
> 2.734 s]
> [INFO] Apache Atlas Authorization . SUCCESS [ 7.162
> s]
> [INFO] Apache Atlas Repository SUCCESS [ 38.694
> s]
> [INFO] Apache Atlas UI FAILURE [ 35.820
> s]
> [INFO] Apache Atlas New UI SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas FileSystem Model .. SKIPPED
> [INFO] Apache Atlas Plugin Classloader SKIPPED
> [INFO] Apache Atlas Hive Bridge Shim .. SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO] Apache Atlas Falcon Bridge Shim SKIPPED
> [INFO] Apache Atlas Falcon Bridge . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge Shim . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge .. SKIPPED
> [INFO] Apache Atlas Storm Bridge Shim . SKIPPED
> [INFO] Apache Atlas Storm Bridge .. SKIPPED
> [INFO] Apache Atlas Hbase Bridge Shim . SKIPPED
> [INFO] Apache Atlas Hbase Bridge .. SKIPPED
> [INFO] Apache HBase - Testing Util SKIPPED
> [INFO] Apache Atlas Kafka Bridge .. SKIPPED
> [INFO] Apache Atlas classification updater SKIPPED
> [INFO] Apache Atlas index repair tool . SKIPPED
> [INFO] Apache Atlas Impala Hook API ... SKIPPED
> [INFO] Apache Atlas Impala Bridge Shim SKIPPED
> [INFO] Apache Atlas Impala Bridge . SKIPPED
> [INFO] Apache Atlas Distribution .. SKIPPED
> [INFO] atlas-examples
[jira] [Commented] (ATLAS-4785) AtlasClientV2 label methods use incorrect API_V2
[ https://issues.apache.org/jira/browse/ATLAS-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761697#comment-17761697 ] ASF subversion and git services commented on ATLAS-4785: Commit 3fddba845cfa5673a0a605663710c416638630dd in atlas's branch refs/heads/branch-2.0 from Zhen Wang [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3fddba845 ] ATLAS-4785: Fix incorrect references in AtlasClientV2 label methods Signed-off-by: Madhan Neethiraj > AtlasClientV2 label methods use incorrect API_V2 > > > Key: ATLAS-4785 > URL: https://issues.apache.org/jira/browse/ATLAS-4785 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.3.0 >Reporter: Zhen Wang >Priority: Major > Fix For: 3.0.0 > > Attachments: image-2023-08-18-13-41-31-830.png > > Time Spent: 10m > Remaining Estimate: 0h > > `AtlasClientV2.addLabels` by unique attribute method and > `AtlasClientV2.setLabels` by unique attribute method use incorrect `API_V2`. > !image-2023-08-18-13-41-31-830.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4785) AtlasClientV2 label methods use incorrect API_V2
[ https://issues.apache.org/jira/browse/ATLAS-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761696#comment-17761696 ] ASF subversion and git services commented on ATLAS-4785: Commit adf3006b9411a80fb19d5264c67721480f43e33c in atlas's branch refs/heads/master from Zhen Wang [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=adf3006b9 ] ATLAS-4785: Fix incorrect references in AtlasClientV2 label methods Merge pull request #237 from wForget/dev Signed-off-by: Madhan Neethiraj > AtlasClientV2 label methods use incorrect API_V2 > > > Key: ATLAS-4785 > URL: https://issues.apache.org/jira/browse/ATLAS-4785 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.3.0 >Reporter: Zhen Wang >Priority: Major > Attachments: image-2023-08-18-13-41-31-830.png > > Time Spent: 10m > Remaining Estimate: 0h > > `AtlasClientV2.addLabels` by unique attribute method and > `AtlasClientV2.setLabels` by unique attribute method use incorrect `API_V2`. > !image-2023-08-18-13-41-31-830.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4785) AtlasClientV2 label methods use incorrect API_V2
[ https://issues.apache.org/jira/browse/ATLAS-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761694#comment-17761694 ] ASF subversion and git services commented on ATLAS-4785: Commit 530d60f0c5e9cc902e1b94d6d7f9e80995f664c0 in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=530d60f0c ] Merge pull request #237 from wForget/dev ATLAS-4785: Fix incorrect references in AtlasClientV2 label methods > AtlasClientV2 label methods use incorrect API_V2 > > > Key: ATLAS-4785 > URL: https://issues.apache.org/jira/browse/ATLAS-4785 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.3.0 >Reporter: Zhen Wang >Priority: Major > Attachments: image-2023-08-18-13-41-31-830.png > > Time Spent: 10m > Remaining Estimate: 0h > > `AtlasClientV2.addLabels` by unique attribute method and > `AtlasClientV2.setLabels` by unique attribute method use incorrect `API_V2`. > !image-2023-08-18-13-41-31-830.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4785) AtlasClientV2 label methods use incorrect API_V2
[ https://issues.apache.org/jira/browse/ATLAS-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761693#comment-17761693 ] ASF subversion and git services commented on ATLAS-4785: Commit 949cebe70a1ef105b29e08456b87a25549ad2e2a in atlas's branch refs/heads/master from wforget [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=949cebe70 ] ATLAS-4785: Fix incorrect references in AtlasClientV2 label methods > AtlasClientV2 label methods use incorrect API_V2 > > > Key: ATLAS-4785 > URL: https://issues.apache.org/jira/browse/ATLAS-4785 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.3.0 >Reporter: Zhen Wang >Priority: Major > Attachments: image-2023-08-18-13-41-31-830.png > > Time Spent: 10m > Remaining Estimate: 0h > > `AtlasClientV2.addLabels` by unique attribute method and > `AtlasClientV2.setLabels` by unique attribute method use incorrect `API_V2`. > !image-2023-08-18-13-41-31-830.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4778) BusinessMetadata string attribute value persists as prefix and suffix
[ https://issues.apache.org/jira/browse/ATLAS-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757194#comment-17757194 ] ASF subversion and git services commented on ATLAS-4778: Commit 87c0e430c7001c1678376b8dee328200c7a453b4 in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=87c0e430c ] ATLAS-4778: BusinessMetadata string attribute value persists as prefix and suffix Signed-off-by: Prasad Pawar > BusinessMetadata string attribute value persists as prefix and suffix > -- > > Key: ATLAS-4778 > URL: https://issues.apache.org/jira/browse/ATLAS-4778 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Pinal Shah >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4778-BusinessMetadata-string-attribute-value-p.patch, > string_attr.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4778) BusinessMetadata string attribute value persists as prefix and suffix
[ https://issues.apache.org/jira/browse/ATLAS-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757193#comment-17757193 ] ASF subversion and git services commented on ATLAS-4778: Commit c3d654b695823768b1b253a855898ebe6e6268bc in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c3d654b69 ] ATLAS-4778: BusinessMetadata string attribute value persists as prefix and suffix Signed-off-by: Prasad Pawar > BusinessMetadata string attribute value persists as prefix and suffix > -- > > Key: ATLAS-4778 > URL: https://issues.apache.org/jira/browse/ATLAS-4778 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Pinal Shah >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4778-BusinessMetadata-string-attribute-value-p.patch, > string_attr.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4784) Atlas - Upgrade Spring framework to 5.2.27
[ https://issues.apache.org/jira/browse/ATLAS-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755361#comment-17755361 ] ASF subversion and git services commented on ATLAS-4784: Commit 77b2a77fb08def25adeec9dd3527f14951bb7296 in atlas's branch refs/heads/branch-2.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=77b2a77fb ] ATLAS-4784 : Upgrade Spring framework to 5.2.27 Signed-off-by: Pinal Shah > Atlas - Upgrade Spring framework to 5.2.27 > -- > > Key: ATLAS-4784 > URL: https://issues.apache.org/jira/browse/ATLAS-4784 > Project: Atlas > Issue Type: Improvement >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] [Commented] (ATLAS-4784) Atlas - Upgrade Spring framework to 5.2.27
[ https://issues.apache.org/jira/browse/ATLAS-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755360#comment-17755360 ] ASF subversion and git services commented on ATLAS-4784: Commit 2452b42a47b84442f5c7eda54bedba725f61a7be in atlas's branch refs/heads/master from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2452b42a4 ] ATLAS-4784 : Upgrade Spring framework to 5.2.27 Signed-off-by: Pinal Shah > Atlas - Upgrade Spring framework to 5.2.27 > -- > > Key: ATLAS-4784 > URL: https://issues.apache.org/jira/browse/ATLAS-4784 > Project: Atlas > Issue Type: Improvement >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] [Commented] (ATLAS-4722) Atlas - Upgrade jettison to 1.5.4
[ https://issues.apache.org/jira/browse/ATLAS-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752317#comment-17752317 ] ASF subversion and git services commented on ATLAS-4722: Commit 6d9ac56410011820c43c35182ff2536c1da6279c in atlas's branch refs/heads/branch-2.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=6d9ac5641 ] ATLAS-4722 : Upgrade jettison to 1.5.4 Signed-off-by: Pinal Shah > Atlas - Upgrade jettison to 1.5.4 > - > > Key: ATLAS-4722 > URL: https://issues.apache.org/jira/browse/ATLAS-4722 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Currently atlas is using jettison version 1.3.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4781) Atlas - Upgrade Netty to 4.1.94.Final
[ https://issues.apache.org/jira/browse/ATLAS-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752316#comment-17752316 ] ASF subversion and git services commented on ATLAS-4781: Commit 12b2c3e94f31479a096fe0f40b7b8df584d4a8e7 in atlas's branch refs/heads/branch-2.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=12b2c3e94 ] ATLAS-4781 : Upgrade Netty to 4.1.94.Final Signed-off-by: Pinal Shah > Atlas - Upgrade Netty to 4.1.94.Final > - > > Key: ATLAS-4781 > URL: https://issues.apache.org/jira/browse/ATLAS-4781 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4722) Atlas - Upgrade jettison to 1.5.4
[ https://issues.apache.org/jira/browse/ATLAS-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752315#comment-17752315 ] ASF subversion and git services commented on ATLAS-4722: Commit 4155466c16eac8dee92c2c652068d1ac86f85e6a in atlas's branch refs/heads/master from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4155466c1 ] ATLAS-4722 : Upgrade jettison to 1.5.4 Signed-off-by: Pinal Shah > Atlas - Upgrade jettison to 1.5.4 > - > > Key: ATLAS-4722 > URL: https://issues.apache.org/jira/browse/ATLAS-4722 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Currently atlas is using jettison version 1.3.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4781) Atlas - Upgrade Netty to 4.1.94.Final
[ https://issues.apache.org/jira/browse/ATLAS-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752314#comment-17752314 ] ASF subversion and git services commented on ATLAS-4781: Commit 878853f1e5a9be785cd66f0a0c560ccba1759d70 in atlas's branch refs/heads/master from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=878853f1e ] ATLAS-4781 : Upgrade Netty to 4.1.94.Final Signed-off-by: Pinal Shah > Atlas - Upgrade Netty to 4.1.94.Final > - > > Key: ATLAS-4781 > URL: https://issues.apache.org/jira/browse/ATLAS-4781 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4746) hive_process and hive_process_execution (lineage) being generated for simple DML UPDATE queries run via hive
[
https://issues.apache.org/jira/browse/ATLAS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750821#comment-17750821
]
ASF subversion and git services commented on ATLAS-4746:
Commit cd1c3d02694fe60a749f0597580dd43808e3961f in atlas's branch
refs/heads/branch-2.0 from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=cd1c3d026 ]
ATLAS-4746: hive_process and hive_process_execution (lineage) being generated
for simple DML UPDATE queries run via hive
Signed-off-by: radhikakundam
(cherry picked from commit 1443f25a46784dfa63892daa74744b19b5c2a71e)
> hive_process and hive_process_execution (lineage) being generated for simple
> DML UPDATE queries run via hive
>
>
> Key: ATLAS-4746
> URL: https://issues.apache.org/jira/browse/ATLAS-4746
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.3.0
>Reporter: Umesh Padashetty
>Assignee: Radhika Kundam
>Priority: Critical
> Attachments: Screenshot 2023-05-02 at 6.28.18 PM.png, Screenshot
> 2023-05-02 at 6.28.34 PM.png, Screenshot 2023-05-02 at 6.29.05 PM.png,
> Screenshot 2023-05-02 at 6.29.10 PM.png, Screenshot 2023-05-02 at 6.47.19
> PM.png, Screenshot 2023-05-02 at 6.50.16 PM.png
>
>
> Queries ran:
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc;
> insert into test_hive_lineage_4 values ('qwer', '2');
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> As you can see, these are simple DML queries, and not DDL
> We should NOT be tracking lineage for any of the DML ({*}SELECT, INSERT,
> DELETE, and UPDATE){*} queries NOR should we be tracking the audits.
> Jiras via which DML operations audits were skipped:
> * https://issues.apache.org/jira/browse/ATLAS-3188
> * https://issues.apache.org/jira/browse/ATLAS-3198
> But all the issues were related to audits and not the lineage. In all these
> cases, lineage was not generated for the DML UPDATE query
> But observing that we are now capturing lineage for simple DML Update query
> Relationship after running
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc; {code}
> !Screenshot 2023-05-02 at 6.28.18 PM.png!
> !Screenshot 2023-05-02 at 6.28.34 PM.png!
> As seen, there is no lineage generated. Good so far
> Then I ran
> {code:java}
> insert into test_hive_lineage_4 values ('qwer', '2'); {code}
> No lineage was generated. Good so far
> !Screenshot 2023-05-02 at 6.47.19 PM.png!
> Then I ran
> {code:java}
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> This immediately generated a hive_process and a hive_process_execution
> Interestingly, hive_process with the following name was generated. As you can
> see, it has DELETE in the process name, when in reality this was an UPDATE
> DML. Another cause of concern?
> {code:java}
> QUERY:default.test_hive_lineage_4@cm:1683032252000->:DELETE:default.test_hive_lineage_4@cm:1683032252000
> {code}
> !Screenshot 2023-05-02 at 6.29.05 PM.png!
> !Screenshot 2023-05-02 at 6.29.10 PM.png!
> I then ran the same update query 100+ times, it created 100+ UNIQUE
> (timestamp delimited) hive_process_executions
> !Screenshot 2023-05-02 at 6.50.16 PM.png!
> This is a disaster since every UPDATE query now generates a
> process_execution.
> Customers can run 1000s of update queries, which are mostly of no use for
> atlas, but this issue is now leading to the generation of 1000s of
> process_executions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4746) hive_process and hive_process_execution (lineage) being generated for simple DML UPDATE queries run via hive
[
https://issues.apache.org/jira/browse/ATLAS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750820#comment-17750820
]
ASF subversion and git services commented on ATLAS-4746:
Commit 1443f25a46784dfa63892daa74744b19b5c2a71e in atlas's branch
refs/heads/master from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1443f25a4 ]
ATLAS-4746: hive_process and hive_process_execution (lineage) being generated
for simple DML UPDATE queries run via hive
Signed-off-by: radhikakundam
> hive_process and hive_process_execution (lineage) being generated for simple
> DML UPDATE queries run via hive
>
>
> Key: ATLAS-4746
> URL: https://issues.apache.org/jira/browse/ATLAS-4746
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.3.0
>Reporter: Umesh Padashetty
>Assignee: Radhika Kundam
>Priority: Critical
> Attachments: Screenshot 2023-05-02 at 6.28.18 PM.png, Screenshot
> 2023-05-02 at 6.28.34 PM.png, Screenshot 2023-05-02 at 6.29.05 PM.png,
> Screenshot 2023-05-02 at 6.29.10 PM.png, Screenshot 2023-05-02 at 6.47.19
> PM.png, Screenshot 2023-05-02 at 6.50.16 PM.png
>
>
> Queries ran:
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc;
> insert into test_hive_lineage_4 values ('qwer', '2');
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> As you can see, these are simple DML queries, and not DDL
> We should NOT be tracking lineage for any of the DML ({*}SELECT, INSERT,
> DELETE, and UPDATE){*} queries NOR should we be tracking the audits.
> Jiras via which DML operations audits were skipped:
> * https://issues.apache.org/jira/browse/ATLAS-3188
> * https://issues.apache.org/jira/browse/ATLAS-3198
> But all the issues were related to audits and not the lineage. In all these
> cases, lineage was not generated for the DML UPDATE query
> But observing that we are now capturing lineage for simple DML Update query
> Relationship after running
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc; {code}
> !Screenshot 2023-05-02 at 6.28.18 PM.png!
> !Screenshot 2023-05-02 at 6.28.34 PM.png!
> As seen, there is no lineage generated. Good so far
> Then I ran
> {code:java}
> insert into test_hive_lineage_4 values ('qwer', '2'); {code}
> No lineage was generated. Good so far
> !Screenshot 2023-05-02 at 6.47.19 PM.png!
> Then I ran
> {code:java}
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> This immediately generated a hive_process and a hive_process_execution
> Interestingly, hive_process with the following name was generated. As you can
> see, it has DELETE in the process name, when in reality this was an UPDATE
> DML. Another cause of concern?
> {code:java}
> QUERY:default.test_hive_lineage_4@cm:1683032252000->:DELETE:default.test_hive_lineage_4@cm:1683032252000
> {code}
> !Screenshot 2023-05-02 at 6.29.05 PM.png!
> !Screenshot 2023-05-02 at 6.29.10 PM.png!
> I then ran the same update query 100+ times, it created 100+ UNIQUE
> (timestamp delimited) hive_process_executions
> !Screenshot 2023-05-02 at 6.50.16 PM.png!
> This is a disaster since every UPDATE query now generates a
> process_execution.
> Customers can run 1000s of update queries, which are mostly of no use for
> atlas, but this issue is now leading to the generation of 1000s of
> process_executions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4335) Hook Notifications through Rest Interface
[ https://issues.apache.org/jira/browse/ATLAS-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750488#comment-17750488 ] ASF subversion and git services commented on ATLAS-4335: Commit f9dec5375499c8ced48c3885b690bab36a172419 in atlas's branch refs/heads/branch-2.0 from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f9dec5375 ] ATLAS-4335: Hook Notifications through Rest Interface Signed-off-by: radhikakundam (cherry picked from commit 8d8169e83ac4acfb7b152594eac96ddbc9bb8437) > Hook Notifications through Rest Interface > - > > Key: ATLAS-4335 > URL: https://issues.apache.org/jira/browse/ATLAS-4335 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Deep Singh >Assignee: Radhika Kundam >Priority: Critical > Attachments: Ordering REST based Hook Notification.pdf > > > In Data-lake <-> Workload-cluster scenario, versions of the services > available on clusters are not always the same. Especially when Kafka versions > are different on the clusters, many a time the Kafka client (on > workload-cluster) becomes incompatible with the Kafka broker (on data-lake). > This leads to failure in the delivery of Atlas Hook notification as the > mechanism is dependent on the Kafka client's capability to deliver messages. > To resolve such an issue there is no other way but to make Kafka client > compatible with the broker by upgrading or degrading the client or the > broker. Often this is not straight-fwd and the easiest thing to do. > We need another mechanism independent of the Kafka client to deliver hook > notifications to the Atlas consumer. > There are various REST API available today to perform CURD on Atlas entities. > Those APIs process notifications in real-time as they arrive, since event > processing is slow and time-consuming these APIs cannot give the throughput > which hooks require. > We need another REST interface that is lightweight and does not process > messages as they arrive instead, it could dump the messages to the local > kafka. Since Kafka will be available locally in the cluster, the interface > will never face the problem of version mismatch of client-broker, as faced by > service hooks running on a different cluster. > As publishing messages through REST notification is not instantaneous > compared to Kafka notification, we need to explicitly handle the ordering of > messages published through REST notification. Attached the document explains > the new architecture of REST Notification and how it handles out of ordered > messages. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4335) Hook Notifications through Rest Interface
[ https://issues.apache.org/jira/browse/ATLAS-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750485#comment-17750485 ] ASF subversion and git services commented on ATLAS-4335: Commit 8d8169e83ac4acfb7b152594eac96ddbc9bb8437 in atlas's branch refs/heads/master from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8d8169e83 ] ATLAS-4335: Hook Notifications through Rest Interface Signed-off-by: radhikakundam > Hook Notifications through Rest Interface > - > > Key: ATLAS-4335 > URL: https://issues.apache.org/jira/browse/ATLAS-4335 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Deep Singh >Assignee: Radhika Kundam >Priority: Critical > Attachments: Ordering REST based Hook Notification.pdf > > > In Data-lake <-> Workload-cluster scenario, versions of the services > available on clusters are not always the same. Especially when Kafka versions > are different on the clusters, many a time the Kafka client (on > workload-cluster) becomes incompatible with the Kafka broker (on data-lake). > This leads to failure in the delivery of Atlas Hook notification as the > mechanism is dependent on the Kafka client's capability to deliver messages. > To resolve such an issue there is no other way but to make Kafka client > compatible with the broker by upgrading or degrading the client or the > broker. Often this is not straight-fwd and the easiest thing to do. > We need another mechanism independent of the Kafka client to deliver hook > notifications to the Atlas consumer. > There are various REST API available today to perform CURD on Atlas entities. > Those APIs process notifications in real-time as they arrive, since event > processing is slow and time-consuming these APIs cannot give the throughput > which hooks require. > We need another REST interface that is lightweight and does not process > messages as they arrive instead, it could dump the messages to the local > kafka. Since Kafka will be available locally in the cluster, the interface > will never face the problem of version mismatch of client-broker, as faced by > service hooks running on a different cluster. > As publishing messages through REST notification is not instantaneous > compared to Kafka notification, we need to explicitly handle the ordering of > messages published through REST notification. Attached the document explains > the new architecture of REST Notification and how it handles out of ordered > messages. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4779) Build failures with svm jar conflicts due to Janusgraph upgrade to 0.6.3
[
https://issues.apache.org/jira/browse/ATLAS-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17749382#comment-17749382
]
ASF subversion and git services commented on ATLAS-4779:
Commit de5bbd37af8ff7a6292935858ffaa54884aa0ea0 in atlas's branch
refs/heads/branch-2.0 from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=de5bbd37a ]
ATLAS-4779: Build failures with svm jar conflicts due to Janusgraph upgrade to
0.6.3
(cherry picked from commit 990bbfc25c2b9e5a288827ea7f9a5e648b1122de)
> Build failures with svm jar conflicts due to Janusgraph upgrade to 0.6.3
>
>
> Key: ATLAS-4779
> URL: https://issues.apache.org/jira/browse/ATLAS-4779
> Project: Atlas
> Issue Type: Bug
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Builds are failing because of below error. This is introduced because of svm
> jar conflicts which included as part of janusgraph upgrade to 0.6.3
>
> {code:java}
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
> Suppressed: java.lang.RuntimeException: Error scanning entry
> com/oracle/svm/core/jdk17/RecordSupportJDK17OrLater.class from jar
> file:///home/jenkins/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/svm-22.3.1.jar
> at org.eclipse.jetty.annotations.AnnotationParser.lambda$parseJar$0
> (AnnotationParser.java:899) at
> java.util.TreeMap$ValueSpliterator.forEachRemaining (TreeMap.java:2897) at
> java.util.stream.ReferencePipeline$Head.forEach
> (ReferencePipeline.java:647){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4779) Build failures with svm jar conflicts due to Janusgraph upgrade to 0.6.3
[
https://issues.apache.org/jira/browse/ATLAS-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17749380#comment-17749380
]
ASF subversion and git services commented on ATLAS-4779:
Commit 990bbfc25c2b9e5a288827ea7f9a5e648b1122de in atlas's branch
refs/heads/master from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=990bbfc25 ]
ATLAS-4779: Build failures with svm jar conflicts due to Janusgraph upgrade to
0.6.3
> Build failures with svm jar conflicts due to Janusgraph upgrade to 0.6.3
>
>
> Key: ATLAS-4779
> URL: https://issues.apache.org/jira/browse/ATLAS-4779
> Project: Atlas
> Issue Type: Bug
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Builds are failing because of below error. This is introduced because of svm
> jar conflicts which included as part of janusgraph upgrade to 0.6.3
>
> {code:java}
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
> Suppressed: java.lang.RuntimeException: Error scanning entry
> com/oracle/svm/core/jdk17/RecordSupportJDK17OrLater.class from jar
> file:///home/jenkins/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/svm-22.3.1.jar
> at org.eclipse.jetty.annotations.AnnotationParser.lambda$parseJar$0
> (AnnotationParser.java:899) at
> java.util.TreeMap$ValueSpliterator.forEachRemaining (TreeMap.java:2897) at
> java.util.stream.ReferencePipeline$Head.forEach
> (ReferencePipeline.java:647){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4770) [UI] When landing on terms page from entity details page, going back lands on same page
[ https://issues.apache.org/jira/browse/ATLAS-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746205#comment-17746205 ] ASF subversion and git services commented on ATLAS-4770: Commit ef18fcf7ba3381e52aa0bb3905e0db69241c1a8e in atlas's branch refs/heads/branch-2.0 from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ef18fcf7b ] ATLAS-4770 ATLAS-4774: When landing on terms page from entity details page, going back lands on same page. Using navigation on the glossary page does not highlight the corresponding term/glossary Signed-off-by: Prasad Pawar > [UI] When landing on terms page from entity details page, going back lands on > same page > --- > > Key: ATLAS-4770 > URL: https://issues.apache.org/jira/browse/ATLAS-4770 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Abhishek Pal >Assignee: Farhan Khan >Priority: Minor > > Steps: > # In classic UI, go to any entity with an associated term, or create one if > required. > # In the entity details page, click on term to land in the term details page > # Try to go back > When going back, i.e. to the previous page, it will keep reloading the term > details page. > This is also seen if we click on the term in the search result page itself. > The behaviour is not seen if we directly go to the terms details page - in > this case it properly goes back to the previous page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4774) [UI] Using navigation on the glossary page does not highlight the corresponding term/glossary
[ https://issues.apache.org/jira/browse/ATLAS-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746206#comment-17746206 ] ASF subversion and git services commented on ATLAS-4774: Commit ef18fcf7ba3381e52aa0bb3905e0db69241c1a8e in atlas's branch refs/heads/branch-2.0 from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ef18fcf7b ] ATLAS-4770 ATLAS-4774: When landing on terms page from entity details page, going back lands on same page. Using navigation on the glossary page does not highlight the corresponding term/glossary Signed-off-by: Prasad Pawar > [UI] Using navigation on the glossary page does not highlight the > corresponding term/glossary > - > > Key: ATLAS-4774 > URL: https://issues.apache.org/jira/browse/ATLAS-4774 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4770-ATLAS-4774-When-landing-on-terms-page-fro.patch > > > Steps: > # In the classic UI, go to the glossaries tab > # Click on a glossary/term > # Click on another glossary/term > # Navigate back > Upon going back the page changes to the correct glossary/term, however the > highlighted term/glossary reflects the most recently selected term/glossary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4774) [UI] Using navigation on the glossary page does not highlight the corresponding term/glossary
[ https://issues.apache.org/jira/browse/ATLAS-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746203#comment-17746203 ] ASF subversion and git services commented on ATLAS-4774: Commit 9f013a94999a191aca2e763e8eac9d48df1e0a0f in atlas's branch refs/heads/master from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9f013a949 ] ATLAS-4770 ATLAS-4774: When landing on terms page from entity details page, going back lands on same page. Using navigation on the glossary page does not highlight the corresponding term/glossary Signed-off-by: Prasad Pawar > [UI] Using navigation on the glossary page does not highlight the > corresponding term/glossary > - > > Key: ATLAS-4774 > URL: https://issues.apache.org/jira/browse/ATLAS-4774 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4770-ATLAS-4774-When-landing-on-terms-page-fro.patch > > > Steps: > # In the classic UI, go to the glossaries tab > # Click on a glossary/term > # Click on another glossary/term > # Navigate back > Upon going back the page changes to the correct glossary/term, however the > highlighted term/glossary reflects the most recently selected term/glossary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
