[
https://issues.apache.org/jira/browse/HADOOP-15625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587473#comment-16587473
]
Brahma Reddy Battula edited comment on HADOOP-15625 at 8/21/18 2:10 PM:
------------------------------------------------------------------------
{quote}there's some SSE-C tests which fail if you turn encryption on by
default; been wondering what to do there
{quote}
Thought of digging more..But $56.67 is generated for this month to my account.
Looks because of S3A guard (dynamodb).shall re-check(dig more) by next month...?
can you review the patch.IMO, this might not related to this pa
was (Author: brahmareddy):
bq.there's some SSE-C tests which fail if you turn encryption on by default;
been wondering what to do there
Thought of digging more..But $56.67 is generated for this month. Looks because
of S3A guard (dynamodb).shall re-check(dig more) by next month...?
can you review the patch.IMO, this might not related to this pa
> S3A input stream to use etags to detect changed source files
> ------------------------------------------------------------
>
> Key: HADOOP-15625
> URL: https://issues.apache.org/jira/browse/HADOOP-15625
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.0
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Priority: Major
> Attachments: HADOOP-15625-001.patch, HADOOP-15625-002.patch
>
>
> S3A input stream doesn't handle changing source files any better than the
> other cloud store connectors. Specifically: it doesn't noticed it has
> changed, caches the length from startup, and whenever a seek triggers a new
> GET, you may get one of: old data, new data, and even perhaps go from new
> data to old data due to eventual consistency.
> We can't do anything to stop this, but we could detect changes by
> # caching the etag of the first HEAD/GET (we don't get that HEAD on open with
> S3Guard, BTW)
> # on future GET requests, verify the etag of the response
> # raise an IOE if the remote file changed during the read.
> It's a more dramatic failure, but it stops changes silently corrupting things.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
