[
https://issues.apache.org/jira/browse/HADOOP-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010931#comment-18010931
]
ASF GitHub Bot commented on HADOOP-19394:
-----------------------------------------
ahmarsuhail commented on PR #7720:
URL: https://github.com/apache/hadoop/pull/7720#issuecomment-3136464282
thanks @mukund-thakur and @steveloughran for the reviews, addressed the
feedback.
Will need to cut a PR to AAL for the release() changes 1/ call release on
failure and 2/ add in null check so that `testNullReleaseOperation` passes.
Don't think think we need to block this on the above, i will create a new PR
to update once there is a new version of AAL
> S3A Analytics Accelerator: vector IO support
> --------------------------------------------
>
> Key: HADOOP-19394
> URL: https://issues.apache.org/jira/browse/HADOOP-19394
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.1
> Reporter: Steve Loughran
> Priority: Major
> Labels: pull-request-available
>
> Add vector IO support for analytics accelerator stream
> Three stages
> # pull up s3a input stream to work with all ObjectInputStreams; do its own
> fetching independent of the analytics stream
> # provide info to stream of fetches having taken place (remove from cache,
> cancel prefetch)
> full integration
> * return a range from cache if present
> * append to the block retrieval callback if a prefetch is in progress
> * only do merge + new request if the range cannot be satisifed entirely from
> cached data
> Out of scope: handling case where part of a range is in cache/retrieval. Too
> complicated and so prone to problems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
