[jira] [Updated] (ATLAS-2458) RelationshipApi Delete doesnt remove relationshipAttributes from entity
[
https://issues.apache.org/jira/browse/ATLAS-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapildeo Nayak updated ATLAS-2458:
--
Attachment: ATLAS-2458.patch
> RelationshipApi Delete doesnt remove relationshipAttributes from entity
> ---
>
> Key: ATLAS-2458
> URL: https://issues.apache.org/jira/browse/ATLAS-2458
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Brandon Kirchner
>Assignee: Kapildeo Nayak
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2458.patch
>
>
> When I create a Process and DataSet entity, and create a
> process_dataset_outputs relationship between the two, when I delete the
> relationship, the relationshipAttributes are not removed from the Process or
> DataSet entities. full reproduction steps and output are below --
>
> step 1 -- create dataset and process (through UI)
> step 2 -- create relationship
> http post http://localhost:21000/api/atlas/v2/relationship
> PAYLOAD
> {
> "end1" : {
> "guid" : "d456dc93-8832-4a36-8ae0-071946c653fc"
> },
> "end2" : {
> "guid" : "247bc2d1-de27-4c50-a35b-b62350dc7979"
> },
> "typeName":"process_dataset_outputs"
> }
> RESPONSE
> {
> "createTime": 1519335073389,
> "createdBy": "admin",
> "end1": {
> "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
> "typeName": "Process"
> },
> "end2": {
> "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
> "typeName": "DataSet"
> },
> "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "label": "__Process.outputs",
> "propagateTags": "ONE_TO_TWO",
> "status": "ACTIVE",
> "typeName": "process_dataset_outputs",
> "updateTime": 1519335073389,
> "updatedBy": "admin",
> "version": 0
> }
> step 3 -- verify relationship on entities
> http get
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
> "entity": {
> "attributes": {
> "description": null,
> "name": "dataset",
> "owner": null,
> "qualifiedName": "dataset"
> },
> "classifications": [],
> "createTime": 1519334042139,
> "createdBy": "admin",
> "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
> "relationshipAttributes": {
> "sinkFromProcesses": [
> {
> "displayText": "process",
> "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
> "relationshipAttributes": {
> "typeName": "process_dataset_outputs"
> },
> "relationshipGuid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "typeName": "Process"
> }
> ],
> "sourceToProcesses": []
> },
> "status": "ACTIVE",
> "typeName": "DataSet",
> "updateTime": 1519334042139,
> "updatedBy": "admin",
> "version": 0
> },
> "referredEntities": {}
> }
> http get
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
> "entity": {
> "attributes": {
> "description": null,
> "name": "dataset",
> "owner": null,
> "qualifiedName": "dataset"
> },
> "classifications": [],
> "createTime": 1519334042139,
> "createdBy": "admin",
> "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
> "relationshipAttributes": {
> "sinkFromProcesses": [
> {
> "displayText": "process",
> "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
> "relationshipAttributes": {
> "typeName": "process_dataset_outputs"
> },
> "relationshipGuid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "typeName": "Process"
> }
> ],
> "sourceToProcesses": []
> },
> "status": "ACTIVE",
> "typeName": "DataSet",
> "updateTime": 1519334042139,
> "updatedBy": "admin",
> "version": 0
> },
> "referredEntities": {}
> }
> step 4 -- delete relationship
> http delete
> http://localhost:21000/api/atlas/v2/relationship/guid/bb9dfa43-c193-4cbb-9472-6b9421f43701
> HTTP/1.1 204 No Content
> step 5 -- verify deletion
> http get
> http://localhost:21000/api/atlas/v2/relationship/guid/bb9dfa43-c193-4cbb-9472-6b9421f43701
> HTTP/1.1 200 OK
> {
> "createTime": 1519334256264,
> "createdBy": "admin",
> "end1": {
> "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "typeName": "Process"
> },
> "end2": {
> "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
> "typeName": "DataSet"
> },
> "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "label": "__Process.outputs",
> "propagateTags": "ONE_TO_TWO",
> "status": "DELETED",
> "typeName": "process_dataset_outputs",
> "updateTime": 1519334383683,
> "updatedBy": "admin",
> "version": 0
> }
> step 6 -- verify relationship removed from entities (FAILS)
> http get
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
> "entity": {
> "attributes": {
> "description": null,
> "name": "dataset",
> "owner": null,
> "qualifiedName": "dataset"
> },
> "classifications": [],
> "createTime": 1519334042139,
> "createdBy": "admin",
> "guid":
[jira] [Assigned] (ATLAS-2458) RelationshipApi Delete doesnt remove relationshipAttributes from entity
[
https://issues.apache.org/jira/browse/ATLAS-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapildeo Nayak reassigned ATLAS-2458:
-
Assignee: Kapildeo Nayak
> RelationshipApi Delete doesnt remove relationshipAttributes from entity
> ---
>
> Key: ATLAS-2458
> URL: https://issues.apache.org/jira/browse/ATLAS-2458
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Brandon Kirchner
>Assignee: Kapildeo Nayak
>Priority: Major
> Fix For: 1.0.0
>
>
> When I create a Process and DataSet entity, and create a
> process_dataset_outputs relationship between the two, when I delete the
> relationship, the relationshipAttributes are not removed from the Process or
> DataSet entities. full reproduction steps and output are below --
>
> step 1 -- create dataset and process (through UI)
> step 2 -- create relationship
> http post http://localhost:21000/api/atlas/v2/relationship
> PAYLOAD
> {
> "end1" : {
> "guid" : "d456dc93-8832-4a36-8ae0-071946c653fc"
> },
> "end2" : {
> "guid" : "247bc2d1-de27-4c50-a35b-b62350dc7979"
> },
> "typeName":"process_dataset_outputs"
> }
> RESPONSE
> {
> "createTime": 1519335073389,
> "createdBy": "admin",
> "end1": {
> "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
> "typeName": "Process"
> },
> "end2": {
> "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
> "typeName": "DataSet"
> },
> "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "label": "__Process.outputs",
> "propagateTags": "ONE_TO_TWO",
> "status": "ACTIVE",
> "typeName": "process_dataset_outputs",
> "updateTime": 1519335073389,
> "updatedBy": "admin",
> "version": 0
> }
> step 3 -- verify relationship on entities
> http get
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
> "entity": {
> "attributes": {
> "description": null,
> "name": "dataset",
> "owner": null,
> "qualifiedName": "dataset"
> },
> "classifications": [],
> "createTime": 1519334042139,
> "createdBy": "admin",
> "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
> "relationshipAttributes": {
> "sinkFromProcesses": [
> {
> "displayText": "process",
> "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
> "relationshipAttributes": {
> "typeName": "process_dataset_outputs"
> },
> "relationshipGuid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "typeName": "Process"
> }
> ],
> "sourceToProcesses": []
> },
> "status": "ACTIVE",
> "typeName": "DataSet",
> "updateTime": 1519334042139,
> "updatedBy": "admin",
> "version": 0
> },
> "referredEntities": {}
> }
> http get
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
> "entity": {
> "attributes": {
> "description": null,
> "name": "dataset",
> "owner": null,
> "qualifiedName": "dataset"
> },
> "classifications": [],
> "createTime": 1519334042139,
> "createdBy": "admin",
> "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
> "relationshipAttributes": {
> "sinkFromProcesses": [
> {
> "displayText": "process",
> "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
> "relationshipAttributes": {
> "typeName": "process_dataset_outputs"
> },
> "relationshipGuid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "typeName": "Process"
> }
> ],
> "sourceToProcesses": []
> },
> "status": "ACTIVE",
> "typeName": "DataSet",
> "updateTime": 1519334042139,
> "updatedBy": "admin",
> "version": 0
> },
> "referredEntities": {}
> }
> step 4 -- delete relationship
> http delete
> http://localhost:21000/api/atlas/v2/relationship/guid/bb9dfa43-c193-4cbb-9472-6b9421f43701
> HTTP/1.1 204 No Content
> step 5 -- verify deletion
> http get
> http://localhost:21000/api/atlas/v2/relationship/guid/bb9dfa43-c193-4cbb-9472-6b9421f43701
> HTTP/1.1 200 OK
> {
> "createTime": 1519334256264,
> "createdBy": "admin",
> "end1": {
> "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "typeName": "Process"
> },
> "end2": {
> "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
> "typeName": "DataSet"
> },
> "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
> "label": "__Process.outputs",
> "propagateTags": "ONE_TO_TWO",
> "status": "DELETED",
> "typeName": "process_dataset_outputs",
> "updateTime": 1519334383683,
> "updatedBy": "admin",
> "version": 0
> }
> step 6 -- verify relationship removed from entities (FAILS)
> http get
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
> "entity": {
> "attributes": {
> "description": null,
> "name": "dataset",
> "owner": null,
> "qualifiedName": "dataset"
> },
> "classifications": [],
> "createTime": 1519334042139,
> "createdBy": "admin",
> "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>
[jira] [Updated] (ATLAS-3032) Importing an entity with tag attribute of type float data type fails with an BigDecimal Exception
[ https://issues.apache.org/jira/browse/ATLAS-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-3032: -- Attachment: ATLAS-3032.patch > Importing an entity with tag attribute of type float data type fails with an > BigDecimal Exception > - > > Key: ATLAS-3032 > URL: https://issues.apache.org/jira/browse/ATLAS-3032 > Project: Atlas > Issue Type: Bug >Reporter: Kapildeo Nayak >Priority: Critical > Attachments: ATLAS-3032.patch > > > 1. In source cluster , created a tag with float attribute. > 2. Created an hive_db and associated the tag to the hive_db with value > "-3.4028235E+38" > 3. On importing the exported hive_db entity, exception is seen and import > fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3032) Importing an entity with tag attribute of type float data type fails with an BigDecimal Exception
Kapildeo Nayak created ATLAS-3032: - Summary: Importing an entity with tag attribute of type float data type fails with an BigDecimal Exception Key: ATLAS-3032 URL: https://issues.apache.org/jira/browse/ATLAS-3032 Project: Atlas Issue Type: Bug Reporter: Kapildeo Nayak 1. In source cluster , created a tag with float attribute. 2. Created an hive_db and associated the tag to the hive_db with value "-3.4028235E+38" 3. On importing the exported hive_db entity, exception is seen and import fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3024) On hive_db rename few attributes are still not renamed after successful import
[
https://issues.apache.org/jira/browse/ATLAS-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapildeo Nayak updated ATLAS-3024:
--
Attachment: ATLAS-3024.patch
> On hive_db rename few attributes are still not renamed after successful import
> --
>
> Key: ATLAS-3024
> URL: https://issues.apache.org/jira/browse/ATLAS-3024
> Project: Atlas
> Issue Type: Bug
>Reporter: Kapildeo Nayak
>Priority: Major
> Attachments: ATLAS-3024.patch
>
>
> # Created a database db9 with a table and external table and exported it.
> # On Importing , renamed it to db11 using :
> {\"conditions\":{\"hive_db.name\":\"EQUALS:
> db9\"},\"action\":{\"hive_db.name\":\"SET: db11\"}}]"
> 3. Attributes related to hive_db location, hive_storagedesc location
> and attributes of hive_process and hdfs_path are not renamed and have db9
> reference still.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-3024) On hive_db rename few attributes are still not renamed after successful import
[
https://issues.apache.org/jira/browse/ATLAS-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapildeo Nayak updated ATLAS-3024:
--
Attachment: (was:
0001-BUG-111658-hive_db-rename-few-attributes-are-still-n.patch)
> On hive_db rename few attributes are still not renamed after successful import
> --
>
> Key: ATLAS-3024
> URL: https://issues.apache.org/jira/browse/ATLAS-3024
> Project: Atlas
> Issue Type: Bug
>Reporter: Kapildeo Nayak
>Priority: Major
> Attachments: ATLAS-3024.patch
>
>
> # Created a database db9 with a table and external table and exported it.
> # On Importing , renamed it to db11 using :
> {\"conditions\":{\"hive_db.name\":\"EQUALS:
> db9\"},\"action\":{\"hive_db.name\":\"SET: db11\"}}]"
> 3. Attributes related to hive_db location, hive_storagedesc location
> and attributes of hive_process and hdfs_path are not renamed and have db9
> reference still.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-3024) On hive_db rename few attributes are still not renamed after successful import
[
https://issues.apache.org/jira/browse/ATLAS-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapildeo Nayak updated ATLAS-3024:
--
Attachment: 0001-BUG-111658-hive_db-rename-few-attributes-are-still-n.patch
> On hive_db rename few attributes are still not renamed after successful import
> --
>
> Key: ATLAS-3024
> URL: https://issues.apache.org/jira/browse/ATLAS-3024
> Project: Atlas
> Issue Type: Bug
>Reporter: Kapildeo Nayak
>Priority: Major
> Attachments:
> 0001-BUG-111658-hive_db-rename-few-attributes-are-still-n.patch
>
>
> # Created a database db9 with a table and external table and exported it.
> # On Importing , renamed it to db11 using :
> {\"conditions\":{\"hive_db.name\":\"EQUALS:
> db9\"},\"action\":{\"hive_db.name\":\"SET: db11\"}}]"
> 3. Attributes related to hive_db location, hive_storagedesc location
> and attributes of hive_process and hdfs_path are not renamed and have db9
> reference still.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-3024) On hive_db rename few attributes are still not renamed after successful import
Kapildeo Nayak created ATLAS-3024:
-
Summary: On hive_db rename few attributes are still not renamed
after successful import
Key: ATLAS-3024
URL: https://issues.apache.org/jira/browse/ATLAS-3024
Project: Atlas
Issue Type: Bug
Reporter: Kapildeo Nayak
# Created a database db9 with a table and external table and exported it.
# On Importing , renamed it to db11 using :
{\"conditions\":{\"hive_db.name\":\"EQUALS:
db9\"},\"action\":{\"hive_db.name\":\"SET: db11\"}}]"
3. Attributes related to hive_db location, hive_storagedesc location and
attributes of hive_process and hdfs_path are not renamed and have db9 reference
still.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-3019) Handle NPE while transform and replicatedTo in import-export
[ https://issues.apache.org/jira/browse/ATLAS-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-3019: -- Attachment: 0001-ATLAS-3019-Handle-NPE-while-transform-and-replicated.patch > Handle NPE while transform and replicatedTo in import-export > > > Key: ATLAS-3019 > URL: https://issues.apache.org/jira/browse/ATLAS-3019 > Project: Atlas > Issue Type: Bug >Reporter: Kapildeo Nayak >Assignee: Kapildeo Nayak >Priority: Minor > Attachments: > 0001-ATLAS-3019-Handle-NPE-while-transform-and-replicated.patch > > > 1) Export fails on setting replicatedTo value to null in export JSON > 2) Using transforms (replace) with both supertype and subtype fails with NPE > during import -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-3019) Handle NPE while transform and replicatedTo in import-export
[ https://issues.apache.org/jira/browse/ATLAS-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak reassigned ATLAS-3019: - Assignee: Kapildeo Nayak > Handle NPE while transform and replicatedTo in import-export > > > Key: ATLAS-3019 > URL: https://issues.apache.org/jira/browse/ATLAS-3019 > Project: Atlas > Issue Type: Bug >Reporter: Kapildeo Nayak >Assignee: Kapildeo Nayak >Priority: Minor > > 1) Export fails on setting replicatedTo value to null in export JSON > 2) Using transforms (replace) with both supertype and subtype fails with NPE > during import -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3019) Handle NPE while transform and replicatedTo in import-export
Kapildeo Nayak created ATLAS-3019: - Summary: Handle NPE while transform and replicatedTo in import-export Key: ATLAS-3019 URL: https://issues.apache.org/jira/browse/ATLAS-3019 Project: Atlas Issue Type: Bug Reporter: Kapildeo Nayak 1) Export fails on setting replicatedTo value to null in export JSON 2) Using transforms (replace) with both supertype and subtype fails with NPE during import -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2968) Update model files to include service-type for each entityDef
[ https://issues.apache.org/jira/browse/ATLAS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-2968: -- Attachment: (was: 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch) > Update model files to include service-type for each entityDef > - > > Key: ATLAS-2968 > URL: https://issues.apache.org/jira/browse/ATLAS-2968 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Kapildeo Nayak >Assignee: Kapildeo Nayak >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch > > > Adding the service-type value to each typedef’s options param. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2968) Update model files to include service-type for each entityDef
[ https://issues.apache.org/jira/browse/ATLAS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-2968: -- Attachment: 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch > Update model files to include service-type for each entityDef > - > > Key: ATLAS-2968 > URL: https://issues.apache.org/jira/browse/ATLAS-2968 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Kapildeo Nayak >Assignee: Kapildeo Nayak >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch, > 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch > > > Adding the service-type value to each typedef’s options param. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2968) Update model files to include service-type for each entityDef
[ https://issues.apache.org/jira/browse/ATLAS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak reassigned ATLAS-2968: - Assignee: Kapildeo Nayak > Update model files to include service-type for each entityDef > - > > Key: ATLAS-2968 > URL: https://issues.apache.org/jira/browse/ATLAS-2968 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Kapildeo Nayak >Assignee: Kapildeo Nayak >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch > > > Adding the service-type value to each typedef’s options param. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2968) Update model files to include service-type for each entityDef
[ https://issues.apache.org/jira/browse/ATLAS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-2968: -- Attachment: (was: 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch) > Update model files to include service-type for each entityDef > - > > Key: ATLAS-2968 > URL: https://issues.apache.org/jira/browse/ATLAS-2968 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Kapildeo Nayak >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch > > > Adding the service-type value to each typedef’s options param. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2968) Update model files to include service-type for each entityDef
[ https://issues.apache.org/jira/browse/ATLAS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-2968: -- Attachment: 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch > Update model files to include service-type for each entityDef > - > > Key: ATLAS-2968 > URL: https://issues.apache.org/jira/browse/ATLAS-2968 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Kapildeo Nayak >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch > > > Adding the service-type value to each typedef’s options param. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2968) Update model files to include service-type for each entityDef
[ https://issues.apache.org/jira/browse/ATLAS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-2968: -- Attachment: 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch > Update model files to include service-type for each entityDef > - > > Key: ATLAS-2968 > URL: https://issues.apache.org/jira/browse/ATLAS-2968 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Kapildeo Nayak >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch > > > Adding the service-type value to each typedef’s options param. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2968) Update model files to include service-type for each entityDef
[ https://issues.apache.org/jira/browse/ATLAS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-2968: -- Description: Adding the service-type value to each typedef’s options param. (was: Adding the service-type value to each typedef’s options ** param.) > Update model files to include service-type for each entityDef > - > > Key: ATLAS-2968 > URL: https://issues.apache.org/jira/browse/ATLAS-2968 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Kapildeo Nayak >Priority: Major > Fix For: trunk > > > Adding the service-type value to each typedef’s options param. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2968) Update model files to include service-type for each entityDef
Kapildeo Nayak created ATLAS-2968: - Summary: Update model files to include service-type for each entityDef Key: ATLAS-2968 URL: https://issues.apache.org/jira/browse/ATLAS-2968 Project: Atlas Issue Type: Improvement Affects Versions: trunk Reporter: Kapildeo Nayak Fix For: trunk Adding the service-type value to each typedef’s options ** param. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2964) Unit TestCases for Exporting multiple hdfs_path
[ https://issues.apache.org/jira/browse/ATLAS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-2964: -- Description: Modified: HdfsPathEntityHandler.java returned path instead of name in toPath() method. > Unit TestCases for Exporting multiple hdfs_path > --- > > Key: ATLAS-2964 > URL: https://issues.apache.org/jira/browse/ATLAS-2964 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Kapildeo Nayak >Assignee: Kapildeo Nayak >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-ATLAS-2964-Unit-TestCases-for-Exporting-multiple-hdf.patch > > > Modified: HdfsPathEntityHandler.java returned path instead of name in > toPath() method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2964) Unit TestCases for Exporting multiple hdfs_path
[ https://issues.apache.org/jira/browse/ATLAS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapildeo Nayak updated ATLAS-2964: -- Attachment: 0001-ATLAS-2964-Unit-TestCases-for-Exporting-multiple-hdf.patch > Unit TestCases for Exporting multiple hdfs_path > --- > > Key: ATLAS-2964 > URL: https://issues.apache.org/jira/browse/ATLAS-2964 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Kapildeo Nayak >Assignee: Kapildeo Nayak >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-ATLAS-2964-Unit-TestCases-for-Exporting-multiple-hdf.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2964) Unit TestCases for Exporting multiple hdfs_path
Kapildeo Nayak created ATLAS-2964: - Summary: Unit TestCases for Exporting multiple hdfs_path Key: ATLAS-2964 URL: https://issues.apache.org/jira/browse/ATLAS-2964 Project: Atlas Issue Type: Bug Affects Versions: 2.0.0 Reporter: Kapildeo Nayak Assignee: Kapildeo Nayak Fix For: 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2257) hive_column type definition changes for position and table attributes when updated
[
https://issues.apache.org/jira/browse/ATLAS-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571361#comment-16571361
]
Kapildeo Nayak commented on ATLAS-2257:
---
In class AtlasStructDefStoreV1 the method[ toJsonFromAttribute](AtlasAttribute
attribute)
The value of lower and upper variable are set according to Cardinality used
for e.g. if Cardinality is SINGLE
and isOptional attribute is true than lower = 0 , and upper is set = 1 by
default.
if isOptional attribute is false than lower = 1 , and upper is set = 1 by
default.
and than value of lower and upper is set for attribute multiplicity with lower
and upper
after this in method() toAttributeDefFromJson()
the value of lower and upper is set for variable valuesMinCount and
valuesMaxCount accordingly.
https://github.com/apache/atlas/blob/branch-0.8/repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasStructDefStoreV1.java#L469
If isUnique is false and Cardinality is other than SINGLE than the Cardinality
is set to LIST and
if isUnique is true and Cardinality is other than SINGLE than the Cardinality
is set to SET.
and if Cardinality is non SINGLE and isOptional attribute is false and
valuesMinCount < 1 than lower = 1 else lower is userdefined value ,
and if Cardinality is non SINGLE and valuesMinCount < 2 than upper =
Integer.MAX_VALUE else upper is userdefined value,
and than value of lower and upper is set for attribute multiplicity with lower
and upper
after this in method() toAttributeDefFromJson()
the value of lower and upper is set for variable valuesMinCount and
valuesMaxCount accordingly.
[https://github.com/apache/atlas/blob/branch-0.8/repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasStructDefStoreV1.java#L516]
Its not a issue.
> hive_column type definition changes for position and table attributes when
> updated
> --
>
> Key: ATLAS-2257
> URL: https://issues.apache.org/jira/browse/ATLAS-2257
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Sharmadha Sainath
>Priority: Major
>
> On a fresh instance of Atlas , following is the type definition of
> hive_column :
> {code}
> {
>category:"ENTITY",
>guid:"076ceac2-5c0d-400f-8f89-ab455125191d",
>createdBy:"atlas",
>updatedBy:"atlas",
>createTime:1510294855527,
>updateTime:1510294855527,
>version:1,
>name:"hive_column",
>description:"hive_column",
>typeVersion:"1.3",
>options:{
> schemaAttributes:"[" name",
> "description",
> "owner",
> "type",
> "comment",
> "position"
>] "
> },
> attributeDefs: [
> {
> name: " type",
>typeName:"string",
>isOptional:false,
>cardinality:"SINGLE",
>valuesMinCount:1,
>valuesMaxCount:1,
>isUnique:false,
>isIndexable:true
> },
> {
>name:"comment",
>typeName:"string",
>isOptional:true,
>cardinality:"SINGLE",
>valuesMinCount:0,
>valuesMaxCount:1,
>isUnique:false,
>isIndexable:false
> },
> {
>name:"position",
>typeName:"int",
>isOptional:true,
>cardinality:"SINGLE",
>valuesMinCount:-1,
>valuesMaxCount:-1,
>isUnique:false,
>isIndexable:false
> },
> {
>name:"table",
>typeName:"hive_table",
>isOptional:true,
>cardinality:"SINGLE",
>valuesMinCount:-1,
>valuesMaxCount:-1,
>isUnique:false,
>isIndexable:false
> }
> ],
> superTypes:[
> "DataSet"
> ]
> }
> {code}
> fired an update PUT request to update the hive_column type definition without
> changing the definition . Update is successful. After update , following is
> the type definition of hive_column :
> {code}
> {
>category:"ENTITY",
>guid:"076ceac2-5c0d-400f-8f89-ab455125191d",
>createdBy:"atlas",
>updatedBy:"admin",
>createTime:1510294855527,
>updateTime:1510294918066,
>version:5,
>name:"hive_column",
>description:"hive_column",
>typeVersion:"1.3",
>options:{
> schemaAttributes:"[" name",
> "description",
> "owner",
> "type",
> "comment",
> "position"
>] "
> },
> attributeDefs: [
> {
> name: " type",
>typeName:"string",
>isOptional:false,
>cardinality:"SINGLE",
>valuesMinCount:1,
>valuesMaxCount:1,
>isUnique:false,
>isIndexable:true
> },
> {
>name:"comment",
>typeName:"string",
>isOptional:true,
>cardinality:"SINGLE",
>valuesMinCount:0,
>valuesMaxCount:1,
>isUnique:false,
>isIndexable:false
> },
> {
>name:"position",
>typeName:"int",
>isOptional:true,
>cardinality:"SINGLE",
>valuesMinCount:0,
>valuesMaxCount:1,
>isUnique:false,
>isIndexable:false
> },
> {
>
[jira] [Commented] (ATLAS-1645) Tag is not associated when value for optional attributes are not provided for byte ,date, double,float,short,int.
[ https://issues.apache.org/jira/browse/ATLAS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561906#comment-16561906 ] Kapildeo Nayak commented on ATLAS-1645: --- [~ssainath],could not reproduce this bug on master and branch-0.8 > Tag is not associated when value for optional attributes are not provided for > byte ,date, double,float,short,int. > - > > Key: ATLAS-1645 > URL: https://issues.apache.org/jira/browse/ATLAS-1645 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Priority: Major > Attachments: Empty value for tag attributes exception.txt > > > 1. Created 8 tags. > 2. Each tag with one attribute of types byte,date, double,float,short,int, > string,boolean. > 3. Associated all the tags to an entity one by one without providing any > value for the tag attribute. > 4.Only tags with string and boolean as types got associated. Rest of the tag > association threw 500 internal server error as empty values are treated as > string and are validated against the datatype. > Trait attribute values are optional ,so empty values should be handled. > Following types expect value : > - byte > - date > - double > - float > - short > - int > Attached exception stack trace when associating an entity, a PII tag with > attribute id of type int ,with no value for id. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
