[jira] [Commented] (ATLAS-3515) Migration: New Types Referenced within Existing Types
[
https://issues.apache.org/jira/browse/ATLAS-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970426#comment-16970426
]
ASF subversion and git services commented on ATLAS-3515:
Commit 77dbea47bf42daceefea6bd03b81116aefa2f755 in atlas's branch
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=77dbea4 ]
ATLAS-3515: Migration import now creates new types and then updates existing
types.
> Migration: New Types Referenced within Existing Types
> -
>
> Key: ATLAS-3515
> URL: https://issues.apache.org/jira/browse/ATLAS-3515
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3515-Migration-import-type-definition.patch
>
>
> *Background*
> During migration import (and regular Import) types coming in are processed in
> the following way:
> * New types are determined.
> * Modification to existing types are determined.
> *Steps to Duplicate*
> _Pre-requisites:_
> * Create type definition with new _structDef_.
> * Modify _hive_table_ (existing) such a new attribute references the
> _structDef_.
> _Steps_
> * Initiate migration import.
> _Expected outcome_
> * New types should be part of the types definition (using REST APIs and
> property pages).
> * Data should get migrated.
> _Actual outcome_
> * Type definition import fails.
> _Additional information_
> Stack trace:
> {code:java}
> org.apache.atlas.exception.AtlasBaseException: Given typename
> hive_table_profile_data was invalid
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025)
>
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285)
>
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3515) Migration: New Types Referenced within Existing Types
[
https://issues.apache.org/jira/browse/ATLAS-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969863#comment-16969863
]
ASF subversion and git services commented on ATLAS-3515:
Commit 98163440590852fa9d142c23e596e8975a322349 in atlas's branch
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9816344 ]
ATLAS-3515: Migration import now creates new types and then updates existing
types.
> Migration: New Types Referenced within Existing Types
> -
>
> Key: ATLAS-3515
> URL: https://issues.apache.org/jira/browse/ATLAS-3515
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3515-Migration-import-type-definition.patch
>
>
> *Background*
> During migration import (and regular Import) types coming in are processed in
> the following way:
> * New types are determined.
> * Modification to existing types are determined.
> *Steps to Duplicate*
> _Pre-requisites:_
> * Create type definition with new _structDef_.
> * Modify _hive_table_ (existing) such a new attribute references the
> _structDef_.
> _Steps_
> * Initiate migration import.
> _Expected outcome_
> * New types should be part of the types definition (using REST APIs and
> property pages).
> * Data should get migrated.
> _Actual outcome_
> * Type definition import fails.
> _Additional information_
> Stack trace:
> {code:java}
> org.apache.atlas.exception.AtlasBaseException: Given typename
> hive_table_profile_data was invalid
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025)
>
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285)
>
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3515) Migration: New Types Referenced within Existing Types
[
https://issues.apache.org/jira/browse/ATLAS-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969644#comment-16969644
]
Sarath Subramanian commented on ATLAS-3515:
---
+1 for the patch. Thanks [~amestry]
> Migration: New Types Referenced within Existing Types
> -
>
> Key: ATLAS-3515
> URL: https://issues.apache.org/jira/browse/ATLAS-3515
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3515-Migration-import-type-definition.patch
>
>
> *Background*
> During migration import (and regular Import) types coming in are processed in
> the following way:
> * New types are determined.
> * Modification to existing types are determined.
> *Steps to Duplicate*
> _Pre-requisites:_
> * Create type definition with new _structDef_.
> * Modify _hive_table_ (existing) such a new attribute references the
> _structDef_.
> _Steps_
> * Initiate migration import.
> _Expected outcome_
> * New types should be part of the types definition (using REST APIs and
> property pages).
> * Data should get migrated.
> _Actual outcome_
> * Type definition import fails.
> _Additional information_
> Stack trace:
> {code:java}
> org.apache.atlas.exception.AtlasBaseException: Given typename
> hive_table_profile_data was invalid
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025)
>
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285)
>
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3515) Migration: New Types Referenced within Existing Types
[
https://issues.apache.org/jira/browse/ATLAS-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969592#comment-16969592
]
Ashutosh Mestry commented on ATLAS-3515:
PC build:
[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1533/]
> Migration: New Types Referenced within Existing Types
> -
>
> Key: ATLAS-3515
> URL: https://issues.apache.org/jira/browse/ATLAS-3515
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3515-Migration-import-type-definition.patch
>
>
> *Background*
> During migration import (and regular Import) types coming in are processed in
> the following way:
> * New types are determined.
> * Modification to existing types are determined.
> *Steps to Duplicate*
> _Pre-requisites:_
> * Create type definition with new _structDef_.
> * Modify _hive_table_ (existing) such a new attribute references the
> _structDef_.
> _Steps_
> * Initiate migration import.
> _Expected outcome_
> * New types should be part of the types definition (using REST APIs and
> property pages).
> * Data should get migrated.
> _Actual outcome_
> * Type definition import fails.
> _Additional information_
> Stack trace:
> {code:java}
> org.apache.atlas.exception.AtlasBaseException: Given typename
> hive_table_profile_data was invalid
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025)
>
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285)
>
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
