[jira] [Commented] (ATLAS-4712) atlas-hive image shows "No such file or directory error"
[
https://issues.apache.org/jira/browse/ATLAS-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635969#comment-17635969
]
Sidharth Kumar Mishra commented on ATLAS-4712:
--
+1 for Patch. Thanks [~madhan]
> atlas-hive image shows "No such file or directory error"
> -
>
> Key: ATLAS-4712
> URL: https://issues.apache.org/jira/browse/ATLAS-4712
> Project: Atlas
> Issue Type: Bug
>Reporter: Snehal Ambavkar
>Assignee: Madhan Neethiraj
>Priority: Minor
> Fix For: 3.0.0, 2.3.0
>
> Attachments: ATLAS-4712.patch
>
>
> Running docker-compose
> {code:java}
> docker-compose -f docker-compose.atlas-base.yml -f docker-compose.atlas.yml
> -f docker-compose.atlas-hadoop.yml -f docker-compose.atlas-hbase.yml -f
> docker-compose.atlas-kafka.yml -f docker-compose.atlas-hive.yml up -d
> {code}
> shows with:
> {code:java}
> /home/atlas/scripts/atlas-hive-setup.sh: line 44: cd:
> /opt/atlas/atlas-hive-plugin: No such file or directory
> /home/atlas/scripts/atlas-hive-setup.sh: line 45: ./enable-hive-plugin.sh: No
> such file or directory {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4548) Set Empty attribute value for queryStr and queryId in case of null value when atlas.hook.hive.hive_process.populate.deprecated.attributes=true
Sidharth Kumar Mishra created ATLAS-4548:
Summary: Set Empty attribute value for queryStr and queryId in
case of null value when
atlas.hook.hive.hive_process.populate.deprecated.attributes=true
Key: ATLAS-4548
URL: https://issues.apache.org/jira/browse/ATLAS-4548
Project: Atlas
Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra
As part of https://issues.apache.org/jira/browse/ATLAS-3606 by default we have
made the userName, queryId and queryText for hive_process deprecated and we
don't get these attribute values for some of the queries from Hive context. For
example creating external table query below we don't get queryText and queryId
from hive context and we can't populate either. If you mark the flag
"atlas.hook.hive.hive_process.populate.deprecated.attributes=true" then it will
cause problems in this case as hive context has null value and Atlas expects
some value to be present.
Repro steps:
--
First set "atlas.hook.hive.hive_process.populate.deprecated.attributes=true".
Then "beeline -e 'create external table csaba_table_3(msg string);'"
Check Atlas log:
{noformat}
2022-01-26 12:26:44,950 ERROR - [NotificationHookConsumer thread-0:] ~ graph
rollback due to exception AtlasBaseException:Invalid instance creation/updation
parameters passed : hive_process.queryText: mandatory attribute value missing
in type hive_process (GraphTransactionInterceptor:202)
2022-01-26 12:26:44,951 WARN - [NotificationHookConsumer thread-0:] ~ Max
retries exceeded for message
{"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgCreationTime":164324951,"spooled":false,"message":{"type":"ENTITY_CREATE_V2","user":"hive","entities":{"referredEntities":{"-30336865853165805":{"typeName":"hive_storagedesc","attributes":{"qualifiedName":"default.csaba_table_3@cm_storage","storedAsSubDirectories":false,"location":"hdfs://ns1/warehouse/tablespace/external/hive/csaba_table_3","compressed":false,"inputFormat":"org.apache.hadoop.mapred.TextInputFormat","parameters":{},"outputFormat":"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat","serdeInfo":{"typeName":"hive_serde","attributes":{"serializationLib":"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe","name":null,"parameters":{"serialization.format":"1"}}},"numBuckets":-1},"guid":"-30336865853165805","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"table":{"guid":"-30336865853165804","typeName":"hive_table","uniqueAttributes":{"qualifiedName":"default.csaba_table_3@cm"},"relationshipType":"hive_table_storagedesc"}},"proxy":false},"-30336865853165806":{"typeName":"hive_column","attributes":{"owner":"hrt_qa","qualifiedName":"default.csaba_table_3.msg@cm","name":"msg","comment":null,"position":0,"type":"string"},"guid":"-30336865853165806","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"table":{"guid":"-30336865853165804","typeName":"hive_table","uniqueAttributes":{"qualifiedName":"default.csaba_table_3@cm"},"relationshipType":"hive_table_columns"}},"proxy":false},"-30336865853165807":{"typeName":"hdfs_path","attributes":{"nameServiceId":"ns1","path":"hdfs://ns1/warehouse/tablespace/external/hive/csaba_table_3","qualifiedName":"hdfs://ns1/warehouse/tablespace/external/hive/csaba_table_3@cm","clusterName":"cm","name":"/warehouse/tablespace/external/hive/csaba_table_3"},"guid":"-30336865853165807","isIncomplete":false,"provenanceType":0,"version":0,"proxy":false}},"entities":[{"typeName":"hive_table","attributes":{"owner":"hrt_qa","tableType":"EXTERNAL_TABLE","temporary":false,"lastAccessTime":164323000,"createTime":164323000,"qualifiedName":"default.csaba_table_3@cm","name":"csaba_table_3","comment":null,"parameters":{"totalSize":"0","EXTERNAL":"TRUE","numRows":"0","rawDataSize":"0","COLUMN_STATS_ACCURATE":"{\"BASIC_STATS\":\"true\",\"COLUMN_STATS\":{\"msg\":\"true\"}}","numFiles":"0","transient_lastDdlTime":"164323","bucketing_version":"2","numFilesErasureCoded":"0"},"retention":0},"guid":"-30336865853165804","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"sd":{"guid":"-30336865853165805","typeName":"hive_storagedesc","uniqueAttributes":{"qualifiedName":"default.csaba_table_3@cm_storage"},"relationshipType":"hive_table_storagedesc"},"columns":[{"guid":"-30336865853165806","typeName":"hive_column","uniqueAttributes":{"qualifiedName":"default.csaba_table_3.msg@cm"},"relationshipType":"hive_table_columns"}],"partitionKeys":[],"db":{"typeName":"hive_db","uniqueAttributes":{"qualifiedName":"default@cm"},"relationshipType":"hive_table_db"}},"proxy":false},{"typeName":"hive_process","attributes":{"recentQueries":[null],"qualifiedName":"default.csaba_table_3@cm:164323000","clusterName":"cm","name":"default.csaba_tabl
[jira] [Assigned] (ATLAS-3985) Not able to assign classification with mandatory attribute of type "array"
[
https://issues.apache.org/jira/browse/ATLAS-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-3985:
Assignee: Sidharth Kumar Mishra
> Not able to assign classification with mandatory attribute of type
> "array"
> ---
>
> Key: ATLAS-3985
> URL: https://issues.apache.org/jira/browse/ATLAS-3985
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2020-10-07 at 1.40.43 PM.png, Screenshot
> 2020-10-07 at 1.41.17 PM.png
>
>
> Create a classification that has mandatory attribute of type
> "*array*" via REST api
> {code:java|title=Create classification with payload:}
> {
> "enumDefs": [],
> "structDefs": [],
> "classificationDefs": [
> {
> "category": "CLASSIFICATION",
> "guid": "8996315b-b5fe-48c6-b9d0-4668fhkfd21af",
> "createdBy": "hrt_qa",
> "updatedBy": "hrt_qa",
> "createTime": 1602057743077,
> "updateTime": 1602057743077,
> "version": 1,
> "name": "read_auth_test_tag1",
> "description": "read_auth_test_tag1",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "type_long_min",
> "typeName": "long",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name":"type_arr_list",
> "typeName":"array",
> "isOptional":false,
> "cardinality":"LIST",
> "valuesMinCount":1,
> "valuesMaxCount":2147483647,
> "isUnique":false,
> "isIndexable":false
> },
> {
> "name":"type_set",
> "typeName":"array",
> "isOptional":false,
> "cardinality":"SET",
> "valuesMinCount":1,
> "valuesMaxCount":2147483647,
> "isUnique":false,
> "isIndexable":false
> }
> ],
> "superTypes": [],
> "entityTypes": [],
> "subTypes": []
> }
> ],
> "entityDefs": [],
> "relationshipDefs": [],
> "businessMetadataDefs": []
> }
> {code}
> Assign the same to an entity.
> The assignment fails as the attributes of type "array" are not
> visible on UI
> {code:java|title=error message}
> {"errorCode":"ATLAS-400-00-01A",
> "errorMessage":"invalid parameters: read_auth_test_tag1.type_arr_list:
> mandatory attribute value missing in type read_auth_test_tag1"}
> {code}
>
> The assignment fails via both UI and rest api.
> In UI creation of attribute of such a type is not allowed but via rest api it
> is possible.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ATLAS-4508) Though a particular tag is blocked propagation , tag is still propagated
Sidharth Kumar Mishra created ATLAS-4508:
Summary: Though a particular tag is blocked propagation , tag is
still propagated
Key: ATLAS-4508
URL: https://issues.apache.org/jira/browse/ATLAS-4508
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra
If we do the operation like Add classification and remove concurrently or Add
classification and block the same classification concurrently then most likely
due to deferred action we are hitting issue at Atlas and the Add/Remove/Block
is not working as expected. Example of Add and block happening concurrently
where the block is not working as expected:
{code:java}
2021-12-12 10:59:36,145 INFO -
[etp1330247343-177:hrt_qa:POST/api/atlas/v2/entity/bulk/classification] ~
Request from authenticated user: hrt_qa,
URL=/api/atlas/v2/entity/bulk/classification
(AtlasAuthenticationFilter$KerberosFilterChainWrapper:800)
2021-12-12 10:59:36,170 INFO - [etp1330247343-177 -
15c26538-375e-4352-b27e-34caf1d4a6f7:hrt_qa:POST/api/atlas/v2/entity/bulk/classification]
~ updateClassificationText: tag_zxpzn: tag_emufo_0 tag_qxnez tag_crqpn_0
tag_xldqo tag_xjdig tag_ksgxh tag_dpzcq tag_vszhd tag_zxpzn tag_crqpn_1
tag_crqpn_2 tag_hzjqk tag_tafen date Sun Dec 12 10:55:20 UTC 2021
hive_principal_type USER boolean false string nJzsc byte -21 double
1.2633179028830385E38 arr_string dYfsL mKlVp iCOwp ssfum iAaGF kcJWp dWxpm
VFsqP hYbVs short 24586 arr_int 476972899 729046663 1927464331 499332336
233258034 -670732418 -1304702956 205121029 float 1.54E38 int 1233345212 long
7716583360736583680 tag_ywwov date Thu Jan 01 00:00:00 UTC 1970 boolean false
byte 0 double 0.0 short 0 float 0.0 int 0 long 0 (EntityGraphMapper:2769)
2021-12-12 10:59:36,325 INFO - [etp1330247343-177 -
15c26538-375e-4352-b27e-34caf1d4a6f7:hrt_qa:POST/api/atlas/v2/entity/bulk/classification]
~
{"type":"CLASSIFICATION_PROPAGATION_ADD","guid":"32961799-d7e5-4aa1-a7b1-9172920f430b","createdBy":"hrt_qa","createdTime":1639306776164,"updatedTime":1639306776164,"parameters":{"relationshipGuid":null,"entityGuid":"b20848ce-4e8d-41d9-abdb-d0a846166e9e","classificationVertexId":"40972512"},"attemptCount":0,"status":"PENDING"}
(TaskExecutor$TaskLogger:170)
2021-12-12 10:59:36,368 INFO - [etp1330247343-570:] ~ Logged into Atlas as =
hrt_qa (AtlasAuthenticationFilter$KerberosFilterChainWrapper:787)
.
2021-12-12 10:59:37,068 INFO - [etp1330247343-570 -
1b14bb3f-face-40f3-b4a4-cbac281ed685:hrt_qa:PUT/api/atlas/v2/relationship] ~
{"type":"CLASSIFICATION_PROPAGATION_RELATIONSHIP_UPDATE","guid":"9b36fa74-46e8-4bd4-9abc-2865354d0d46","createdBy":"hrt_qa","createdTime":1639306776679,"updatedTime":1639306776679,"parameters":{"relationshipEdgeId":"osjyc-okbog-4e1h-3v7k","relationshipObject":"{\"typeName\":\"dataset_process_inputs\",\"guid\":\"a2f03e60-d677-473b-ada5-dd77b21dc149\",\"provenanceType\":0,\"end1\":{\"guid\":\"3e9b2e57-1e32-4692-ac7a-a617ea0c4648\",\"typeName\":\"hive_process\",\"uniqueAttributes\":{\"qualifiedName\":\"default.table_xluwf_2@cm:1639305904000\"}},\"end2\":{\"guid\":\"b20848ce-4e8d-41d9-abdb-d0a846166e9e\",\"typeName\":\"hive_table\",\"uniqueAttributes\":{\"qualifiedName\":\"default.table_xluwf_1@cm\"}},\"label\":\"__Process.inputs\",\"propagateTags\":\"TWO_TO_ONE\",\"status\":\"ACTIVE\",\"createdBy\":\"hrt_qa\",\"updatedBy\":\"hrt_qa\",\"createTime\":1639305904397,\"updateTime\":1639305904397,\"version\":0,\"propagatedClassifications\":[{\"typeName\":\"tag_qxnez\",\"entityGuid\":\"b20848ce-4e8d-41d9-abdb-d0a846166e9e\",\"entityStatus\":\"ACTIVE\",\"propagate\":true,\"removePropagationsOnEntityDelete\":false},{\"typeName\":\"tag_crqpn_1\",\"entityGuid\":\"b20848ce-4e8d-41d9-abdb-d0a846166e9e\",\"entityStatus\":\"ACTIVE\",\"propagate\":true,\"removePropagationsOnEntityDelete\":false},{\"typeName\":\"tag_ksgxh\",\"entityGuid\":\"b20848ce-4e8d-41d9-abdb-d0a846166e9e\",\"entityStatus\":\"ACTIVE\",\"propagate\":true,\"removePropagationsOnEntityDelete\":false},{\"typeName\":\"tag_tafen\",\"attributes\":{\"short\":24586,\"string\":\"nJzsc\",\"boolean\":false,\"double\":1.2633179028830385E+38,\"float\":1.54E+38,\"arr_string\":[\"dYfsL\",\"mKlVp\",\"iCOwp\",\"ssfum\",\"iAaGF\",\"kcJWp\",\"dWxpm\",\"VFsqP\",\"hYbVs\"],\"long\":7716583360736583680,\"arr_int\":[476972899,729046663,1927464331,499332336,233258034,-670732418,-1304702956,205121029],\"int\":1233345212,\"hive_principal_type\":\"USER\",\"date\":1639306520089,\"byte\":-21},\"entityGuid\":\"b20848ce-4e8d-41d9-abdb-d0a846166e9e\",\"entityStatus\":\"ACTIVE\",\"propagate\":true,\"removePropagationsOnEntityDelete\":false},{\"typeName\":\"tag_crqpn_0\",\"entityGuid\":\"b20848ce-4e8d-41d9-abdb-d0a846166e9e\",\"entityStatus\":\"ACTIVE\",\"propagate\":true,\"removePropagationsOnEntityDelete\":false},{\"typeName\":\"tag_ywwo
[jira] [Resolved] (ATLAS-4492) Atlas to skip external temporary table created in hive
[
https://issues.apache.org/jira/browse/ATLAS-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4492.
--
Resolution: Fixed
> Atlas to skip external temporary table created in hive
> --
>
> Key: ATLAS-4492
> URL: https://issues.apache.org/jira/browse/ATLAS-4492
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> As per the current design, skip temp tables feature in Atlas will skip
> creating temporary tables only if that temp table is {*}not external{*}. *New
> requirement is to skip creating external temp tables also.*
> Introducing new config property *skip.all.temp.tables* which can be used to
> skip all temp tables {*}irrespective of external or not{*}.
> With this fix in Atlas two options will be available.
> atlas.hook.hive.skip.temp.tables => which works same as earlier, skipping
> non-external temporary table creation and it is enabled in Atlas by default.
> atlas.hook.hive.skip.all.temp.tables => which skips all temporary tables
> irrespective of external or not
> To skip all the temporary tables user has to configure the property as below.
> atlas.hook.hive.skip.all.temp.tables=true
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ATLAS-4502) Add cassandra and elasticsearch search profile for Atlas
Sidharth Kumar Mishra created ATLAS-4502: Summary: Add cassandra and elasticsearch search profile for Atlas Key: ATLAS-4502 URL: https://issues.apache.org/jira/browse/ATLAS-4502 Project: Atlas Issue Type: New Feature Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4487) User having import and export privilege is failing with status 403
Sidharth Kumar Mishra created ATLAS-4487:
Summary: User having import and export privilege is failing with
status 403
Key: ATLAS-4487
URL: https://issues.apache.org/jira/browse/ATLAS-4487
Project: Atlas
Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra
org.apache.atlas.AtlasServiceException: Metadata service API
org.apache.atlas.AtlasBaseClient$API@3fb9a67f failed with status 403
(Forbidden) Response Body
(\{"errorCode":"ATLAS-403-00-001","errorMessage":"hive is not authorized to
perform create entity: type=__AtlasAuditEntry"})
at
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:448)
at
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:366)
at
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:352)
at org.apache.atlas.AtlasBaseClient.callAPI(AtlasBaseClient.java:228)
at
org.apache.atlas.AtlasBaseClient.performImportData(AtlasBaseClient.java:551)
at org.apache.atlas.AtlasBaseClient.importData(AtlasBaseClient.java:537)
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridgeV2.runAtlasImport(HiveMetaStoreBridgeV2.java:558)
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridgeV2.exportDataToZipAndRunAtlasImport(HiveMetaStoreBridgeV2.java:200)
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:180)
Exception details from Application.log:
{code:java}
2021-11-19 20:43:09,128 ERROR - [etp221634215-236 -
a445a639-7068-4f80-ad08-541e7be3dd4d:hive:POST/api/atlas/admin/import] ~ graph
rollback due to exception (GraphTransactionInterceptor:200)
org.apache.atlas.exception.AtlasBaseException: hive is not authorized to
perform create entity: type=__AtlasAuditEntry
at
org.apache.atlas.authorize.AtlasAuthorizationUtils.verifyAccess(AtlasAuthorizationUtils.java:64)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:1150)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:366)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke()
at
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:779)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750)
at
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:111)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:692)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$34d64e85.createOrUpdate()
at
org.apache.atlas.repository.ogm.DataAccess.saveNoLoad(DataAccess.java:73)
at
org.apache.atlas.repository.audit.AtlasAuditService.save(AtlasAuditService.java:65)
at
org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:106)
at
org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:86)
at
org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:71)
at
org.apache.atlas.repository.audit.AtlasAuditService$$FastClassBySpringCGLIB$$2eddda47.invoke()
at
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:688)
at
org.apache.atlas.repository.audit.AtlasAuditService$$EnhancerBySpringCGLIB$$bd2eba1f.add()
at
org.apache.atlas.web.resources.AdminResource.addToImportOperationAudits(AdminResource.java:839)
at
org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:522)
at sun.reflect.GeneratedMethodAccessor328.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchPr
[jira] [Resolved] (ATLAS-4482) GCP : Load data in path query throws Referenced entity -guid is not found and the GCP directory is not created in Atlas
[
https://issues.apache.org/jira/browse/ATLAS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4482.
--
Resolution: Fixed
> GCP : Load data in path query throws Referenced entity -guid is not found
> and the GCP directory is not created in Atlas
> -
>
> Key: ATLAS-4482
> URL: https://issues.apache.org/jira/browse/ATLAS-4482
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 2.3.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Following queries have succeeded:
>
> {code:java}
> create external table default.hive_table_cloud_load_data_in_path_qiuvr
> (student_roll int, student_name string, student_dob date) ROW FORMAT
> DELIMITED FIELDS TERMINATED BY ' ' STORED AS TEXTFILE location
> 'gs://gcp-eng-qe-func-daily/cc-atlas-fmp5pj-dd/warehouse/tablespace/external/hive/hive_table_cloud_load_data_in_path_qiuvr'
> load data inpath
> 'gs://gcp-eng-qe-func-daily/cc-atlas-fmp5pj-dd/hive_table_cloud_load_data_in_path_qiuvr_input_data.txt'
> into table hive_table_cloud_load_data_in_path_qiuvr
> {code}
>
> In Atlas , could see the following exception:
> {code:java}
> 2021-11-11 10:38:36,236 ERROR - [NotificationHookConsumer thread-0:] ~ graph
> rollback due to exception AtlasBaseException:Referenced entity -9503445734599
> is not found (GraphTransactionInterceptor:202)
> 2021-11-11 10:38:36,236 WARN - [NotificationHookConsumer thread-0:] ~ Max
> retries exceeded for message
> {"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgCreationTime":1636627116236,"spooled":false,"message":{"type":"ENTITY_CREATE_V2","user":"hrt_qa","entities":{"referredEntities":{"-9503445734600":{"typeName":"gcp_storage_virtual_directory","attributes":{"qualifiedName":"gs://gcp-eng-qe-func-daily/cc-atlas-fmp5pj-dd/@cm","name":"cc-atlas-fmp5pj-dd","objectPrefix":"/"},"guid":"-9503445734600","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"parent":{"guid":"-9503445734599","typeName":"gcp_storage_bucket","uniqueAttributes":{"qualifiedName":"gs://gcp-eng-qe-func-daily@cm"},"relationshipType":"gcp_storage_parent_children"}},"proxy":false},"-9503445734601":{"typeName":"gcp_storage_virtual_directory","attributes":{"qualifiedName":"gs://gcp-eng-qe-func-daily/cc-atlas-fmp5pj-dd/hive_table_cloud_load_data_in_path_qiuvr_input_data.txt/@cm","name":"hive_table_cloud_load_data_in_path_qiuvr_input_data.txt","objectPrefix":"/cc-atlas-fmp5pj-dd/"},"guid":"-9503445734601","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"parent":{"guid":"-9503445734600","typeName":"gcp_storage_virtual_directory","uniqueAttributes":{"qualifiedName":"gs://gcp-eng-qe-func-daily/cc-atlas-fmp5pj-dd/@cm"},"relationshipType":"gcp_storage_parent_children"}},"proxy":false}},"entities":[{"typeName":"hive_process_execution","attributes":{"hostName":"atlas-fmp5pj-dw-master1.atlas-vh.l2ov-m7vs.int.cldr.work","qualifiedName":"LOAD:gs:gcp-eng-qe-func-dailycc-atlas-fmp5pj-ddhive_table_cloud_load_data_in_path_qiuvr_input_data.txt->:default.hive_table_cloud_load_data_in_path_qiuvr@cm:1636627083000:1636627112266:1636627115211","name":"LOAD:gs:gcp-eng-qe-func-dailycc-atlas-fmp5pj-ddhive_table_cloud_load_data_in_path_qiuvr_input_data.txt->:default.hive_table_cloud_load_data_in_path_qiuvr@cm:1636627083000:1636627112266:1636627115211","queryText":"load
> data inpath
> 'gs://gcp-eng-qe-func-daily/cc-atlas-fmp5pj-dd/hive_table_cloud_load_data_in_path_qiuvr_input_data.txt'
> into table
> hive_table_cloud_load_data_in_path_qiuvr","startTime":1636627112266,"queryPlan":"Not
>
> Supported","endTime":1636627115211,"userName":"hrt_qa","queryId":"hive_2021103832_2983e653-a768-4062-a1bc-0224f5346765"},"guid":"-9503445734609","isIncomplete":false,"provenanceType":0,"version":0,"relationshipAttributes":{"process":{"guid":"-9503445734608","typeName":"hive_process","relationshipType":"hive_process_process_executions"}},"proxy":false},{"typeName":"hive_process","attributes":{"recentQueries":["load
> data inpath
> 'gs://gcp-eng-qe-func-daily/cc-atlas-fmp5pj-dd/hive_table_cloud_load_data_in_path_qiuvr_input_data.txt'
> into table
> hive_table_cloud_load_data_in_path_qiuvr"],"qualifiedName":"LOAD:gs:gcp-eng-qe-func-dailycc-atlas-fmp5pj-ddhive_table_cloud_load_data_in_path_qiuvr_input_data.txt->:default.hive_table_cloud_load_data_in_path_qiuvr@cm:1636627083000","clusterName":"cm","name":"LOAD:gs:gcp-eng-qe-func-dailycc-atlas-fmp5pj-ddhive_table_cloud_load_data_in_path_qiuvr_input_data.txt->:default.hive_table_cloud_load_data_in_path_qiuvr@cm:1636627083000","queryText":"","operationType":"LOAD","startTime":163662711
[jira] [Created] (ATLAS-4481) Atlas API on update classifications is failing with NPE when we pass body without propagate flag
Sidharth Kumar Mishra created ATLAS-4481:
Summary: Atlas API on update classifications is failing with NPE
when we pass body without propagate flag
Key: ATLAS-4481
URL: https://issues.apache.org/jira/browse/ATLAS-4481
Project: Atlas
Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra
Curl:
curl --location --request PUT
'http://atlas-host:31000/api/atlas/v2/entity/guid/86ed9144-dc1d-4c5a-8f04-836cf6c9fc4b/classifications'
\
--header 'Content-Type: application/json' \
--header 'Cookie: ATLASSESSIONID=node0xhfij9kxtpwo1fuxrfem3u7u11.node0' \
--data-raw '[
{
"typeName": "PII_STATUS",
"attributes": {
"status": "accepted"
}
}
]'
Response : [
{"success":false,"guid":"86ed9144-dc1d-4c5a-8f04-836cf6c9fc4b","err":"Unexpected
error from Atlas: Received "}
]
NPE Details from Atlas log:
ea4c-411c-913b-edce4b6ecd4f/classifications?doAs=alpha_stagecookieuser
(AtlasAuthenticationFilter$KerberosFilterChainWrapper:800)
2021-11-10 11:09:08,670 ERROR - [etp1632682988-593 -
76b982fc-8582-49f2-98f3-6f103af81188:knox:PUT/api/atlas/v2/entity/guid/5a49aab9-ea4c-411c-913b-edce4b6ecd4f/classifications]
~ graph rollback due to exception (GraphTransactionInterceptor:200)
java.lang.NullPointerException
at
org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.updateClassifications(EntityGraphMapper.java:2411)
at
org.apache.atlas.repository.store.graph.v2.EntityGraphMapper$$FastClassBySpringCGLIB$$8e3f1c72.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
at
org.apache.atlas.repository.store.graph.v2.EntityGraphMapper$$EnhancerBySpringCGLIB$$5bec6507.updateClassifications()
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.updateClassifications(AtlasEntityStoreV2.java:721)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.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.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:111)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$2c77000c.updateClassifications()
at
org.apache.atlas.web.rest.EntityREST.updateClassifications(EntityREST.java:586)
at
org.apache.atlas.web.rest.EntityREST$$FastClassBySpringCGLIB$$31581d5e.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.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:84)
at
org.apache.atlas.web.service.TimedAspectInterceptor.timerAdvice(TimedAspectInterceptor.java:46)
at sun.reflect.GeneratedMethodAccessor165.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616)
at
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
at
org.apache.atlas.web.rest.EntityREST$$EnhancerBySpringCGLIB$$345affc6.updateClassifications()
at sun.reflect.GeneratedMethodAccessor372.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMet
[jira] [Created] (ATLAS-4475) Import Hive V2 is throwing wrong log message when running with set of tables
Sidharth Kumar Mishra created ATLAS-4475: Summary: Import Hive V2 is throwing wrong log message when running with set of tables Key: ATLAS-4475 URL: https://issues.apache.org/jira/browse/ATLAS-4475 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (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&focusedCommentId=17441381#comment-17441381 ] Sidharth Kumar Mishra edited comment on ATLAS-4246 at 11/10/21, 1:24 AM: - Hi [~aileeen], Please add your email id, Commit Msg etc to the patch and upload again. I will merge once add these details. The header for patch should be like: From: Date: <> Subject: Recent successful CI build - https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/956/ Thanks cc: [~sarath] , [~amestry] was (Author: sidharthkmishra): Hi [~aileeen], Please add your email id, Commit Msg etc to the patch and upload again. I will merge once add these details. The header for patch should be like: From: Date: <> Subject: Thanks cc: [~sarath] , [~amestry] > 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&focusedCommentId=17441381#comment-17441381 ] Sidharth Kumar Mishra commented on ATLAS-4246: -- Hi [~aileeen], Please add your email id, Commit Msg etc to the patch and upload again. I will merge once add these details. The header for patch should be like: From: Date: <> Subject: Thanks cc: [~sarath] , [~amestry] > 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] [Resolved] (ATLAS-4159) Build failure on ARM64
[
https://issues.apache.org/jira/browse/ATLAS-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4159.
--
Resolution: Fixed
> Build failure on ARM64
> --
>
> Key: ATLAS-4159
> URL: https://issues.apache.org/jira/browse/ATLAS-4159
> Project: Atlas
> Issue Type: Bug
> Components: storm-integration
>Reporter: Martin Tzvetanov Grigorov
>Priority: Major
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> Apache Atlas build fails on ARM64/AARCH64 machines with:
>
> {code:java}
> INFO] --- maven-failsafe-plugin:2.18.1:integration-test (integration-test) @
> storm-bridge ---
> [WARNING] useSystemClassloader setting has no effect when not forking
> [INFO] Failsafe report directory:
> /home/ubuntu/git/apache/atlas/addons/storm-bridge/target/failsafe-reports
> Running org.apache.atlas.storm.hook.StormAtlasHookIT
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 2.758 sec <<<
> FAILURE! - in org.apache.atlas.storm.hook.StormAtlasHookIT
> setUp(org.apache.atlas.storm.hook.StormAtlasHookIT) Time elapsed: 2.686 sec
> <<< FAILURE!
> java.lang.UnsatisfiedLinkError: /tmp/librocksdbjni7739762391070118246.so:
> /tmp/librocksdbjni7739762391070118246.so: cannot open shared object file: No
> such file or directory (Possible cause: can't load AMD 64-bit .so on a
> AARCH64-bit platform)
> at java.lang.ClassLoader$NativeLibrary.load(Native Method)
> at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934)
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1817)
> at java.lang.Runtime.load0(Runtime.java:810)
> at java.lang.System.load(System.java:1088)
> at
> org.rocksdb.NativeLibraryLoader.loadLibraryFromJar(NativeLibraryLoader.java:78)
> at
> org.rocksdb.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:56)
> at org.rocksdb.RocksDB.loadLibrary(RocksDB.java:64)
> at org.rocksdb.RocksDB.(RocksDB.java:35)
> at
> org.apache.storm.metricstore.rocksdb.RocksDbStore.prepare(RocksDbStore.java:67)
> at
> org.apache.storm.metricstore.MetricStoreConfig.configure(MetricStoreConfig.java:33)
> at org.apache.storm.daemon.nimbus.Nimbus.(Nimbus.java:531)
> at org.apache.storm.LocalCluster.(LocalCluster.java:244)
> at org.apache.storm.LocalCluster.(LocalCluster.java:126)
> at org.apache.storm.LocalCluster$Builder.build(LocalCluster.java:1234)
> at org.apache.storm.Testing.getLocalCluster(Testing.java:231)
> at
> org.apache.atlas.storm.hook.StormTestUtil.createLocalStormCluster(StormTestUtil.java:45)
> at
> org.apache.atlas.storm.hook.StormAtlasHookIT.setUp(StormAtlasHookIT.java:53)
> Results :Failed tests:
> StormAtlasHookIT.setUp:53 » UnsatisfiedLink
> /tmp/librocksdbjni7739762391070118...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[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&focusedCommentId=17437081#comment-17437081 ] Sidharth Kumar Mishra commented on ATLAS-4246: -- [~aileeen] From the recent two runs [https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/947/] and [https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/946/] it looks like some of the Kafka bridge test cases are failing consistently and it could be because of your change. Could you please look at it in detail? Some of the details of test failures: [ERROR] org.apache.atlas.kafka.bridge.KafkaBridgeTest.testCreateTopic Time elapsed: 0.13 s <<< FAILURE! org.apache.http.conn.HttpHostConnectException: Connect to localhost:80 [localhost/127.0.0.1] failed: Connection refused (Connection refused) at org.apache.atlas.kafka.bridge.KafkaBridgeTest.testCreateTopic(KafkaBridgeTest.java:146) Caused by: java.net.ConnectException: Connection refused (Connection refused) at org.apache.atlas.kafka.bridge.KafkaBridgeTest.testCreateTopic(KafkaBridgeTest.java:146) [ERROR] org.apache.atlas.kafka.bridge.KafkaBridgeTest.testImportTopic Time elapsed: 0.01 s <<< FAILURE! org.apache.http.conn.HttpHostConnectException: Connect to localhost:80 [localhost/127.0.0.1] failed: Connection refused (Connection refused) at org.apache.atlas.kafka.bridge.KafkaBridgeTest.testImportTopic(KafkaBridgeTest.java:117) Caused by: java.net.ConnectException: Connection refused (Connection refused) at org.apache.atlas.kafka.bridge.KafkaBridgeTest.testImportTopic(KafkaBridgeTest.java:117) [ERROR] org.apache.atlas.kafka.bridge.KafkaBridgeTest.testUpdateTopic Time elapsed: 0.009 s <<< FAILURE! org.apache.http.conn.HttpHostConnectException: Connect to localhost:80 [localhost/127.0.0.1] failed: Connection refused (Connection refused) at org.apache.atlas.kafka.bridge.KafkaBridgeTest.testUpdateTopic(KafkaBridgeTest.java:226) Caused by: java.net.ConnectException: Connection refused (Connection refused) at org.apache.atlas.kafka.bridge.KafkaBridgeTest.testUpdateTopic(KafkaBridgeTest.java:226) cc: [~amestry], [~sarath] > 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.3.4#803005)
[jira] [Comment Edited] (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&focusedCommentId=17435730#comment-17435730 ] Sidharth Kumar Mishra edited comment on ATLAS-4246 at 10/29/21, 10:38 PM: -- [~aileeen] We have fixed our CI build. Started the PreCommit job - https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/942/ Once it will pass I will commit your patch. cc: [~amestry], [~sarath] was (Author: sidharthkmishra): [~aileeen] We have fixed our CI build. Started the PreCommit job - https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/935/ Once it will pass I will commit your patch. cc: [~amestry], [~sarath] > 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.3.4#803005)
[jira] [Comment Edited] (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&focusedCommentId=17435730#comment-17435730 ] Sidharth Kumar Mishra edited comment on ATLAS-4246 at 10/29/21, 3:25 AM: - [~aileeen] We have fixed our CI build. Started the PreCommit job - https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/935/ Once it will pass I will commit your patch. cc: [~amestry], [~sarath] was (Author: sidharthkmishra): [~aileeen] We have fixed our CI build. Started the PreCommit job - [https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/933/] Once it will pass I will commit your patch. cc: [~amestry], [~sarath] > 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.3.4#803005)
[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&focusedCommentId=17435730#comment-17435730 ] Sidharth Kumar Mishra commented on ATLAS-4246: -- [~aileeen] We have fixed our CI build. Started the PreCommit job - [https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/933/] Once it will pass I will commit your patch. cc: [~amestry], [~sarath] > 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.3.4#803005)
[jira] [Comment Edited] (ATLAS-4351) Maven-jetty throwing warnings when running Integration tests for conflicting jars in classpath
[ https://issues.apache.org/jira/browse/ATLAS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435660#comment-17435660 ] Sidharth Kumar Mishra edited comment on ATLAS-4351 at 10/28/21, 9:15 PM: - Reverting the changes - Code review - [https://reviews.apache.org/r/73670/] was (Author: sidharthkmishra): Reverting the changes as part of review - https://reviews.apache.org/r/73670/ > Maven-jetty throwing warnings when running Integration tests for conflicting > jars in classpath > --- > > Key: ATLAS-4351 > URL: https://issues.apache.org/jira/browse/ATLAS-4351 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0, 2.2.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > Below warnings are thrown when integration tests executed : > [INFO] jetty-9.4.31.v20200723; built: 2020-07-23T17:57:36.812Z; git: > 450ba27947e13e66baa8cd1ce7e85a4461cacc1d; jvm 1.8.0_291-b10 > [WARNING] javax.activation.ActivationDataFlavor scanned from multiple > locations: jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/jakarta.activation-api-1.2.1.jar!/javax/activation/ActivationDataFlavor.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.activation-api-1.2.0.jar!/javax/activation/ActivationDataFlavor.class] > [WARNING] com.google.common.base.Stopwatch$1 scanned from multiple locations: > jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/guava-25.1-jre.jar!/com/google/common/base/Stopwatch$1.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/janusgraph-hbase-0.5.3.jar!/com/google/common/base/Stopwatch$1.class] > [WARNING] javax.servlet.AsyncContext scanned from multiple locations: jar: > [file:///home/jenkins/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncContext.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncContext.class] > [WARNING] javax.servlet.AsyncEvent scanned from multiple locations: jar: > [file:///home/jenkins/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncEvent.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncEvent.class] > [WARNING] javax.servlet.AsyncListener scanned from multiple locations: jar: > [file:///home/jenkins/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncListener.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncListener.class] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4351) Maven-jetty throwing warnings when running Integration tests for conflicting jars in classpath
[ https://issues.apache.org/jira/browse/ATLAS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435660#comment-17435660 ] Sidharth Kumar Mishra commented on ATLAS-4351: -- Reverting the changes as part of review - https://reviews.apache.org/r/73670/ > Maven-jetty throwing warnings when running Integration tests for conflicting > jars in classpath > --- > > Key: ATLAS-4351 > URL: https://issues.apache.org/jira/browse/ATLAS-4351 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0, 2.2.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > Below warnings are thrown when integration tests executed : > [INFO] jetty-9.4.31.v20200723; built: 2020-07-23T17:57:36.812Z; git: > 450ba27947e13e66baa8cd1ce7e85a4461cacc1d; jvm 1.8.0_291-b10 > [WARNING] javax.activation.ActivationDataFlavor scanned from multiple > locations: jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/jakarta.activation-api-1.2.1.jar!/javax/activation/ActivationDataFlavor.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.activation-api-1.2.0.jar!/javax/activation/ActivationDataFlavor.class] > [WARNING] com.google.common.base.Stopwatch$1 scanned from multiple locations: > jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/guava-25.1-jre.jar!/com/google/common/base/Stopwatch$1.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/janusgraph-hbase-0.5.3.jar!/com/google/common/base/Stopwatch$1.class] > [WARNING] javax.servlet.AsyncContext scanned from multiple locations: jar: > [file:///home/jenkins/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncContext.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncContext.class] > [WARNING] javax.servlet.AsyncEvent scanned from multiple locations: jar: > [file:///home/jenkins/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncEvent.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncEvent.class] > [WARNING] javax.servlet.AsyncListener scanned from multiple locations: jar: > [file:///home/jenkins/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncListener.class] > , jar: > [file:///home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/webapp/target/atlas-webapp-3.0.0-SNAPSHOT/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncListener.class] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4463) Infinite loop at Index Health Monitor (IndexRecoveryService)
Sidharth Kumar Mishra created ATLAS-4463: Summary: Infinite loop at Index Health Monitor (IndexRecoveryService) Key: ATLAS-4463 URL: https://issues.apache.org/jira/browse/ATLAS-4463 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra When we stop the IndexRecoveryService service, it doesn't stop the RecoveryThread child thread and RecoveryThread thread run Infinitely. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4462) Atlas tests are failing and PreCommit tests are also failing
Sidharth Kumar Mishra created ATLAS-4462: Summary: Atlas tests are failing and PreCommit tests are also failing Key: ATLAS-4462 URL: https://issues.apache.org/jira/browse/ATLAS-4462 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4425) Migration import should be able to import multiple zip files present in a particular path
Sidharth Kumar Mishra created ATLAS-4425: Summary: Migration import should be able to import multiple zip files present in a particular path Key: ATLAS-4425 URL: https://issues.apache.org/jira/browse/ATLAS-4425 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra Right now migration import only imports one zip file. Instead it should import all the zip files given inside a path in lexicographic order -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4424) Enhance the Import hive utility to create export zip files and run bulk import
Sidharth Kumar Mishra created ATLAS-4424: Summary: Enhance the Import hive utility to create export zip files and run bulk import Key: ATLAS-4424 URL: https://issues.apache.org/jira/browse/ATLAS-4424 Project: Atlas Issue Type: Improvement Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra The enhanced import hive will work in two stages to improves the performance: stage 1 - Create the hive metadata export zip file stage 2 - Use the exported zip file to run bulk import at Atlas Instead of stage two we can even run the migration import for more performance boost. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4400) Lower version of aws_s3_v2_directory (1.2) of Atlas is is compatible with new Hooks
[ https://issues.apache.org/jira/browse/ATLAS-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4400: - Description: Due to this the aws_s3_v2_directory metadata data at Atlas is getting lost or overridden by new data. New version of Atlas should contains the correct objectPrefix value at aws_s3_v2_directory even if the older Hooks are interacting with newer Atlas with aws_s3_v2_directory version 1.2. Similarly the older Atlas with aws_s3_v2_directory version 1.1 should have any issue when Hooks are upgraded to recent version. (was: Due to this the metadata data at Atlas ) > Lower version of aws_s3_v2_directory (1.2) of Atlas is is compatible with new > Hooks > --- > > Key: ATLAS-4400 > URL: https://issues.apache.org/jira/browse/ATLAS-4400 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Due to this the aws_s3_v2_directory metadata data at Atlas is getting lost or > overridden by new data. New version of Atlas should contains the correct > objectPrefix value at aws_s3_v2_directory even if the older Hooks are > interacting with newer Atlas with aws_s3_v2_directory version 1.2. Similarly > the older Atlas with aws_s3_v2_directory version 1.1 should have any issue > when Hooks are upgraded to recent version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4400) Lower version of aws_s3_v2_directory (1.2) of Atlas is is compatible with new Hooks
[ https://issues.apache.org/jira/browse/ATLAS-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4400: - Description: Due to this the metadata data at Atlas > Lower version of aws_s3_v2_directory (1.2) of Atlas is is compatible with new > Hooks > --- > > Key: ATLAS-4400 > URL: https://issues.apache.org/jira/browse/ATLAS-4400 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Due to this the metadata data at Atlas -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4400) Lower version of aws_s3_v2_directory (1.2) of Atlas is is compatible with new Hooks
Sidharth Kumar Mishra created ATLAS-4400: Summary: Lower version of aws_s3_v2_directory (1.2) of Atlas is is compatible with new Hooks Key: ATLAS-4400 URL: https://issues.apache.org/jira/browse/ATLAS-4400 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4383) Update Atlas website for 2.2.0 release
[ https://issues.apache.org/jira/browse/ATLAS-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4383: - Attachment: (was: ATLAS-4383-updated-documentation-for-2.2.0-release_branch-2.0.patch) > Update Atlas website for 2.2.0 release > -- > > Key: ATLAS-4383 > URL: https://issues.apache.org/jira/browse/ATLAS-4383 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Attachments: > ATLAS-4383-updated-documentation-for-2.2.0-release-master-2.patch, > ATLAS-4383-updated-documentation-for-2.2.0-release_branch-2.0-2.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4383) Update Atlas website for 2.2.0 release
[ https://issues.apache.org/jira/browse/ATLAS-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4383: - Attachment: ATLAS-4383-updated-documentation-for-2.2.0-release-master-2.patch ATLAS-4383-updated-documentation-for-2.2.0-release_branch-2.0-2.patch > Update Atlas website for 2.2.0 release > -- > > Key: ATLAS-4383 > URL: https://issues.apache.org/jira/browse/ATLAS-4383 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Attachments: > ATLAS-4383-updated-documentation-for-2.2.0-release-master-2.patch, > ATLAS-4383-updated-documentation-for-2.2.0-release_branch-2.0-2.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4383) Update Atlas website for 2.2.0 release
[ https://issues.apache.org/jira/browse/ATLAS-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4383: - Attachment: (was: ATLAS-4383-updated-documentation-for-2.2.0-release-master.patch) > Update Atlas website for 2.2.0 release > -- > > Key: ATLAS-4383 > URL: https://issues.apache.org/jira/browse/ATLAS-4383 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Attachments: > ATLAS-4383-updated-documentation-for-2.2.0-release-master-2.patch, > ATLAS-4383-updated-documentation-for-2.2.0-release_branch-2.0-2.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4383) Update Atlas website for 2.2.0 release
[ https://issues.apache.org/jira/browse/ATLAS-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4383: - Attachment: ATLAS-4383-updated-documentation-for-2.2.0-release-master.patch ATLAS-4383-updated-documentation-for-2.2.0-release_branch-2.0.patch > Update Atlas website for 2.2.0 release > -- > > Key: ATLAS-4383 > URL: https://issues.apache.org/jira/browse/ATLAS-4383 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Attachments: > ATLAS-4383-updated-documentation-for-2.2.0-release-master.patch, > ATLAS-4383-updated-documentation-for-2.2.0-release_branch-2.0.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4383) Update Atlas website for 2.2.0 release
[ https://issues.apache.org/jira/browse/ATLAS-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4383: - Attachment: (was: ATLAS-4383-updated-documentation-for-2.2.0-release.patch) > Update Atlas website for 2.2.0 release > -- > > Key: ATLAS-4383 > URL: https://issues.apache.org/jira/browse/ATLAS-4383 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4394) Build error due to wrong version of atllass-buildtools at pom.xml
[ https://issues.apache.org/jira/browse/ATLAS-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra reassigned ATLAS-4394: Assignee: Sidharth Kumar Mishra > Build error due to wrong version of atllass-buildtools at pom.xml > - > > Key: ATLAS-4394 > URL: https://issues.apache.org/jira/browse/ATLAS-4394 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Error facing while running - > mvn clean install -Papache-release -DskipTests -DskipDocs -DskipCheck > > Error Details: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check > (checkstyle-check) on project apache-atlas: Execution checkstyle-check of > goal org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check failed: > Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1 or one of its > dependencies could not be resolved: org.apache.atlas:atlas-buildtools:jar:1.0 > was not found in [https://repo.maven.apache.org/maven2] during a previous > attempt. This failure was cached in the local repository and resolution is > not reattempted until the update interval of central has elapsed or updates > are forced -> [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/PluginResolutionException] > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :apache-atlas > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4394) Build error due to wrong version of atllass-buildtools at pom.xml
Sidharth Kumar Mishra created ATLAS-4394: Summary: Build error due to wrong version of atllass-buildtools at pom.xml Key: ATLAS-4394 URL: https://issues.apache.org/jira/browse/ATLAS-4394 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Error facing while running - mvn clean install -Papache-release -DskipTests -DskipDocs -DskipCheck Error Details: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check (checkstyle-check) on project apache-atlas: Execution checkstyle-check of goal org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1 or one of its dependencies could not be resolved: org.apache.atlas:atlas-buildtools:jar:1.0 was not found in [https://repo.maven.apache.org/maven2] during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced -> [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/PluginResolutionException] [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :apache-atlas -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4384) Publish release artifacts
[ https://issues.apache.org/jira/browse/ATLAS-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra resolved ATLAS-4384. -- Resolution: Fixed Published and verified at [https://repository.apache.org/content/repositories/releases/org/apache/atlas/] > Publish release artifacts > - > > Key: ATLAS-4384 > URL: https://issues.apache.org/jira/browse/ATLAS-4384 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4277) [Atlas: Glossary Term Bulk Import] [Regression] Unable to create term term_1 under glossary glossary_1 via bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4277.
--
Resolution: Fixed
Already Fixed
> [Atlas: Glossary Term Bulk Import] [Regression] Unable to create term term_1
> under glossary glossary_1 via bulk import
> --
>
> Key: ATLAS-4277
> URL: https://issues.apache.org/jira/browse/ATLAS-4277
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Unable to create term *term_1* under glossary *glossary_1* the cluster with
> latest bits
> Import input:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1
> glossary_1,term_2{code}
> Current result:
> {code:java}
> {
> "failedImportInfoList":[
> {
> "parentObjectName":"glossary_1",
> "childObjectName":"term_1",
> "importStatus":"FAILED",
> "remarks":"Glossary term with qualifiedName term_1@glossary_1 already
> exists"
> }
> ],
> "successImportInfoList":[
> {
> "parentObjectName":"glossary_1",
> "childObjectName":"term_2",
> "importStatus":"SUCCESS",
>
> "remarks":"{\"termGuid\":\"8fe9a26a-aa14-4ed4-9a37-ef6db69ec29b\",\"qualifiedName\":\"term_2@glossary_1\"}"
> }
> ]
> } {code}
> Even though there is no glossary with name glossary_1 and you are creating it
> for the first time, this error is thrown.
> This was working fine on the older bits
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4266) [Atlas: Glossary Term Bulk Import] Import fails with success state
[
https://issues.apache.org/jira/browse/ATLAS-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4266.
--
Resolution: Fixed
This is fixed as part of
[ATLAS-4288|https://reviews.apache.org/r/73358/bugs/ATLAS-4288/]
> [Atlas: Glossary Term Bulk Import] Import fails with success state
> --
>
> Key: ATLAS-4266
> URL: https://issues.apache.org/jira/browse/ATLAS-4266
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-04-28 at 4.34.30 PM.png, Screenshot
> 2021-04-28 at 5.00.33 PM.png, Screenshot 2021-04-28 at 5.00.33 PM.png
>
>
> The following is a complete failure scenario, where the user inputs blank
> spaces, here the import fails with complete failure, but the status is *200*
> ok
> *Scenario*: Import Blank glossary and terms
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> " ", " "{code}
> *Observation:*
> {code:java}
> {
> "failedImportInfoList":[
> {
> "parentObjectName":"",
> "childObjectName":null,
> "importStatus":"FAILED",
> "remarks":"The GlossaryName is blank for the record : [ , ]"
> },
> {
> "parentObjectName":"",
> "childObjectName":null,
> "importStatus":"FAILED",
> "remarks":"The GlossaryName is blank for the record : [ , ]"
> }
> ]
> }{code}
> !Screenshot 2021-04-28 at 5.00.33 PM.png|width=597,height=399! There is only
> failure report in the response
> !Screenshot 2021-04-28 at 5.00.33 PM.png|width=854,height=570!
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4266) [Atlas: Glossary Term Bulk Import] Import fails with success state
[
https://issues.apache.org/jira/browse/ATLAS-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-4266:
Assignee: Sidharth Kumar Mishra
> [Atlas: Glossary Term Bulk Import] Import fails with success state
> --
>
> Key: ATLAS-4266
> URL: https://issues.apache.org/jira/browse/ATLAS-4266
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-04-28 at 4.34.30 PM.png, Screenshot
> 2021-04-28 at 5.00.33 PM.png, Screenshot 2021-04-28 at 5.00.33 PM.png
>
>
> The following is a complete failure scenario, where the user inputs blank
> spaces, here the import fails with complete failure, but the status is *200*
> ok
> *Scenario*: Import Blank glossary and terms
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> " ", " "{code}
> *Observation:*
> {code:java}
> {
> "failedImportInfoList":[
> {
> "parentObjectName":"",
> "childObjectName":null,
> "importStatus":"FAILED",
> "remarks":"The GlossaryName is blank for the record : [ , ]"
> },
> {
> "parentObjectName":"",
> "childObjectName":null,
> "importStatus":"FAILED",
> "remarks":"The GlossaryName is blank for the record : [ , ]"
> }
> ]
> }{code}
> !Screenshot 2021-04-28 at 5.00.33 PM.png|width=597,height=399! There is only
> failure report in the response
> !Screenshot 2021-04-28 at 5.00.33 PM.png|width=854,height=570!
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4265) [Atlas: Glossary Term Bulk Import]: Error message is displayed twice for an error in bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4265.
--
Resolution: Fixed
Fixed as part of
[ATLAS-4261|https://reviews.apache.org/r/73313/bugs/ATLAS-4261/]
> [Atlas: Glossary Term Bulk Import]: Error message is displayed twice for an
> error in bulk import
>
>
> Key: ATLAS-4265
> URL: https://issues.apache.org/jira/browse/ATLAS-4265
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-04-28 at 4.34.30 PM.png
>
>
> Scenario: Import Blank glossary and terms
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> " ", " "{code}
> *Observation:*
> {code:java}
> {
> "failedImportInfoList":[
> {
> "parentObjectName":"",
> "childObjectName":null,
> "importStatus":"FAILED",
> "remarks":"The GlossaryName is blank for the record : [ , ]"
> },
> {
> "parentObjectName":"",
> "childObjectName":null,
> "importStatus":"FAILED",
> "remarks":"The GlossaryName is blank for the record : [ , ]"
> }
> ]
> }{code}
> !Screenshot 2021-04-28 at 4.34.30 PM.png|width=546,height=217!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4265) [Atlas: Glossary Term Bulk Import]: Error message is displayed twice for an error in bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-4265:
Assignee: Sidharth Kumar Mishra
> [Atlas: Glossary Term Bulk Import]: Error message is displayed twice for an
> error in bulk import
>
>
> Key: ATLAS-4265
> URL: https://issues.apache.org/jira/browse/ATLAS-4265
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-04-28 at 4.34.30 PM.png
>
>
> Scenario: Import Blank glossary and terms
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> " ", " "{code}
> *Observation:*
> {code:java}
> {
> "failedImportInfoList":[
> {
> "parentObjectName":"",
> "childObjectName":null,
> "importStatus":"FAILED",
> "remarks":"The GlossaryName is blank for the record : [ , ]"
> },
> {
> "parentObjectName":"",
> "childObjectName":null,
> "importStatus":"FAILED",
> "remarks":"The GlossaryName is blank for the record : [ , ]"
> }
> ]
> }{code}
> !Screenshot 2021-04-28 at 4.34.30 PM.png|width=546,height=217!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4185) [Atlas: Glossary Term Bulk Import] Facing intermittent failures with Bulk Import
[
https://issues.apache.org/jira/browse/ATLAS-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4185.
--
Resolution: Fixed
Fixed as part of
[ATLAS-4288|https://reviews.apache.org/r/73358/bugs/ATLAS-4288/]
> [Atlas: Glossary Term Bulk Import] Facing intermittent failures with Bulk
> Import
>
>
> Key: ATLAS-4185
> URL: https://issues.apache.org/jira/browse/ATLAS-4185
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-03-04 at 3.39.32 PM.png
>
>
> Input used:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossaryBulkImport_2,BwTZ_1
> glossaryBulkImport_2,BwTZ_2
> glossaryBulkImport_2,BwTZ_3
> glossaryBulkImport_2,BwTZ_4
> glossaryBulkImport_2,BwTZ_5
> glossaryBulkImport_2,BwTZ_6
> glossaryBulkImport_2,BwTZ_7
> glossaryBulkImport_2,BwTZ_8
> glossaryBulkImport_2,BwTZ_9
> glossaryBulkImport_2,BwTZ_10
> glossaryBulkImport_2,BwTZ_11
> glossaryBulkImport_2,BwTZ_12
> glossaryBulkImport_2,BwTZ_13
> glossaryBulkImport_2,BwTZ_14
> glossaryBulkImport_2,BwTZ_15
> glossaryBulkImport_2,BwTZ_16
> glossaryBulkImport_2,BwTZ_17
> glossaryBulkImport_2,BwTZ_18
> glossaryBulkImport_2,BwTZ_19
> glossaryBulkImport_2,BwTZ_20
> glossaryBulkImport_2,BwTZ_21
> glossaryBulkImport_2,BwTZ_22
> glossaryBulkImport_2,BwTZ_23
> glossaryBulkImport_2,BwTZ_24
> glossaryBulkImport_2,BwTZ_25
> glossaryBulkImport_2,BwTZ_26
> glossaryBulkImport_2,BwTZ_27
> glossaryBulkImport_2,BwTZ_28
> glossaryBulkImport_2,BwTZ_29
> glossaryBulkImport_2,BwTZ_30 {code}
> While performing bulk import *AtlasBaseException* is thrown
> {code:java}
> 2021-03-04 03:27:33,075 INFO -
> [etp1527953000-559:knox:POST/api/atlas/v2/glossary/import] ~ Request from
> authenticated user: knox, URL=/api/atlas/v2/glossary/import?doAs=hrt_qa
> (AtlasAuthenticationFilter$KerberosFilterChainWrapper:739)
> 2021-03-04 03:27:33,896 ERROR - [etp1527953000-559 -
> 25016961-548a-47ca-905e-3a0df3bcf8db:knox:POST/api/atlas/v2/glossary/import]
> ~ Error handling a request: 4716c7eab64cc999 (ExceptionMapperUtil:32)
> org.apache.atlas.exception.AtlasBaseException: Error occurred while creating
> glossary term: {0}
> at
> org.apache.atlas.glossary.GlossaryService.createGlossaryTerms(GlossaryService.java:1107)
> at
> org.apache.atlas.glossary.GlossaryService.importGlossaryData(GlossaryService.java:1092)
> at
> org.apache.atlas.glossary.GlossaryService$$FastClassBySpringCGLIB$$e1f893e0.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
> at
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$d03b0914.importGlossaryData()
> at
> org.apache.atlas.web.rest.GlossaryREST.importGlossaryData(GlossaryREST.java:988)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleReq
[jira] [Assigned] (ATLAS-4185) [Atlas: Glossary Term Bulk Import] Facing intermittent failures with Bulk Import
[
https://issues.apache.org/jira/browse/ATLAS-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-4185:
Assignee: Sidharth Kumar Mishra
> [Atlas: Glossary Term Bulk Import] Facing intermittent failures with Bulk
> Import
>
>
> Key: ATLAS-4185
> URL: https://issues.apache.org/jira/browse/ATLAS-4185
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-03-04 at 3.39.32 PM.png
>
>
> Input used:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossaryBulkImport_2,BwTZ_1
> glossaryBulkImport_2,BwTZ_2
> glossaryBulkImport_2,BwTZ_3
> glossaryBulkImport_2,BwTZ_4
> glossaryBulkImport_2,BwTZ_5
> glossaryBulkImport_2,BwTZ_6
> glossaryBulkImport_2,BwTZ_7
> glossaryBulkImport_2,BwTZ_8
> glossaryBulkImport_2,BwTZ_9
> glossaryBulkImport_2,BwTZ_10
> glossaryBulkImport_2,BwTZ_11
> glossaryBulkImport_2,BwTZ_12
> glossaryBulkImport_2,BwTZ_13
> glossaryBulkImport_2,BwTZ_14
> glossaryBulkImport_2,BwTZ_15
> glossaryBulkImport_2,BwTZ_16
> glossaryBulkImport_2,BwTZ_17
> glossaryBulkImport_2,BwTZ_18
> glossaryBulkImport_2,BwTZ_19
> glossaryBulkImport_2,BwTZ_20
> glossaryBulkImport_2,BwTZ_21
> glossaryBulkImport_2,BwTZ_22
> glossaryBulkImport_2,BwTZ_23
> glossaryBulkImport_2,BwTZ_24
> glossaryBulkImport_2,BwTZ_25
> glossaryBulkImport_2,BwTZ_26
> glossaryBulkImport_2,BwTZ_27
> glossaryBulkImport_2,BwTZ_28
> glossaryBulkImport_2,BwTZ_29
> glossaryBulkImport_2,BwTZ_30 {code}
> While performing bulk import *AtlasBaseException* is thrown
> {code:java}
> 2021-03-04 03:27:33,075 INFO -
> [etp1527953000-559:knox:POST/api/atlas/v2/glossary/import] ~ Request from
> authenticated user: knox, URL=/api/atlas/v2/glossary/import?doAs=hrt_qa
> (AtlasAuthenticationFilter$KerberosFilterChainWrapper:739)
> 2021-03-04 03:27:33,896 ERROR - [etp1527953000-559 -
> 25016961-548a-47ca-905e-3a0df3bcf8db:knox:POST/api/atlas/v2/glossary/import]
> ~ Error handling a request: 4716c7eab64cc999 (ExceptionMapperUtil:32)
> org.apache.atlas.exception.AtlasBaseException: Error occurred while creating
> glossary term: {0}
> at
> org.apache.atlas.glossary.GlossaryService.createGlossaryTerms(GlossaryService.java:1107)
> at
> org.apache.atlas.glossary.GlossaryService.importGlossaryData(GlossaryService.java:1092)
> at
> org.apache.atlas.glossary.GlossaryService$$FastClassBySpringCGLIB$$e1f893e0.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
> at
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$d03b0914.importGlossaryData()
> at
> org.apache.atlas.web.rest.GlossaryREST.importGlossaryData(GlossaryREST.java:988)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey
[jira] [Resolved] (ATLAS-4140) [Atlas: Glossary Term Bulk Import] When imported with only glossary name incorrect message is conveyed
[
https://issues.apache.org/jira/browse/ATLAS-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4140.
--
Resolution: Fixed
Fixed as part of
[ATLAS-4261|https://reviews.apache.org/r/73313/bugs/ATLAS-4261/]
> [Atlas: Glossary Term Bulk Import] When imported with only glossary name
> incorrect message is conveyed
> --
>
> Key: ATLAS-4140
> URL: https://issues.apache.org/jira/browse/ATLAS-4140
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-02-05 at 4.15.35 PM.png
>
>
> On uploading a file with no term name, incorrect message is conveyed
> Please note there is no "*,*" at the end
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1
> {code}
> Note:
> When the data is "glossary_1," instead of "glossary_1" then the right message
> is thrown
> The above input should convey "term name cannot be blank or empty"
> but it throws "No data found in the uploaded file"
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4140) [Atlas: Glossary Term Bulk Import] When imported with only glossary name incorrect message is conveyed
[
https://issues.apache.org/jira/browse/ATLAS-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-4140:
Assignee: Sidharth Kumar Mishra
> [Atlas: Glossary Term Bulk Import] When imported with only glossary name
> incorrect message is conveyed
> --
>
> Key: ATLAS-4140
> URL: https://issues.apache.org/jira/browse/ATLAS-4140
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-02-05 at 4.15.35 PM.png
>
>
> On uploading a file with no term name, incorrect message is conveyed
> Please note there is no "*,*" at the end
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1
> {code}
> Note:
> When the data is "glossary_1," instead of "glossary_1" then the right message
> is thrown
> The above input should convey "term name cannot be blank or empty"
> but it throws "No data found in the uploaded file"
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4132) [Atlas: Glossary Term Bulk Import] When all data is populated with right input bulk import fails
[
https://issues.apache.org/jira/browse/ATLAS-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4132.
--
Resolution: Fixed
Fixed as part of
[ATLAS-4191|https://reviews.apache.org/r/73218/bugs/ATLAS-4191/]
> [Atlas: Glossary Term Bulk Import] When all data is populated with right
> input bulk import fails
>
>
> Key: ATLAS-4132
> URL: https://issues.apache.org/jira/browse/ATLAS-4132
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> When all the fields in the bulk import are populated, bulk import fails with
> the following error
> Please note that glossary_1 and term_1 are being created as a part of this
> same request.
> {code:java}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"The uploaded file has not
> been processed due to the following errors : \n[\nThe provided Reference
> Glossary and TermName does not exist in the system term_1:glossary_1 for
> record with TermName : term_3 and GlossaryName : glossary_3, \nThe provided
> Reference Glossary and TermName does not exist in the system
> term_1:glossary_1 for record with TermName : term_3 and GlossaryName :
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in
> the system term_1:glossary_1 for record with TermName : term_3 and
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName
> does not exist in the system term_1:glossary_1 for record with TermName :
> term_3 and GlossaryName : glossary_3, \nThe provided Reference Glossary and
> TermName does not exist in the system term_1:glossary_1 for record with
> TermName : term_3 and GlossaryName : glossary_3, \nThe provided Reference
> Glossary and TermName does not exist in the system term_1:glossary_1 for
> record with TermName : term_3 and GlossaryName : glossary_3, \nThe provided
> Reference Glossary and TermName does not exist in the system
> term_1:glossary_1 for record with TermName : term_3 and GlossaryName :
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in
> the system term_2:glossary_2 for record with TermName : term_3 and
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName
> does not exist in the system term_1:glossary_1 for record with TermName :
> term_3 and GlossaryName : glossary_3, \nThe provided Reference Glossary and
> TermName does not exist in the system term_1:glossary_1 for record with
> TermName : term_3 and GlossaryName : glossary_3, \nThe provided Reference
> Glossary and TermName does not exist in the system term_1:glossary_1 for
> record with TermName : term_3 and GlossaryName : glossary_3, \nThe provided
> Reference Glossary and TermName does not exist in the system
> term_1:glossary_1 for record with TermName : term_3 and GlossaryName :
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in
> the system term_1:glossary_1 for record with TermName : term_3 and
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName
> does not exist in the system term_1:glossary_1 for record with TermName :
> term_3 and GlossaryName : glossary_3]"}
> {code}
>
> File contents:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1
> glossary_2,term_2
> glossary_3,term_3,"short description for glossary_3","this can be used as
> long description for glossary_3 ", "random glossary Example", "G3", "Usage
> details", "glossaryAttribute:100%|termAttribute:0%",
> "glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1|glossary_2:term_2","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1"
> {code}
> Expectation:
> Since term_1 of glossary_1 and term_2 of glossary_2 are created as a part of
> this same request, glossary_3 and term_3 creation should succeed and
> associate it will the remaining data.
> Observation:
> When the related terms are created as a part of the current import, the call
> fails
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4132) [Atlas: Glossary Term Bulk Import] When all data is populated with right input bulk import fails
[
https://issues.apache.org/jira/browse/ATLAS-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-4132:
Assignee: Sidharth Kumar Mishra
> [Atlas: Glossary Term Bulk Import] When all data is populated with right
> input bulk import fails
>
>
> Key: ATLAS-4132
> URL: https://issues.apache.org/jira/browse/ATLAS-4132
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> When all the fields in the bulk import are populated, bulk import fails with
> the following error
> Please note that glossary_1 and term_1 are being created as a part of this
> same request.
> {code:java}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"The uploaded file has not
> been processed due to the following errors : \n[\nThe provided Reference
> Glossary and TermName does not exist in the system term_1:glossary_1 for
> record with TermName : term_3 and GlossaryName : glossary_3, \nThe provided
> Reference Glossary and TermName does not exist in the system
> term_1:glossary_1 for record with TermName : term_3 and GlossaryName :
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in
> the system term_1:glossary_1 for record with TermName : term_3 and
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName
> does not exist in the system term_1:glossary_1 for record with TermName :
> term_3 and GlossaryName : glossary_3, \nThe provided Reference Glossary and
> TermName does not exist in the system term_1:glossary_1 for record with
> TermName : term_3 and GlossaryName : glossary_3, \nThe provided Reference
> Glossary and TermName does not exist in the system term_1:glossary_1 for
> record with TermName : term_3 and GlossaryName : glossary_3, \nThe provided
> Reference Glossary and TermName does not exist in the system
> term_1:glossary_1 for record with TermName : term_3 and GlossaryName :
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in
> the system term_2:glossary_2 for record with TermName : term_3 and
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName
> does not exist in the system term_1:glossary_1 for record with TermName :
> term_3 and GlossaryName : glossary_3, \nThe provided Reference Glossary and
> TermName does not exist in the system term_1:glossary_1 for record with
> TermName : term_3 and GlossaryName : glossary_3, \nThe provided Reference
> Glossary and TermName does not exist in the system term_1:glossary_1 for
> record with TermName : term_3 and GlossaryName : glossary_3, \nThe provided
> Reference Glossary and TermName does not exist in the system
> term_1:glossary_1 for record with TermName : term_3 and GlossaryName :
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in
> the system term_1:glossary_1 for record with TermName : term_3 and
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName
> does not exist in the system term_1:glossary_1 for record with TermName :
> term_3 and GlossaryName : glossary_3]"}
> {code}
>
> File contents:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1
> glossary_2,term_2
> glossary_3,term_3,"short description for glossary_3","this can be used as
> long description for glossary_3 ", "random glossary Example", "G3", "Usage
> details", "glossaryAttribute:100%|termAttribute:0%",
> "glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1|glossary_2:term_2","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1"
> {code}
> Expectation:
> Since term_1 of glossary_1 and term_2 of glossary_2 are created as a part of
> this same request, glossary_3 and term_3 creation should succeed and
> associate it will the remaining data.
> Observation:
> When the related terms are created as a part of the current import, the call
> fails
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4390) Change the Atlas branch at dev-support/atlas-docker/.env
[ https://issues.apache.org/jira/browse/ATLAS-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4390: - Description: Update the Atlas branch at dev-support/atlas-docker/.env to release-2.2.0-rc1 so that docker build would use Atlas sources from this tag (was: Update the Atlas version at dev-support/atlas-docker/.env to release-2.2.0-rc1 so that docker build would use Atlas sources from this tag) > Change the Atlas branch at dev-support/atlas-docker/.env > - > > Key: ATLAS-4390 > URL: https://issues.apache.org/jira/browse/ATLAS-4390 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Attachments: > ATLAS-4390-Changed-Atlas-branch-to-release-2.2.0-rc1.patch > > > Update the Atlas branch at dev-support/atlas-docker/.env to > release-2.2.0-rc1 so that docker build would use Atlas sources from this tag -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4390) Change the Atlas branch at dev-support/atlas-docker/.env
[ https://issues.apache.org/jira/browse/ATLAS-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4390: - Summary: Change the Atlas branch at dev-support/atlas-docker/.env (was: Change the Atlas version at dev-support/atlas-docker/.env ) > Change the Atlas branch at dev-support/atlas-docker/.env > - > > Key: ATLAS-4390 > URL: https://issues.apache.org/jira/browse/ATLAS-4390 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Attachments: > ATLAS-4390-Changed-Atlas-branch-to-release-2.2.0-rc1.patch > > > Update the Atlas version at dev-support/atlas-docker/.env to > release-2.2.0-rc1 so that docker build would use Atlas sources from this tag -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4390) Change the Atlas version at dev-support/atlas-docker/.env
[ https://issues.apache.org/jira/browse/ATLAS-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4390: - Description: Update the Atlas version at dev-support/atlas-docker/.env to release-2.2.0-rc1 so that docker build would use Atlas sources from this tag (was: Update the Atlas version at dev-support/atlas-docker/.env to release-2.2.0-rc0 so that docker build would use Atlas sources from this tag) > Change the Atlas version at dev-support/atlas-docker/.env > -- > > Key: ATLAS-4390 > URL: https://issues.apache.org/jira/browse/ATLAS-4390 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Update the Atlas version at dev-support/atlas-docker/.env to > release-2.2.0-rc1 so that docker build would use Atlas sources from this tag -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4391) NoSuchFileException for ${atlas.log.dir}/atlas-metrics.out
Sidharth Kumar Mishra created ATLAS-4391:
Summary: NoSuchFileException for
${atlas.log.dir}/atlas-metrics.out
Key: ATLAS-4391
URL: https://issues.apache.org/jira/browse/ATLAS-4391
Project: Atlas
Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Mayank Jain
Atlas startup logs NoSuchFileException for ${atlas.log.dir}/atlas-metrics.out:
2021-08-05 07:54:07,353 WARN - [main:] ~ Error creating sink
'atlas-debug-metrics-context' (MetricsSystemImpl:508)
org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating plugin:
org.apache.hadoop.metrics2.sink.FileSink
at
org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:210)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:531)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:503)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:479)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:188)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:163)
at
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:62)
at
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:58)
at
org.apache.atlas.web.service.DebugMetricsWrapper.init(DebugMetricsWrapper.java:43)
...
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
at
org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:110)
at org.apache.atlas.Atlas.main(Atlas.java:133)
Caused by: org.apache.hadoop.metrics2.MetricsException: Error creating
${atlas.log.dir}/atlas-metrics.out
at org.apache.hadoop.metrics2.sink.FileSink.init(FileSink.java:53)
at
org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:207)
... 63 more
Caused by: java.nio.file.NoSuchFileException: ${atlas.log.dir}/atlas-metrics.out
at
sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at
sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
at
java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
at java.nio.file.Files.newOutputStream(Files.java:216)
at org.apache.hadoop.metrics2.sink.FileSink.init(FileSink.java:50)
... 64 more
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4390) Change the Atlas version at dev-support/atlas-docker/.env
Sidharth Kumar Mishra created ATLAS-4390: Summary: Change the Atlas version at dev-support/atlas-docker/.env Key: ATLAS-4390 URL: https://issues.apache.org/jira/browse/ATLAS-4390 Project: Atlas Issue Type: Sub-task Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra Update the Atlas version at dev-support/atlas-docker/.env to release-2.2.0-rc0 so that docker build would use Atlas sources from this tag -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4385) Update version in branch-2.0 to 2.3.0-SNAPSHOT
Sidharth Kumar Mishra created ATLAS-4385: Summary: Update version in branch-2.0 to 2.3.0-SNAPSHOT Key: ATLAS-4385 URL: https://issues.apache.org/jira/browse/ATLAS-4385 Project: Atlas Issue Type: Sub-task Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4384) Publish release artifacts
[ https://issues.apache.org/jira/browse/ATLAS-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra reassigned ATLAS-4384: Assignee: Sidharth Kumar Mishra > Publish release artifacts > - > > Key: ATLAS-4384 > URL: https://issues.apache.org/jira/browse/ATLAS-4384 > Project: Atlas > Issue Type: Sub-task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4384) Publish release artifacts
Sidharth Kumar Mishra created ATLAS-4384: Summary: Publish release artifacts Key: ATLAS-4384 URL: https://issues.apache.org/jira/browse/ATLAS-4384 Project: Atlas Issue Type: Sub-task Reporter: Sidharth Kumar Mishra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ATLAS-4380) Change pom version from 2.2.0-SNAPSHOT to 2.2.0
[ https://issues.apache.org/jira/browse/ATLAS-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra closed ATLAS-4380. > Change pom version from 2.2.0-SNAPSHOT to 2.2.0 > --- > > Key: ATLAS-4380 > URL: https://issues.apache.org/jira/browse/ATLAS-4380 > Project: Atlas > Issue Type: Task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Update pom version from 2.2.0-SNAPSHOT to 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4383) Update Atlas website for 2.2.0 release
Sidharth Kumar Mishra created ATLAS-4383: Summary: Update Atlas website for 2.2.0 release Key: ATLAS-4383 URL: https://issues.apache.org/jira/browse/ATLAS-4383 Project: Atlas Issue Type: Sub-task Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4382) Change pom version from 2.2.0-SNAPSHOT to 2.2.0
Sidharth Kumar Mishra created ATLAS-4382: Summary: Change pom version from 2.2.0-SNAPSHOT to 2.2.0 Key: ATLAS-4382 URL: https://issues.apache.org/jira/browse/ATLAS-4382 Project: Atlas Issue Type: Sub-task Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra Update pom version from 2.2.0-SNAPSHOT to 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4380) Change pom version from 2.2.0-SNAPSHOT to 2.2.0
[ https://issues.apache.org/jira/browse/ATLAS-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra resolved ATLAS-4380. -- Resolution: Won't Fix > Change pom version from 2.2.0-SNAPSHOT to 2.2.0 > --- > > Key: ATLAS-4380 > URL: https://issues.apache.org/jira/browse/ATLAS-4380 > Project: Atlas > Issue Type: Task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Update pom version from 2.2.0-SNAPSHOT to 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4381) Release Atlas 2.2.0
Sidharth Kumar Mishra created ATLAS-4381: Summary: Release Atlas 2.2.0 Key: ATLAS-4381 URL: https://issues.apache.org/jira/browse/ATLAS-4381 Project: Atlas Issue Type: Task Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra parent task to capture release tasks for Apache Atlas 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4380) Change pom version from 2.2.0-SNAPSHOT to 2.2.0
[ https://issues.apache.org/jira/browse/ATLAS-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra reassigned ATLAS-4380: Assignee: Sidharth Kumar Mishra > Change pom version from 2.2.0-SNAPSHOT to 2.2.0 > --- > > Key: ATLAS-4380 > URL: https://issues.apache.org/jira/browse/ATLAS-4380 > Project: Atlas > Issue Type: Task >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Update pom version from 2.2.0-SNAPSHOT to 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4380) Change pom version from 2.2.0-SNAPSHOT to 2.2.0
Sidharth Kumar Mishra created ATLAS-4380: Summary: Change pom version from 2.2.0-SNAPSHOT to 2.2.0 Key: ATLAS-4380 URL: https://issues.apache.org/jira/browse/ATLAS-4380 Project: Atlas Issue Type: Task Reporter: Sidharth Kumar Mishra Update pom version from 2.2.0-SNAPSHOT to 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4350) Atlas - Jetty Version disclosure in http response
Sidharth Kumar Mishra created ATLAS-4350:
Summary: Atlas - Jetty Version disclosure in http response
Key: ATLAS-4350
URL: https://issues.apache.org/jira/browse/ATLAS-4350
Project: Atlas
Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra
Atlas reveals netty version in http response
{code:java}
GET
https://atlas.host:8443/gateway/cdp-proxy/atlas/js/utils/Overrides.js?bust=1601951148602
{code}
{code:java}
HTTP/1.1 200 OK
Connection: close
Date: Wed, 03 Feb 2021 14:24:28 GMT
Connection: close
Last-Modified: Tue, 06 Oct 2020 04:13:55 GMT Content-Type:
application/javascript Accept-Ranges: bytes
Server: Jetty(9.4.26.v20200117)
Content-Length: 8186
{code}
*Recommendation:* Remove the version information from the http response
header.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4307) Atlas bulk clarification REST should be enhanced to associate classification to bulk entities with uniq attribute and type
[
https://issues.apache.org/jira/browse/ATLAS-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351410#comment-17351410
]
Sidharth Kumar Mishra commented on ATLAS-4307:
--
With the change below three options will work -
Option 1 (Only with type name and list of uniq attributes)
curl --location --request POST
'http://atlas-host:31000/api/atlas/v2/entity/bulk/classification?skipFailedEntities=True'
\
--header 'Authorization: Basic YWRtaW46YWRtaW4xMjM=' \
--header 'Content-Type: application/json' \
--data-raw '{
"classification" : {
"propagate" : false,
"attributes" : {
"type" : "false"
},
"typeName" : "TEST_TAG_TABLE"
},
"entitiesUniqAttributes" : [
\{"qualifiedName": "db1.table43@cm"},
\{"qualifiedName": "db1.table7@cm"},
\{"qualifiedName": "db1.table55@cm"}],
"entityTypeName" : "hive_table"
}'
Option 2 (Only with entity Guids)
curl --location --request POST
'http://atlas-host:31000/api/atlas/v2/entity/bulk/classification?skipFailedEntities=True'
\
--header 'Authorization: Basic YWRtaW46YWRtaW4xMjM=' \
--header 'Content-Type: application/json' \
--data-raw '{
"classification" : {
"propagate" : false,
"attributes" : {
"type" : "false"
},
"typeName" : "TEST_TAG_TABLE"
},
"entityGuids" : ["f7288e81-46e4-4c88-b6c7-da092d6b6e35",
"1793c6df-53a6-481b-a75c-c705f98d6900"],
"entityTypeName" : "hive_table"
}'
Option 3 (With both entity GUIDs and type Name with list of uniq attributes)
curl --location --request POST
'http://atlas-host:31000/api/atlas/v2/entity/bulk/classification?skipFailedEntities=True'
\
--header 'Authorization: Basic YWRtaW46YWRtaW4xMjM=' \
--header 'Content-Type: application/json' \
--data-raw '{
"classification" : {
"propagate" : false,
"attributes" : {
"type" : "false"
},
"typeName" : "TEST_TAG_TABLE"
},
"entitiesUniqAttributes" : [
\{"qualifiedName": "db1.table43@cm"},
\{"qualifiedName": "db1.table8@cm"},
\{"qualifiedName": "db1.table55@cm"}],
"entityGuids" : [
"6d6ab082-9a62-4aea-97b7-2b7337173631",
"9a0d3275-eb42-4229-ac51-6db1ddf3ccc6"],
"entityTypeName" : "hive_table"
}'
> Atlas bulk clarification REST should be enhanced to associate classification
> to bulk entities with uniq attribute and type
> --
>
> Key: ATLAS-4307
> URL: https://issues.apache.org/jira/browse/ATLAS-4307
> Project: Atlas
> Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4307..patch
>
>
> Right now there is no REST to support this. The existing bulk add
> classification takes a list of GUIDs and associates the classification to
> them. The existing one should also take type name and list of unique
> attribute values for entities and tag the classification if it finds entries.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4307) Atlas bulk clarification REST should be enhanced to associate classification to bulk entities with uniq attribute and type
[ https://issues.apache.org/jira/browse/ATLAS-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4307: - Summary: Atlas bulk clarification REST should be enhanced to associate classification to bulk entities with uniq attribute and type (was: Atlas should have REST to add a classification to bulk entities with uniq attribute and type) > Atlas bulk clarification REST should be enhanced to associate classification > to bulk entities with uniq attribute and type > -- > > Key: ATLAS-4307 > URL: https://issues.apache.org/jira/browse/ATLAS-4307 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Right now there is no REST to support this. The existing bulk add > classification takes a list of GUIDs and associates the classification to > them. The existing one should also take type name and list of unique > attribute values for entities and tag the classification if it finds entries. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4307) Atlas should have REST to add a classification to bulk entities with uniq attribute and type
[ https://issues.apache.org/jira/browse/ATLAS-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351395#comment-17351395 ] Sidharth Kumar Mishra commented on ATLAS-4307: -- In case there is no entity found for the specific unique attribute and type and skipFailedEntities flag is not set to True then it will fail even there will be more specified unique attributes for other enttities. If skipFailedEntities = True then it will continue even there are some error for some entity. > Atlas should have REST to add a classification to bulk entities with uniq > attribute and type > > > Key: ATLAS-4307 > URL: https://issues.apache.org/jira/browse/ATLAS-4307 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Right now there is no REST to support this. The existing bulk add > classification takes a list of GUIDs and associates the classification to > them. The existing one should also take type name and list of unique > attribute values for entities and tag the classification if it finds entries. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4307) Atlas should have REST to add a classification to bulk entities with uniq attribute and type
[ https://issues.apache.org/jira/browse/ATLAS-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4307: - Description: Right now there is no REST to support this. The existing bulk add classification takes a list of GUIDs and associates the classification to them. The existing one should also take type name and list of unique attribute values for entities and tag the classification if it finds entries. (was: Right now there is no REST to support this. The existing bulk add classification takes list of GUIDs and associate the classification to them. The new one will take type name and list of uniq attribute values for each entity and tag the classification.) > Atlas should have REST to add a classification to bulk entities with uniq > attribute and type > > > Key: ATLAS-4307 > URL: https://issues.apache.org/jira/browse/ATLAS-4307 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Right now there is no REST to support this. The existing bulk add > classification takes a list of GUIDs and associates the classification to > them. The existing one should also take type name and list of unique > attribute values for entities and tag the classification if it finds entries. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4307) Atlas should have REST to add a classification to bulk entities with uniq attribute and type
[ https://issues.apache.org/jira/browse/ATLAS-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4307: - Description: Right now there is no REST to support this. The existing bulk add classification takes list of GUIDs and associate the classification to them. The new one will take type name and list of uniq attribute values for each entity and tag the classification. > Atlas should have REST to add a classification to bulk entities with uniq > attribute and type > > > Key: ATLAS-4307 > URL: https://issues.apache.org/jira/browse/ATLAS-4307 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Right now there is no REST to support this. The existing bulk add > classification takes list of GUIDs and associate the classification to them. > The new one will take type name and list of uniq attribute values for each > entity and tag the classification. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4307) Atlas should have REST to add a classification to bulk entities with uniq attribute and type
Sidharth Kumar Mishra created ATLAS-4307: Summary: Atlas should have REST to add a classification to bulk entities with uniq attribute and type Key: ATLAS-4307 URL: https://issues.apache.org/jira/browse/ATLAS-4307 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4288) [Atlas: Glossary Term Bulk Import] Will all the data populated, while performing bulk import, PreferredToTerms relationship alone is not created
[
https://issues.apache.org/jira/browse/ATLAS-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346590#comment-17346590
]
Sidharth Kumar Mishra commented on ATLAS-4288:
--
Changed code to take care of preferredToTerms relation when it exists without
any other relations. Below it has also self-reference so now its throwing error
for self reference and then creating the remaining relations successfully.
Check below error messages and response json.
!image-2021-05-17-16-43-31-487.png!
Response json:
{
"failedImportInfoList": [
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_1",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_2",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_3",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_4",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_5",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_6",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_7",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_8",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_9",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_10",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_11",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_12",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_13",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
}
],
"successImportInfoList": [
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_1",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"a83cf35d-22f5-4b4c-8d4f-1d658c85b0ae\",\"qualifiedName\":\"term_1@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_2",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"77d08bd2-9cff-489e-9240-50f2c0f68d89\",\"qualifiedName\":\"term_2@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_3",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"10563ed5-c1fb-438e-bead-b6f0ccbd4d44\",\"qualifiedName\":\"term_3@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_4",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"0f1ec608-4692-4041-b7d4-e270032f2bac\",\"qualifiedName\":\"term_4@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_5",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"30728c5b-99f6-4f69-a54a-2b0d4d49acef\",\"qualifiedName\":\"term_5@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_6",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"b075398a-f845-42ca-90b0-e1362c5757c4\",\"qualifiedName\":\"term_6@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_7",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"0c75f006-9d29-49db-96bb-b9c7738eb155\",\"qualifiedName\":\"term_7@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_8",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"e3cee557-1017-44ed-bfd1-fa42bf9f2b51\",\"qualifiedName\":\"term_8@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_9",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"63635428-a966-4843-b8c8-97576fa349da\",\"qualifiedName\":\"term_9@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_10",
"importStatus": "SUCCESS",
"remarks":
"\{\"termGuid\":\"44cbaf67-9d66-42ad-b339-c97804b5980d\",\"qualifiedName\"
[jira] [Updated] (ATLAS-4288) [Atlas: Glossary Term Bulk Import] Will all the data populated, while performing bulk import, PreferredToTerms relationship alone is not created
[
https://issues.apache.org/jira/browse/ATLAS-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra updated ATLAS-4288:
-
Attachment: image-2021-05-17-16-43-31-487.png
> [Atlas: Glossary Term Bulk Import] Will all the data populated, while
> performing bulk import, PreferredToTerms relationship alone is not created
>
>
> Key: ATLAS-4288
> URL: https://issues.apache.org/jira/browse/ATLAS-4288
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: image-2021-05-17-16-43-31-487.png
>
>
> Consider the following input, here all the relations are established except
> the preferredToTerms (term_2)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms,
> PreferredTermsGlossaryName, TermName, ShortDescription, LongDescription,
> Examples, Abbreviation, Usage, AdditionalAttributes, TranslationTerms,
> ValidValuesFor, Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTermsd
> ,term_1,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_2,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_3,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_4,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_5,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_6,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_7,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_8,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_9,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_10,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_11,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_12,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_13,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"
> {code}
>
> Before the above import happens, please do the initial import of the related
> terms with the following input
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossaryBulkImport_1,termBulkImport_1
> glossaryBulkImport_1,termBulkImport_2
> glossaryBulkImport_1,termBulkImport_3
> glossaryBulkImport_1,termBulkImport_4
> glossaryBulkImport_1,termBulkImport_5
> glossaryBulkImport_2,termBulkImport_1
> glossaryBulkImport_2,termBulkImport_2
> glossaryBulkImport_2,termBulkImport_3
> glossaryBulkImport_2,termBulkImport_4
> glossaryBulkImport_2,termBulkImport_5
> glossaryBulkImport_3,termBulkImport_1
> glossaryBulkImport_3,termBulkImport_2
> g
[jira] [Resolved] (ATLAS-4287) [Atlas: Glossary Term Bulk Import] When there is self-reference in the input, bulk import is broken
[
https://issues.apache.org/jira/browse/ATLAS-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4287.
--
Resolution: Duplicate
> [Atlas: Glossary Term Bulk Import] When there is self-reference in the input,
> bulk import is broken
> ---
>
> Key: ATLAS-4287
> URL: https://issues.apache.org/jira/browse/ATLAS-4287
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> This was working on the previous build before that latest fix, but broken now.
> Scenario 1: Self-reference and Failure (2 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",{code}
> Scenario 2: Self-reference and Success (1 failure expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",
> glossary_1,term_2 {code}
> Scenatio 3: Only self reference (1 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1", {code}
> In all these cases we expect failure message which mentions about self
> reference, this is currently broken.
> What makes this important is, in case of self-reference and success scenario,
> the relationship is not established
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4287) [Atlas: Glossary Term Bulk Import] When there is self-reference in the input, bulk import is broken
[
https://issues.apache.org/jira/browse/ATLAS-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346477#comment-17346477
]
Sidharth Kumar Mishra commented on ATLAS-4287:
--
Before the next import happens, please do the initial import of the related
terms with the following input
{code:java}
GlossaryName, TermName, ShortDescription, LongDescription, Examples,
Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, TranslatedTerms,
IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
glossaryBulkImport_1,termBulkImport_1
glossaryBulkImport_1,termBulkImport_2{code}
Now with the below payload I tested and self-reference gives error message as
expected.
{code:java}
GlossaryName, TermName, ShortDescription, LongDescription, Examples,
Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, TranslatedTerms,
IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
dharshmk_11,term_2,"short desc","long description", "Example", "G1", "Usage",
"glossary:100%","dharshmk_11:term_2|glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_1:termBulkImport_2"{code}
Response as expected:
{
"failedImportInfoList": [
{ "parentObjectName": "dharshmk_11", "childObjectName": "term_2",
"importStatus": "FAILED", "remarks": "Invalid Term relationship: Term cant
have a relationship with self" }
],
"successImportInfoList": [
{ "parentObjectName": "dharshmk_11", "childObjectName": "term_2",
"importStatus": "SUCCESS", "remarks":
"\\{\"termGuid\":\"7e6e4be7-1dc3-43de-8c7b-5f853113e406\",\"qualifiedName\":\"term_2@dharshmk_11\"}
"
}
]
}
For the mentioned csv payload where this doesn't work is due to the fact that
PreferredToTerms relationship doesn't work as filed by
https://issues.apache.org/jira/browse/ATLAS-4288 Jira. So closing this as
duplicate of ATLAS-4288
> [Atlas: Glossary Term Bulk Import] When there is self-reference in the input,
> bulk import is broken
> ---
>
> Key: ATLAS-4287
> URL: https://issues.apache.org/jira/browse/ATLAS-4287
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> This was working on the previous build before that latest fix, but broken now.
> Scenario 1: Self-reference and Failure (2 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",{code}
> Scenario 2: Self-reference and Success (1 failure expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",
> glossary_1,term_2 {code}
> Scenatio 3: Only self reference (1 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1", {code}
> In all these cases we expect failure message which mentions about self
> reference, this is currently broken.
> What makes this important is, in case of self-reference and success scenario,
> the relationship is not established
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4288) [Atlas: Glossary Term Bulk Import] Will all the data populated, while performing bulk import, PreferredToTerms relationship alone is not created
[
https://issues.apache.org/jira/browse/ATLAS-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-4288:
Assignee: Sidharth Kumar Mishra
> [Atlas: Glossary Term Bulk Import] Will all the data populated, while
> performing bulk import, PreferredToTerms relationship alone is not created
>
>
> Key: ATLAS-4288
> URL: https://issues.apache.org/jira/browse/ATLAS-4288
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Consider the following input, here all the relations are established except
> the preferredToTerms (term_2)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms,
> PreferredTermsGlossaryName, TermName, ShortDescription, LongDescription,
> Examples, Abbreviation, Usage, AdditionalAttributes, TranslationTerms,
> ValidValuesFor, Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTermsd
> ,term_1,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_2,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_3,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_4,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_5,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_6,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_7,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_8,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_9,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_10,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_11,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_12,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_13,"short
> desc","long description", "Example", "G1", "Usage",
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"
> {code}
>
> Before the above import happens, please do the initial import of the related
> terms with the following input
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossaryBulkImport_1,termBulkImport_1
> glossaryBulkImport_1,termBulkImport_2
> glossaryBulkImport_1,termBulkImport_3
> glossaryBulkImport_1,termBulkImport_4
> glossaryBulkImport_1,termBulkImport_5
> glossaryBulkImport_2,termBulkImport_1
> glossaryBulkImport_2,termBulkImport_2
> glossaryBulkImport_2,termBulkImport_3
> glossaryBulkImport_2,termBulkImport_4
> glossaryBulkImport_2,termBulkImport_5
> glossaryBulkImport_3,termBulkImport_1
> glossaryBulkImport_3,termBulkImport_2
> glossaryBulkImport_3,termBulkImport_3
> glossaryBulkImport_3,termBu
[jira] [Assigned] (ATLAS-4287) [Atlas: Glossary Term Bulk Import] When there is self-reference in the input, bulk import is broken
[
https://issues.apache.org/jira/browse/ATLAS-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-4287:
Assignee: Sidharth Kumar Mishra
> [Atlas: Glossary Term Bulk Import] When there is self-reference in the input,
> bulk import is broken
> ---
>
> Key: ATLAS-4287
> URL: https://issues.apache.org/jira/browse/ATLAS-4287
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> This was working on the previous build before that latest fix, but broken now.
> Scenario 1: Self-reference and Failure (2 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",{code}
> Scenario 2: Self-reference and Success (1 failure expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",
> glossary_1,term_2 {code}
> Scenatio 3: Only self reference (1 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1", {code}
> In all these cases we expect failure message which mentions about self
> reference, this is currently broken.
> What makes this important is, in case of self-reference and success scenario,
> the relationship is not established
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4273) [Atlas: Glossary Term Bulk Import] When there is only 1 term imported via bulk import and if it fails, no proper reason is mentioned in response
[
https://issues.apache.org/jira/browse/ATLAS-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4273.
--
Resolution: Won't Fix
> [Atlas: Glossary Term Bulk Import] When there is only 1 term imported via
> bulk import and if it fails, no proper reason is mentioned in response
>
>
> Key: ATLAS-4273
> URL: https://issues.apache.org/jira/browse/ATLAS-4273
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> The following fails as we do not support @ in term name
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_l,term_@_1 {code}
> But the failure is
> {code:java}
> {"errorCode":"ATLAS-409-00-011","errorMessage":"Glossary import failed"}
> {code}
> The code is 409 which mean a conflict but the reason is different
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4275) [Atlas: Glossary Term Bulk Import] When there an incorrect data in preferred term column, it is not considered while importing
[
https://issues.apache.org/jira/browse/ATLAS-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra resolved ATLAS-4275.
--
Resolution: Duplicate
> [Atlas: Glossary Term Bulk Import] When there an incorrect data in preferred
> term column, it is not considered while importing
> --
>
> Key: ATLAS-4275
> URL: https://issues.apache.org/jira/browse/ATLAS-4275
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
>
> When there is an error in the PreferredTerms of the input, error is not
> considered
> Consider the following input. Here the provided term "abcd:efgh" does not
> exists in the system.
> The error is thrown when it is provided as an input for "*PreferredToTerms*"
> column but not for "*PreferredTerms*" column
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> dharsh,term_1,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%","abcd:efgh"
> dharsh,term_2,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%""abcd:efgh", {code}
>
> *Expectation:*
> 2 failed message info should be thrown one for term_1(incorrect
> PreferredTerms) and the other for term_2(incorrect PreferredToTerms), but
> only 1 is thrown
>
> *Current output:*
> {code:java}
> {
> "failedImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "FAILED",
> "remarks": "The provided Reference efgh@abcd does not exist at Atlas
> referred at record with TermName : term_2 and GlossaryName : dharsh"
> }
> ],
> "successImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_1",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"284fe9a7-911c-423a-90bf-adf8231afb27\",\"qualifiedName\":\"term_1@dharsh\"}"
> },
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"29a51c8a-ce92-4988-8fca-feaf683c58dd\",\"qualifiedName\":\"term_2@dharsh\"}"
> }
> ]
> } {code}
>
> *Expected output:*
> {code:java}
> {
> "failedImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_1",
> "importStatus": "FAILED",
> "remarks": "The provided Reference efgh@abcd does not exist at Atlas
> referred at record with TermName : term_1 and GlossaryName : dharsh"
> },
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "FAILED",
> "remarks": "The provided Reference efgh@abcd does not exist at Atlas
> referred at record with TermName : term_2 and GlossaryName : dharsh"
> }
> ],
> "successImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_1",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"284fe9a7-911c-423a-90bf-adf8231afb27\",\"qualifiedName\":\"term_1@dharsh\"}"
> },
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"29a51c8a-ce92-4988-8fca-feaf683c58dd\",\"qualifiedName\":\"term_2@dharsh\"}"
> }
> ]
> } {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4274) [Atlas: Glossary] Non matching relation are created via bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-4274:
Assignee: Sidharth Kumar Mishra
> [Atlas: Glossary] Non matching relation are created via bulk import
> ---
>
> Key: ATLAS-4274
> URL: https://issues.apache.org/jira/browse/ATLAS-4274
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-05-04 at 3.31.00 PM.png, Screenshot
> 2021-05-04 at 3.34.03 PM.png, Screenshot 2021-05-04 at 3.34.21 PM.png,
> Screenshot 2021-05-04 at 3.34.36 PM.png
>
>
> The related terms provided in the input does not match the relation created
> via import
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> a_glossary_1,term_1,,,"a_glossary_1:term_2"
> a_glossary_1,term_2,"a_glossary_1:term_3",,
> a_glossary_1,term_3,,"a_glossary_1:term_1", {code}
> !Screenshot 2021-05-04 at 3.31.00 PM.png|width=1973,height=127!
> !Screenshot 2021-05-04 at 3.34.03 PM.png|width=1038,height=578!
> !Screenshot 2021-05-04 at 3.34.21 PM.png|width=1005,height=563!
> !Screenshot 2021-05-04 at 3.34.36 PM.png|width=541,height=303!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4272) [Atlas: Glossary Term Bulk Import] Re-importing after deleting a glossary fails
[
https://issues.apache.org/jira/browse/ATLAS-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra reassigned ATLAS-4272:
Assignee: Sidharth Kumar Mishra
> [Atlas: Glossary Term Bulk Import] Re-importing after deleting a glossary
> fails
>
>
> Key: ATLAS-4272
> URL: https://issues.apache.org/jira/browse/ATLAS-4272
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Scenario: Import a glossary, after import delete the glossary and its terms
> and reimport the same input
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> abc_glossary,term_1
> abc_glossary,term_2
> abc_glossary,term_3{code}
> This throws the following error
> {code:java}
> errorCode: "ATLAS-404-00-005",
> errorMessage: "Given instance guid 6363d630-a96e-4c15-a3ae-d4812dd67aa2 is
> invalid/not found" {code}
> {code:java}
> 2021-05-03 13:33:43,562 ERROR - [etp813603842-30 -
> 8f83ce44-0c56-4224-9f57-8211b3435b2e:] ~ graph rollback due to exception
> AtlasBaseException:Given instance guid 45163be7-377a-4b74-b977-75fa5a4b5a2e
> is invalid/not found (GraphTransactionInterceptor:202)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4261) Bulk Glossary Import Response and Failed Error Message Improvements
[ https://issues.apache.org/jira/browse/ATLAS-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4261: - Description: 1. For bulk glossary import, if we have relations and there is some error present then the failed error message contains duplicate messages. 2. The success response doesn't contains information about the relations 3. The failed messages at response contains extra '\n' > Bulk Glossary Import Response and Failed Error Message Improvements > > > Key: ATLAS-4261 > URL: https://issues.apache.org/jira/browse/ATLAS-4261 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > 1. For bulk glossary import, if we have relations and there is some error > present then the failed error message contains duplicate messages. > 2. The success response doesn't contains information about the relations > 3. The failed messages at response contains extra '\n' > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4261) Bulk Glossary Import Response and Failed Error Message Improvements
Sidharth Kumar Mishra created ATLAS-4261: Summary: Bulk Glossary Import Response and Failed Error Message Improvements Key: ATLAS-4261 URL: https://issues.apache.org/jira/browse/ATLAS-4261 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4231) UI: Create icons for new entity types for Google Cloud Storage
[ https://issues.apache.org/jira/browse/ATLAS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312633#comment-17312633 ] Sidharth Kumar Mishra commented on ATLAS-4231: -- Thanks [~prasadpp13]. It would be good to include Google Cloud Storage inside the icon to make it consistent with AWS S3 and ADLS Gen 2. > UI: Create icons for new entity types for Google Cloud Storage > -- > > Key: ATLAS-4231 > URL: https://issues.apache.org/jira/browse/ATLAS-4231 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Sidharth Kumar Mishra >Assignee: Sameer Shaikh >Priority: Major > Labels: entity-icons > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4231-UI-Create-icons-for-new-entity-types-for-.patch > > > The model changes are part of ATLAS-4226 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4226) Add model types for Google cloud platform
[ https://issues.apache.org/jira/browse/ATLAS-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312619#comment-17312619 ] Sidharth Kumar Mishra commented on ATLAS-4226: -- !image.png! > Add model types for Google cloud platform > -- > > Key: ATLAS-4226 > URL: https://issues.apache.org/jira/browse/ATLAS-4226 > Project: Atlas > Issue Type: Improvement >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Attachments: ATLAS-4226_2.patch, image.png > > > Right now Atlas has no entity type for gcp paths. We should have the all the > types like bucket, object, virtual directory etc. for google cloud storage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4226) Add model types for Google cloud platform
[ https://issues.apache.org/jira/browse/ATLAS-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-4226: - Attachment: image.png > Add model types for Google cloud platform > -- > > Key: ATLAS-4226 > URL: https://issues.apache.org/jira/browse/ATLAS-4226 > Project: Atlas > Issue Type: Improvement >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Attachments: ATLAS-4226_2.patch, image.png > > > Right now Atlas has no entity type for gcp paths. We should have the all the > types like bucket, object, virtual directory etc. for google cloud storage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4231) UI: Create icons for new entity types for Google Cloud Storage
[ https://issues.apache.org/jira/browse/ATLAS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311867#comment-17311867 ] Sidharth Kumar Mishra commented on ATLAS-4231: -- cc: [~jayendrap] > UI: Create icons for new entity types for Google Cloud Storage > -- > > Key: ATLAS-4231 > URL: https://issues.apache.org/jira/browse/ATLAS-4231 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sameer Shaikh >Priority: Major > > The model changes are part of ATLAS-4226 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4231) UI: Create icons for new entity types for Google Cloud Storage
[ https://issues.apache.org/jira/browse/ATLAS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra reassigned ATLAS-4231: Assignee: Sameer Shaikh > UI: Create icons for new entity types for Google Cloud Storage > -- > > Key: ATLAS-4231 > URL: https://issues.apache.org/jira/browse/ATLAS-4231 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sameer Shaikh >Priority: Major > > The model changes are part of ATLAS-4226 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4231) UI: Create icons for new entity types for Google Cloud Storage
Sidharth Kumar Mishra created ATLAS-4231: Summary: UI: Create icons for new entity types for Google Cloud Storage Key: ATLAS-4231 URL: https://issues.apache.org/jira/browse/ATLAS-4231 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra The model changes are part of ATLAS-4226 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4230) Create new entity for Google cloud storage location from hive
Sidharth Kumar Mishra created ATLAS-4230: Summary: Create new entity for Google cloud storage location from hive Key: ATLAS-4230 URL: https://issues.apache.org/jira/browse/ATLAS-4230 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra When I try to run the below create command at hive with GCP cloud configured - create external table hive_table_cloud_external_test1 (student_roll int, student_name string, student_dob date); We see a hdfs path entity - gs://gcp-daily-test/testdir1/hiveurltests Instead we should have a Google cloud storage directory entity and bucket entity created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4227) Remove aws_s3_v2_directory.objectPrefix uniqueness
Sidharth Kumar Mishra created ATLAS-4227: Summary: Remove aws_s3_v2_directory.objectPrefix uniqueness Key: ATLAS-4227 URL: https://issues.apache.org/jira/browse/ATLAS-4227 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra For aws_s3_v2_directory.objectPrefix, the isUnique property is true. based on the test here: (see verifyS3V2PseudoDir) [https://github.com/apache/atlas/blob/d27790dfdde09a58db15064bbdaf77d224f61ecc/common/src/test/java/org/apache/atlas/utils/AtlasPathExtractorUtilTest.java] if we have 2 AWS S3 files from different buckets: # s3://aws_my_bucket*1/1234567890/test.csv* # s3://aws_my_bucket*2/1234567890/test.csv* as you see there is 2 different directories from different buckets, but having same objectPrefix, and different qualified name. object 1: aws_s3_v2_directory: qualifiedName: "s3://*aws_my_bucket1*/1234567890/" objectPrefix: "/1234567890/" object 2: aws_s3_v2_directory: qualifiedName: "s3://*aws_my_bucket2*/1234567890/" objectPrefix: "/1234567890/" So we should remove uniqueness -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4226) Add model types for Google cloud platform
Sidharth Kumar Mishra created ATLAS-4226: Summary: Add model types for Google cloud platform Key: ATLAS-4226 URL: https://issues.apache.org/jira/browse/ATLAS-4226 Project: Atlas Issue Type: Improvement Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra Right now Atlas has no entity type for gcp paths. We should have the all the types like bucket, object, virtual directory etc. for google cloud storage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4191) Creation of relations does not work for glossary import
Sidharth Kumar Mishra created ATLAS-4191: Summary: Creation of relations does not work for glossary import Key: ATLAS-4191 URL: https://issues.apache.org/jira/browse/ATLAS-4191 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra Attachments: Atlas BG template - smallish.csv When importing glossary data in CSV format, any relations within the imported data lead to an error; import can only find referenced Terms that already exist in Atlas. Example: Term GA -> T1 has a 'seeAlso' relation to GA -> T2 and vice versa. (See also attached CSV file) This makes using relations with larger glossaries almost impossible to use: there will be circular references (as with 'seeAlso'), so even a two-step approach to import will not work. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4170) v2/entity/bulk Entity GET API is able to read unauthorised entities too when skipFailedEntities is passed as True
[
https://issues.apache.org/jira/browse/ATLAS-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra updated ATLAS-4170:
-
Attachment: (was: ATLAS-4170.patch)
> v2/entity/bulk Entity GET API is able to read unauthorised entities too when
> skipFailedEntities is passed as True
> -
>
> Key: ATLAS-4170
> URL: https://issues.apache.org/jira/browse/ATLAS-4170
> Project: Atlas
> Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4170.patch
>
>
> As part of https://issues.apache.org/jira/browse/ATLAS-3855,
> skipFailedEntities was introduced to ignore the entities where it fails to
> read
> When skipFailedEntities is not passed or is passed as
> skipFailedEntities=False, then we get 403 with below error as expected
> {code:java}
> {
> "errorCode": "ATLAS-403-00-001",
> "errorMessage": "hrt is not authorized to perform read entity:
> guid=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c"
> } {code}
> But when we pass skipFailedEntities=True, then API is able to retrieve the
> data for even those entities on which the user has explicit deny conditions.
> Ideally, we should be ignoring these unauthorised entities and return data
> only for authorised ones.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4170) v2/entity/bulk Entity GET API is able to read unauthorised entities too when skipFailedEntities is passed as True
[
https://issues.apache.org/jira/browse/ATLAS-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra updated ATLAS-4170:
-
Attachment: ATLAS-4170.patch
> v2/entity/bulk Entity GET API is able to read unauthorised entities too when
> skipFailedEntities is passed as True
> -
>
> Key: ATLAS-4170
> URL: https://issues.apache.org/jira/browse/ATLAS-4170
> Project: Atlas
> Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4170.patch
>
>
> As part of https://issues.apache.org/jira/browse/ATLAS-3855,
> skipFailedEntities was introduced to ignore the entities where it fails to
> read
> When skipFailedEntities is not passed or is passed as
> skipFailedEntities=False, then we get 403 with below error as expected
> {code:java}
> {
> "errorCode": "ATLAS-403-00-001",
> "errorMessage": "hrt is not authorized to perform read entity:
> guid=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c"
> } {code}
> But when we pass skipFailedEntities=True, then API is able to retrieve the
> data for even those entities on which the user has explicit deny conditions.
> Ideally, we should be ignoring these unauthorised entities and return data
> only for authorised ones.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4170) v2/entity/bulk Entity GET API is able to read unauthorised entities too when skipFailedEntities is passed as True
Sidharth Kumar Mishra created ATLAS-4170:
Summary: v2/entity/bulk Entity GET API is able to read
unauthorised entities too when skipFailedEntities is passed as True
Key: ATLAS-4170
URL: https://issues.apache.org/jira/browse/ATLAS-4170
Project: Atlas
Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra
As part of https://issues.apache.org/jira/browse/ATLAS-3855, skipFailedEntities
was introduced to ignore the entities where it fails to read
When skipFailedEntities is not passed or is passed as skipFailedEntities=False,
then we get 403 with below error as expected
{code:java}
{
"errorCode": "ATLAS-403-00-001",
"errorMessage": "hrt is not authorized to perform read entity:
guid=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c"
} {code}
But when we pass skipFailedEntities=True, then API is able to retrieve the data
for even those entities on which the user has explicit deny conditions.
Ideally, we should be ignoring these unauthorised entities and return data only
for authorised ones.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4126) Rewrite enable value is not present at Atlas for Materialized View metadata
[ https://issues.apache.org/jira/browse/ATLAS-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra reassigned ATLAS-4126: Assignee: Sidharth Kumar Mishra > Rewrite enable value is not present at Atlas for Materialized View metadata > --- > > Key: ATLAS-4126 > URL: https://issues.apache.org/jira/browse/ATLAS-4126 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Repro steps: > create table test_1 (id integer); > CREATE MATERIALIZED VIEW test_mv_ctas_1 as select * from test_1; > ALTER MATERIALIZED VIEW test_mv_ctas_1 enable rewrite; > After this go to Atlas and see the Rewrite enable value is not present at > Atlas for the Materialized View entity test_mv_ctas_1 > [https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.5/materialized-view/content/hive_alter_materialized_view_rewrite.html] > Even checked parameters like transient_lastDdlTime is not getting populated > at hive_table of type MATERIALIZED_VIEW -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4126) Rewrite enable value is not present at Atlas for Materialized View metadata
Sidharth Kumar Mishra created ATLAS-4126: Summary: Rewrite enable value is not present at Atlas for Materialized View metadata Key: ATLAS-4126 URL: https://issues.apache.org/jira/browse/ATLAS-4126 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Repro steps: create table test_1 (id integer); CREATE MATERIALIZED VIEW test_mv_ctas_1 as select * from test_1; ALTER MATERIALIZED VIEW test_mv_ctas_1 enable rewrite; After this go to Atlas and see the Rewrite enable value is not present at Atlas for the Materialized View entity test_mv_ctas_1 [https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.5/materialized-view/content/hive_alter_materialized_view_rewrite.html] Even checked parameters like transient_lastDdlTime is not getting populated at hive_table of type MATERIALIZED_VIEW -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4123) Lineage missing in case of CREATE MATERIALIZED VIEW query at Hive
Sidharth Kumar Mishra created ATLAS-4123: Summary: Lineage missing in case of CREATE MATERIALIZED VIEW query at Hive Key: ATLAS-4123 URL: https://issues.apache.org/jira/browse/ATLAS-4123 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Issue: At hive run the below queries: create table test_1 (id integer); CREATE MATERIALIZED VIEW test_mv_ctas_1 as select * from test_1; Expected behaviour: At Atlas we should have the lineage created between hive_table entity test_1 and test_mv_ctas_1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4123) Lineage missing in case of CREATE MATERIALIZED VIEW query at Hive
[ https://issues.apache.org/jira/browse/ATLAS-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra reassigned ATLAS-4123: Assignee: Sidharth Kumar Mishra > Lineage missing in case of CREATE MATERIALIZED VIEW query at Hive > - > > Key: ATLAS-4123 > URL: https://issues.apache.org/jira/browse/ATLAS-4123 > Project: Atlas > Issue Type: Bug >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > Issue: > At hive run the below queries: > create table test_1 (id integer); > CREATE MATERIALIZED VIEW test_mv_ctas_1 as select * from test_1; > Expected behaviour: > At Atlas we should have the lineage created between hive_table entity test_1 > and test_mv_ctas_1 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4099) adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory created by Hook
[
https://issues.apache.org/jira/browse/ATLAS-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra updated ATLAS-4099:
-
Attachment: ATLAS-4099-Removed-slash-from-adls_gen2_directory_2.patch
> adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory
> created by Hook
>
>
> Key: ATLAS-4099
> URL: https://issues.apache.org/jira/browse/ATLAS-4099
> Project: Atlas
> Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4099-Removed-slash-from-adls_gen2_directory_2.patch
>
>
> For the query :
> {code:java}
> create external table ext_table(id int) location
> 'abfs://contai...@storageaccount.dfs.core.windows.net/test51' {code}
> adls_gen2_directory created by Hook has QualifiedName :
> *abfs://container@storageaccount/test51/@cm*
> whereas , adls_gen2_directory created by Extractor has QualifiedName:
> *abfs://**container@storageaccount/test51**@cm*
> There is an extra "/" after storage account name which causes issue. Because
> of this , duplicate entities are created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4099) adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory created by Hook
[
https://issues.apache.org/jira/browse/ATLAS-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharth Kumar Mishra updated ATLAS-4099:
-
Attachment: (was:
ATLAS-4099-Removed-slash-from-adls_gen2_directory.patch)
> adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory
> created by Hook
>
>
> Key: ATLAS-4099
> URL: https://issues.apache.org/jira/browse/ATLAS-4099
> Project: Atlas
> Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4099-Removed-slash-from-adls_gen2_directory_2.patch
>
>
> For the query :
> {code:java}
> create external table ext_table(id int) location
> 'abfs://contai...@storageaccount.dfs.core.windows.net/test51' {code}
> adls_gen2_directory created by Hook has QualifiedName :
> *abfs://container@storageaccount/test51/@cm*
> whereas , adls_gen2_directory created by Extractor has QualifiedName:
> *abfs://**container@storageaccount/test51**@cm*
> There is an extra "/" after storage account name which causes issue. Because
> of this , duplicate entities are created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4099) adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory created by Hook
Sidharth Kumar Mishra created ATLAS-4099:
Summary: adls_gen2_directory, Hive Hook : An extra "/" is seen in
adls_gen2_directory created by Hook
Key: ATLAS-4099
URL: https://issues.apache.org/jira/browse/ATLAS-4099
Project: Atlas
Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra
For the query :
{code:java}
create external table ext_table(id int) location
'abfs://contai...@storageaccount.dfs.core.windows.net/test51' {code}
adls_gen2_directory created by Hook has QualifiedName :
*abfs://container@storageaccount/test51/@cm*
whereas , adls_gen2_directory created by Extractor has QualifiedName:
*abfs://**container@storageaccount/test51**@cm*
There is an extra "/" after storage account name which causes issue. Because of
this , duplicate entities are created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4083) Change the existing ADLS Gen2 type with new attributes
[ https://issues.apache.org/jira/browse/ATLAS-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra reassigned ATLAS-4083: Assignee: Sidharth Kumar Mishra > Change the existing ADLS Gen2 type with new attributes > -- > > Key: ATLAS-4083 > URL: https://issues.apache.org/jira/browse/ATLAS-4083 > Project: Atlas > Issue Type: Improvement >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > We should change the existing ADLS Gen2 type with new attributes as per the > 005-azure_adls_add_attributes.json patch -- This message was sent by Atlassian Jira (v8.3.4#803005)
