[
https://issues.apache.org/jira/browse/AVRO-3594?focusedWorklogId=798113&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-798113
]
ASF GitHub Bot logged work on AVRO-3594:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Aug/22 16:49
Start Date: 04/Aug/22 16:49
Worklog Time Spent: 10m
Work Description: steveloughran commented on PR #1807:
URL: https://github.com/apache/avro/pull/1807#issuecomment-1205517072
except that hadoop-2 profile still exists, doesn't it? which means that even
though hadoop 3 profile is full of features, the 2.x one blocks things from
working
Issue Time Tracking
-------------------
Worklog Id: (was: 798113)
Time Spent: 20m (was: 10m)
> FsInput to use openFile() API for cloud storage read performance
> ----------------------------------------------------------------
>
> Key: AVRO-3594
> URL: https://issues.apache.org/jira/browse/AVRO-3594
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.11.2
> Reporter: Steve Loughran
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> avro can now use the FileSystem.openFile() API to open a file on a hadoop
> filesystem connector (HADOOP-15229).
> by setting the file length and fadvise policy through opt() calls, the
> clients can
> * skip a HEAD request when opening a file
> * optimise the ranges of GET request for sequential access, even in clusters
> where s3a has been configured to use random iO (which some hive clusters do)
> filesystems/releases which don't recognise the options added in HADOOP-16202
> will ignore them; the api will fall back to classic open(path) API call if
> the connector doesn't have a custom implementation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
