This is an automated email from the ASF dual-hosted git repository.
ahmar pushed a change to branch feature-HADOOP-19363-analytics-accelerator-s3
in repository https://gitbox.apache.org/repos/asf/hadoop.git
discard 944fbbb16f3 review changes
discard bae4ed47bd5 AAL ITest updates
discard 8063bb11754 remove createContract() usage
discard 977a1b05c6d initial review comments
discard b2b045fabbd bump AAL version to 0.0.4
discard 2fa69eb1101 check for null etag
discard 5a2db0ad128 review nits
discard b92a66176ed pass down file open options such as read policy, file
status to AAL
discard 3828ad54469 lazy eval of stream factory + test fixes
discard 6e0e5673d3f Integrates AAL into S3A
add a8da9b230a8 Integrates AAL into S3A
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (944fbbb16f3)
\
N -- N -- N
refs/heads/feature-HADOOP-19363-analytics-accelerator-s3 (a8da9b230a8)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org
