[
https://issues.apache.org/jira/browse/ATLAS-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405939#comment-17405939
]
ASF subversion and git services commented on ATLAS-4400:
--------------------------------------------------------
Commit d7547c493f25f3e1acc5572ce7159068d6b2d00e in atlas's branch
refs/heads/master from Sidharth Mishra
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d7547c4 ]
ATLAS-4400: Fixed Hook and Atlas Preprocessor to handle S3 V2 directory
objectPrefix Issue with Atlas Server and Hook versions mismatch
Signed-off-by: sidmishra <[email protected]>
> 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
> Attachments:
> ATLAS-4400-Fixed-Hook-and-Atlas-Preprocessor-to-hand.patch
>
>
> 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)
