saksenasonali opened a new pull request, #660:
URL: https://github.com/apache/atlas/pull/660

   What changes were proposed in this pull request?
   CDPD-69317: Export/Import API — handle tag attribute type changes between 
exports
   
   When a tag/classification attribute’s type changed between two exports (e.g. 
attrib1 was date in the target Atlas instance but string in the import bundle), 
import previously failed with INVALID_IMPORT_ATTRIBUTE_TYPE_CHANGED.
   
   This patch allows import to succeed in that scenario by:
   
   TypeAttributeDifference — Treat attribute type mismatches as updatable 
differences instead of throwing INVALID_IMPORT_ATTRIBUTE_TYPE_CHANGED.
   AtlasStructDefStoreV2 — Skip the “Data type update for attribute is not 
supported” guard when an import is in progress.
   GraphBackedSearchIndexer — During import, if a graph property key already 
exists with a different Java type, delete and recreate it (JanusGraph does not 
support in-place type changes).
   AtlasGraphManagement / AtlasJanusGraphManagement — Add 
getPropertyKeyDataType() to read the registered type of an existing property 
key.
   Example: Import bundle defines tag1 with attrib1=string, attrib2=int, 
attrib3=int, while the target has tag1 with attrib1=date, attrib3=int. Import 
now completes and updates attrib1 to string, adds attrib2, and keeps attrib3.
   
   How was this patch tested?
   Unit tests
   TypeAttributeDifferenceTest.attributeTypeChange_ReturnsUpdatedAttribute — 
verifies a changed attribute type is returned as a difference to apply.
   ImportServiceTest.importHdfs_path1 — updated from expecting 
INVALID_IMPORT_ATTRIBUTE_TYPE_CHANGED to asserting successful import with 
updated tag attributes (attrib1=string, attrib2=int, attrib3=int) using 
hdfs_path1.zip and tag1.json.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to