[ 
https://issues.apache.org/jira/browse/HADOOP-19559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039818#comment-18039818
 ] 

ASF GitHub Bot commented on HADOOP-19559:
-----------------------------------------

ahmarsuhail commented on PR #8095:
URL: https://github.com/apache/hadoop/pull/8095#issuecomment-3562520696

   I don't think we should try and fixing these tests, instead always run them 
with the classic input stream. Most of them assert behaviour which does not 
apply to AAL (eg: the readAhead value, stream draining, or thread context 
stats). 
   
   What I will do as a follow up is look at which ones make sense to have as 
part of a new ITest for AAL. Similar to what we did for the prefetching input 
stream. I will make those changes as part of our 
https://github.com/apache/hadoop/pull/7923. 
   
   Merging this for now and will backport, so if you kick of a 3.4.3 run this 
weekend we can catch any issues early.  




> S3A: Analytics accelerator for S3 to be enabled by default
> ----------------------------------------------------------
>
>                 Key: HADOOP-19559
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19559
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: fs/s3
>    Affects Versions: 3.5.0, 3.4.2
>            Reporter: Ahmar Suhail
>            Priority: Major
>              Labels: pull-request-available
>
> Make "analytics" the default input stream in S3A. 
> Goals
> * Parquet performance through applications running queries over the data 
> (spark etc)
> * Performance for other formats good as/better than today. Examples: avro 
> manifests in iceberg, ORC in hive/spark
> * Performance for other uses as good as today (whole-file/sequential reads of 
> parquet data in distcp etc)
> * better resilience to bad uses (incomplete reads not retaining http streams, 
> buffer allocations on long-retained data)
> * efficient on applications like Impala, which caches parquet footers itself, 
> and uses unbuffer() to discard all stream-side resources. Maybe just throw 
> alway all state on unbuffer() and stop trying to be sophisticated, or support 
> some new openFile flag which can be used to disable footer parsing



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to