[jira] [Commented] (ATLAS-4476) Atlas UI : Classification/Tag: Tag attribute name mismatch (casing issue) in "Attribute Filter" of search
[ https://issues.apache.org/jira/browse/ATLAS-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444271#comment-17444271 ] ASF subversion and git services commented on ATLAS-4476: Commit 9532e8a3e337e47af113e622010549a9a57df5b3 in atlas's branch refs/heads/branch-2.0 from prasad pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9532e8a ] ATLAS-4476:Atlas UI:#1:Classification/Tag: Tag attribute name mismatch (casing issue) in "Attribute Filter" of search Signed-off-by: Pinal Shah > Atlas UI : Classification/Tag: Tag attribute name mismatch (casing issue) in > "Attribute Filter" of search > - > > Key: ATLAS-4476 > URL: https://issues.apache.org/jira/browse/ATLAS-4476 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0, 2.3.0 >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: Atlas-UI > Attachments: > 0001-ATLAS-4476-Atlas-UI-1-Classification-Tag-Tag-attribu.patch, tag_attr.png > > > When an attribute is added to a tag as "a" it is getting reflected as "A" in > Attribute filter -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4476) Atlas UI : Classification/Tag: Tag attribute name mismatch (casing issue) in "Attribute Filter" of search
[ https://issues.apache.org/jira/browse/ATLAS-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444270#comment-17444270 ] ASF subversion and git services commented on ATLAS-4476: Commit dd0f137e80fce60bc7a9639985c540effe18b195 in atlas's branch refs/heads/master from prasad pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=dd0f137 ] ATLAS-4476:Atlas UI:#1:Classification/Tag: Tag attribute name mismatch (casing issue) in "Attribute Filter" of search Signed-off-by: Pinal Shah > Atlas UI : Classification/Tag: Tag attribute name mismatch (casing issue) in > "Attribute Filter" of search > - > > Key: ATLAS-4476 > URL: https://issues.apache.org/jira/browse/ATLAS-4476 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0, 2.3.0 >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: Atlas-UI > Attachments: > 0001-ATLAS-4476-Atlas-UI-1-Classification-Tag-Tag-attribu.patch, tag_attr.png > > > When an attribute is added to a tag as "a" it is getting reflected as "A" in > Attribute filter -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: Review Request 73700: ATLAS-4473 GlossaryTerms Bulk Create Performance Improvement
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73700/ --- (Updated Nov. 16, 2021, 4:22 a.m.) Review request for atlas, Ashutosh Mestry, Jayendra Parab, Pinal Shah, and Sarath Subramanian. Changes --- Addressed review comments Bugs: ATLAS-4473 https://issues.apache.org/jira/browse/ATLAS-4473 Repository: atlas Description --- While creating GlossaryTerms we need information about Glossary and GlossaryCategory (if present) As per current design, When every Term is created, respective Glossary and Category objects are fetched from db and they are populated with unwanted information. In case of bulk creation, Even if multiple Terms have same Glossary and Category associated with them, every time these objects are fetched from db and they are populated. This patch stores the optimum information of Glossaries and Categoies in the cache against their respective Guids. This helps in performance improvement of Bulk Term Creation. Diffs (updated) - repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java 9c8459874 repository/src/main/java/org/apache/atlas/glossary/GlossaryTermUtils.java d92daeea5 Diff: https://reviews.apache.org/r/73700/diff/2/ Changes: https://reviews.apache.org/r/73700/diff/1-2/ Testing --- Earlier, it was taking more than a day to complete the creation process of the Terms. Now with the Performacne optimization, it is taking 5 to 6 minutes to complete. Thanks, Mandar Ambawane
npm error building dashboardv2
I'm wondering if someone could help me figure out how to finish my Atlas
compile.
I'm following the build instructions here: https://github.com/apache/atlas
and using the 2.2.0 source from
https://www.apache.org/dyn/closer.cgi/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz
I had to change the buildtools version in pom.xml to 0.8.1 to make it this
far, as discovered here:
https://ducfilan.wordpress.com/2021/07/29/installing-apache-atlas-and-its-awkward/
Here's the error I'm encountering when it gets to dashboardv2:
[INFO] --- frontend-maven-plugin:1.4:npm (npm install) @ atlas-dashboardv2
---
[INFO] Running 'npm install' in
/x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target
[ERROR] internal/modules/cjs/loader.js:984
[ERROR] throw err;
[ERROR] ^
[ERROR]
[ERROR] Error: Cannot find module 'semver'
[ERROR] Require stack:
[ERROR] -
/x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/lib/utils/unsupported.js
[ERROR] -
/x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/bin/npm-cli.js
[ERROR] at Function.Module._resolveFilename
(internal/modules/cjs/loader.js:981:15)
[ERROR] at Function.Module._load
(internal/modules/cjs/loader.js:863:27)
[ERROR] at Module.require (internal/modules/cjs/loader.js:1043:19)
[ERROR] at require (internal/modules/cjs/helpers.js:77:18)
[ERROR] at Object.
(/x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/lib/utils/unsupported.js:2:14)
[ERROR] at Module._compile (internal/modules/cjs/loader.js:1157:30)
[ERROR] at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1177:10)
[ERROR] at Module.load (internal/modules/cjs/loader.js:1001:32)
[ERROR] at Function.Module._load
(internal/modules/cjs/loader.js:900:14)
[ERROR] at Module.require (internal/modules/cjs/loader.js:1043:19) {
[ERROR] code: 'MODULE_NOT_FOUND',
[ERROR] requireStack: [
[ERROR]
'/x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/lib/utils/unsupported.js',
[ERROR]
'/x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/bin/npm-cli.js'
[ERROR] ]
[ERROR] }
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Atlas Server Build Tools SUCCESS [
0.719 s]
[INFO] apache-atlas 2.2.0 . SUCCESS [
5.147 s]
[INFO] Apache Atlas Integration ... SUCCESS [
20.095 s]
[INFO] Apache Atlas Test Utility Tools SUCCESS [
8.901 s]
[INFO] Apache Atlas Common SUCCESS [
9.003 s]
[INFO] Apache Atlas Client SUCCESS [
0.358 s]
[INFO] atlas-client-common SUCCESS [
4.538 s]
[INFO] atlas-client-v1 SUCCESS [
5.281 s]
[INFO] Apache Atlas Server API SUCCESS [
6.837 s]
[INFO] Apache Atlas Notification .. SUCCESS [
11.072 s]
[INFO] atlas-client-v2 SUCCESS [
4.899 s]
[INFO] Apache Atlas Graph Database Projects ... SUCCESS [
0.356 s]
[INFO] Apache Atlas Graph Database API SUCCESS [
4.534 s]
[INFO] Graph Database Common Code . SUCCESS [
3.700 s]
[INFO] Apache Atlas JanusGraph-HBase2 Module .. SUCCESS [
5.433 s]
[INFO] Apache Atlas JanusGraph DB Impl SUCCESS [
14.073 s]
[INFO] Apache Atlas Graph DB Dependencies . SUCCESS [
1.375 s]
[INFO] Apache Atlas Authorization . SUCCESS [
7.535 s]
[INFO] Apache Atlas Repository SUCCESS [
34.258 s]
[INFO] Apache Atlas UI FAILURE [
13.342 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
[jira] [Commented] (ATLAS-4479) ApplicationProperties cause NPE when using Elasticsearch
[
https://issues.apache.org/jira/browse/ATLAS-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444230#comment-17444230
]
wuzhiguo commented on ATLAS-4479:
-
thanks
> ApplicationProperties cause NPE when using Elasticsearch
>
>
> Key: ATLAS-4479
> URL: https://issues.apache.org/jira/browse/ATLAS-4479
> Project: Atlas
> Issue Type: Bug
>Reporter: wuzhiguo
>Priority: Major
>
> code in line 367: `LOG.info("Setting " + SOLR_WAIT_SEARCHER_CONF + " = " +
> getBoolean(SOLR_WAIT_SEARCHER_CONF));` will cause NPE when using
> elasticsearch, which should not, cause the configuration belongs to solr
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ATLAS-4246) Make Kafka Interface aware of Kafka Schema Registry
[ https://issues.apache.org/jira/browse/ATLAS-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444056#comment-17444056 ] ASF subversion and git services commented on ATLAS-4246: Commit 7871d9e1a6efe6875b6d4da9326cefa31ea20c0e in atlas's branch refs/heads/branch-2.0 from Aileen Toleikis [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7871d9e ] ATLAS-4246: Make Kafka Interface aware of Kafka Schema Registry Signed-off-by: Sidharth Mishra (cherry picked from commit b4ee37b6d850baa0803deb39652e6f4ff6d665e7) > Make Kafka Interface aware of Kafka Schema Registry > --- > > Key: ATLAS-4246 > URL: https://issues.apache.org/jira/browse/ATLAS-4246 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0, 3.0.0 >Reporter: Aileen Toleikis >Assignee: Viktor Somogyi-Vass >Priority: Major > Labels: Kafka > Fix For: 3.0.0, 2.3.0 > > > Kafka Community is using Schema Registry more and more heavily but as Atlas > is currently unaware of this, this extension helps Atlas make use of the > Schemas. > > We have tested this extension and we have production environments where Atlas > will not be allowed without schema registry access. We have received feedback > that this extension would be sufficient to allow production use. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4246) Make Kafka Interface aware of Kafka Schema Registry
[ https://issues.apache.org/jira/browse/ATLAS-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444054#comment-17444054 ] ASF subversion and git services commented on ATLAS-4246: Commit b4ee37b6d850baa0803deb39652e6f4ff6d665e7 in atlas's branch refs/heads/master from Aileen Toleikis [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b4ee37b ] ATLAS-4246: Make Kafka Interface aware of Kafka Schema Registry Signed-off-by: Sidharth Mishra > Make Kafka Interface aware of Kafka Schema Registry > --- > > Key: ATLAS-4246 > URL: https://issues.apache.org/jira/browse/ATLAS-4246 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0, 3.0.0 >Reporter: Aileen Toleikis >Assignee: Viktor Somogyi-Vass >Priority: Major > Labels: Kafka > Fix For: 3.0.0, 2.3.0 > > > Kafka Community is using Schema Registry more and more heavily but as Atlas > is currently unaware of this, this extension helps Atlas make use of the > Schemas. > > We have tested this extension and we have production environments where Atlas > will not be allowed without schema registry access. We have received feedback > that this extension would be sufficient to allow production use. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4479) ApplicationProperties cause NPE when using Elasticsearch
[
https://issues.apache.org/jira/browse/ATLAS-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444001#comment-17444001
]
Ashutosh Mestry commented on ATLAS-4479:
I have approved the PR.
> ApplicationProperties cause NPE when using Elasticsearch
>
>
> Key: ATLAS-4479
> URL: https://issues.apache.org/jira/browse/ATLAS-4479
> Project: Atlas
> Issue Type: Bug
>Reporter: wuzhiguo
>Priority: Major
>
> code in line 367: `LOG.info("Setting " + SOLR_WAIT_SEARCHER_CONF + " = " +
> getBoolean(SOLR_WAIT_SEARCHER_CONF));` will cause NPE when using
> elasticsearch, which should not, cause the configuration belongs to solr
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ATLAS-4246) Make Kafka Interface aware of Kafka Schema Registry
[ https://issues.apache.org/jira/browse/ATLAS-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443956#comment-17443956 ] Aileen Toleikis commented on ATLAS-4246: Hi [~sidharthkmishra] [~sarath] [~amestry] , we uploaded the patch again and added the details you described in the message. Is this okay? Kind regards, Aileen > Make Kafka Interface aware of Kafka Schema Registry > --- > > Key: ATLAS-4246 > URL: https://issues.apache.org/jira/browse/ATLAS-4246 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Affects Versions: 2.1.0, 3.0.0 >Reporter: Aileen Toleikis >Assignee: Viktor Somogyi-Vass >Priority: Major > Labels: Kafka > Fix For: 3.0.0, 2.3.0 > > > Kafka Community is using Schema Registry more and more heavily but as Atlas > is currently unaware of this, this extension helps Atlas make use of the > Schemas. > > We have tested this extension and we have production environments where Atlas > will not be allowed without schema registry access. We have received feedback > that this extension would be sufficient to allow production use. -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: Review Request 73286: Initial commit
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73286/ --- (Updated Nov. 15, 2021, 4:59 nachm.) Review request for atlas. Changes --- From: aileen.tolei...@hpe.com Date: 15.Nov.2021 Subject: Make Kafka Interface aware of Kafka Schema Registry Recent successful CI build - https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/956/ Repository: atlas Description --- The Kafka Community is using Schema Registry more and more heavily but as Atlas is currently unaware of this, this extension helps Atlas make use of the Schemas. We have tested this extension and we have production environments where Atlas will not be allowed without schema registry access. We have received feedback that this extension would be sufficient to allow production use. Changes: initial commit added schema creation in Atlas added Schema creation, Schema linkage and started to work on versions avro_field creation is working. However, there is no connection to schemas yet smaller refactorings and improved logging added field reference in schemas deleted second README and added gitignore Smaller changes after rebasing on new version moved HTTP REST calls to a separate class (SchemaRegistryConnector.java) added testCreateSchema() as test case added testCreateField() and testUpdateField() as test case added testGetSchemas() and testGetSchemaVersions() as test case added testUpdateSchema() as test case removed unnecessary comments Diffs (updated) - addons/kafka-bridge/pom.xml 2ac19fd20e0c0322b0d104641ddd5a2ef89bf9d0 addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/bridge/KafkaBridge.java f9548244364a8f79f346411739348d0d53298c99 addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/bridge/SchemaRegistryConnector.java PRE-CREATION addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/model/KafkaDataTypes.java 0f81b4c37a1d8f84c587a914eb460b290ae36987 addons/kafka-bridge/src/test/java/org/apache/atlas/kafka/bridge/KafkaBridgeTest.java f86ceb58fd250d80f3ae3c71085c8c0adbc9116b pom.xml 47768e9fa7d8abcfc81cd148917400ac478a333a Diff: https://reviews.apache.org/r/73286/diff/6/ Changes: https://reviews.apache.org/r/73286/diff/5-6/ Testing --- Thanks, Aileen Toleikis
Re: Review Request 73637: ATLAS-4370: Persist Metrics for user to retrieve Metrics info at a past timestamp
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73637/ --- (Updated Nov. 15, 2021, 4:06 p.m.) Review request for atlas, Ashutosh Mestry, Radhika Kundam, Sarath Subramanian, and Sidharth Mishra. Changes --- 1. Removed duplicate "__AtlasMetricsStat" 2. Single entry and exit debug logs in "scheduleSaveAndDeleteMetrics()" 3. Moved private methods after public Bugs: ATLAS-4370 https://issues.apache.org/jira/browse/ATLAS-4370 Repository: atlas Description --- Rebased patch #73483 (https://reviews.apache.org/r/73483/) against the newest master branch. Diffs (updated) - addons/models/-Area0/0010-base_model.json 769d8859f intg/src/main/java/org/apache/atlas/AtlasConfiguration.java b63fab7cf intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 7d092616d intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMapToChart.java PRE-CREATION intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsStat.java PRE-CREATION intg/src/main/java/org/apache/atlas/utils/AtlasEntityUtil.java 1e78e2550 repository/src/main/java/org/apache/atlas/repository/ogm/metrics/AtlasMetricsStatDTO.java PRE-CREATION repository/src/main/java/org/apache/atlas/services/MetricsService.java ceb252822 repository/src/test/java/org/apache/atlas/TestModules.java 8dda20825 repository/src/test/java/org/apache/atlas/services/MetricsServiceTest.java 040592184 test-tools/src/main/resources/solr/core-template/solrconfig.xml 3341e7199 webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 0580f7f33 Diff: https://reviews.apache.org/r/73637/diff/7/ Changes: https://reviews.apache.org/r/73637/diff/6-7/ Testing --- 1) Tested locally. 2) Patched a cluster. PC build: https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/880/ Thanks, Disha Talreja
[jira] [Created] (ATLAS-4480) [API] Observing slowness in rest api response
Dharshana M Krishnamoorthy created ATLAS-4480:
-
Summary: [API] Observing slowness in rest api response
Key: ATLAS-4480
URL: https://issues.apache.org/jira/browse/ATLAS-4480
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Dharshana M Krishnamoorthy
Attachments: Screenshot 2021-11-15 at 3.51.10 PM.png
Observing slowness in the api response
Eg: Scenario
# Create a entity
# Soft delete it
# Purge the entity
# Verify purge audit
Here we fire a admin api call immediately after the entity is purged
But the admin api response is empty []
If we query after some time, we can see the audit is present for the purge call
!Screenshot 2021-11-15 at 3.51.10 PM.png|width=377,height=180!
Logs showing the above steps
{code:java}
2021-11-12 10:34:17,702|INFO|MainThread|atlasv2.py:659 -
get_entity_def()|https://quasar-gmxrxz-2.quasar-gmxrxz.root.hwx.site:31443/api/atlas/v2/entity/guid/e15aeb8e-cfb2-4b9d-96f1-b9bce94586e4
2021-11-12 10:34:17,703|INFO|MainThread|atlas.py:1135 -
http_get_request()|https://quasar-gmxrxz-2.quasar-gmxrxz.root.hwx.site:31443/api/atlas/v2/entity/guid/e15aeb8e-cfb2-4b9d-96f1-b9bce94586e4
2021-11-12 10:34:17,703|INFO|MainThread|atlas.py:1202 -
http_request()|https://quasar-gmxrxz-2.quasar-gmxrxz.root.hwx.site:31443/api/atlas/v2/entity/guid/e15aeb8e-cfb2-4b9d-96f1-b9bce94586e4
2021-11-12 10:34:17,704|INFO|MainThread|atlas.py:1209 - http_request()|HTTP
Method: GET, Body: None
2021-11-12 10:34:17,705|INFO|MainThread|atlas.py:1238 - http_request()|Making
HTTP requests via Kerberos auth
2021-11-12 10:34:17,787|INFO|MainThread|atlas.py:1257 - http_request()|HTTP
response code: 200
2021-11-12 10:34:17,790|INFO|MainThread|atlas.py:807 - set_base_url()|Base url:
https://quasar-gmxrxz-2.quasar-gmxrxz.root.hwx.site:31443
2021-11-12 10:34:17,791|INFO|MainThread|atlas.py:1202 -
http_request()|https://quasar-gmxrxz-2.quasar-gmxrxz.root.hwx.site:31443/api/atlas/admin/purge
2021-11-12 10:34:17,791|INFO|MainThread|atlas.py:1209 - http_request()|HTTP
Method: PUT, Body: ["e15aeb8e-cfb2-4b9d-96f1-b9bce94586e4"]
2021-11-12 10:34:17,792|INFO|MainThread|atlas.py:1238 - http_request()|Making
HTTP requests via Kerberos auth
2021-11-12 10:34:18,184|INFO|MainThread|atlas.py:1257 - http_request()|HTTP
response code: 200
2021-11-12 10:34:18,186|INFO|MainThread|utils.py:18 -
purge_entity_and_verify_status()|{u'mutatedEntities': {u'PURGE': [{u'status':
u'DELETED', u'isIncomplete': False, u'guid':
u'9c9d8fc0-3f81-4d24-987f-60172e776d84', u'classifications': [], u'labels': [],
u'typeName': u'hive_column', u'meaningNames': [], u'displayText': u'id',
u'meanings': [], u'attributes': {u'owner': u'hrt_qa', u'qualifiedName':
u'default.table_lxjgr.id@cm', u'name': u'id'}, u'classificationNames': []},
{u'status': u'DELETED', u'isIncomplete': False, u'guid':
u'6c7b8038-3c46-4d25-9ef3-c4bdb7ddb5a3', u'classifications': [], u'labels': [],
u'typeName': u'hive_column', u'meaningNames': [], u'displayText': u'name',
u'meanings': [], u'attributes': {u'owner': u'hrt_qa', u'qualifiedName':
u'default.table_lxjgr.name@cm', u'name': u'name'}, u'classificationNames': []},
{u'status': u'DELETED', u'isIncomplete': False, u'guid':
u'e15aeb8e-cfb2-4b9d-96f1-b9bce94586e4', u'classifications': [], u'labels': [],
u'typeName': u'hive_table', u'meaningNames': [], u'displayText':
u'table_lxjgr', u'meanings': [], u'attributes': {u'owner': u'hrt_qa',
u'qualifiedName': u'default.table_lxjgr@cm', u'createTime': 1636713248000,
u'name': u'table_lxjgr'}, u'classificationNames': []}, {u'status': u'DELETED',
u'isIncomplete': False, u'guid': u'6132f1b4-6efb-45af-8ec2-70f197aa16c2',
u'classifications': [], u'labels': [], u'typeName': u'hive_storagedesc',
u'meaningNames': [], u'displayText': u'default.table_lxjgr@cm_storage',
u'meanings': [], u'attributes': {u'qualifiedName':
u'default.table_lxjgr@cm_storage'}, u'classificationNames': []}, {u'status':
u'DELETED', u'isIncomplete': False, u'guid':
u'0354d287-c598-4325-b0ec-d48dfaf6fd9a', u'classifications': [], u'labels': [],
u'typeName': u'hive_table_ddl', u'meaningNames': [], u'displayText':
u'default.table_lxjgr@cm:1636713248787', u'meanings': [], u'attributes':
{u'qualifiedName': u'default.table_lxjgr@cm:1636713248787'},
u'classificationNames': []}]}}
2021-11-12 10:34:18,186|INFO|MainThread|utils.py:72 -
purge_async_deleted_entities()|{u'mutatedEntities': {u'PURGE': [{u'status':
u'DELETED', u'isIncomplete': False, u'guid':
u'9c9d8fc0-3f81-4d24-987f-60172e776d84', u'classifications': [], u'labels': [],
u'typeName': u'hive_column', u'meaningNames': [], u'displayText': u'id',
u'meanings': [], u'attributes': {u'owner': u'hrt_qa', u'qualifiedName':
u'default.table_lxjgr.id@cm', u'name': u'id'}, u'classificationNames': []},
{u'status': u'DELETED', u'isIncomplete': False, u'guid':
[jira] [Commented] (ATLAS-4479) ApplicationProperties cause NPE when using Elasticsearch
[
https://issues.apache.org/jira/browse/ATLAS-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443634#comment-17443634
]
wuzhiguo commented on ATLAS-4479:
-
https://github.com/apache/atlas/pull/152
> ApplicationProperties cause NPE when using Elasticsearch
>
>
> Key: ATLAS-4479
> URL: https://issues.apache.org/jira/browse/ATLAS-4479
> Project: Atlas
> Issue Type: Bug
>Reporter: wuzhiguo
>Priority: Major
>
> code in line 367: `LOG.info("Setting " + SOLR_WAIT_SEARCHER_CONF + " = " +
> getBoolean(SOLR_WAIT_SEARCHER_CONF));` will cause NPE when using
> elasticsearch, which should not, cause the configuration belongs to solr
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ATLAS-4479) ApplicationProperties cause NPE when using Elasticsearch
wuzhiguo created ATLAS-4479:
---
Summary: ApplicationProperties cause NPE when using Elasticsearch
Key: ATLAS-4479
URL: https://issues.apache.org/jira/browse/ATLAS-4479
Project: Atlas
Issue Type: Bug
Reporter: wuzhiguo
code in line 367: `LOG.info("Setting " + SOLR_WAIT_SEARCHER_CONF + " = " +
getBoolean(SOLR_WAIT_SEARCHER_CONF));` will cause NPE when using elasticsearch,
which should not, cause the configuration belongs to solr
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [atlas] kevinw66 opened a new pull request #152: Fix NPE when using Elasticsearch
kevinw66 opened a new pull request #152: URL: https://github.com/apache/atlas/pull/152 When using elasticsearch, if the `atlas.graph.index.search.solr.wait-searcher` is not configured, it will produce NullPointerException -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
