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

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

HarshitGupta11 opened a new pull request, #5168:
URL: https://github.com/apache/hadoop/pull/5168

   
   ### Description of PR
   ChecksumFileSystem::readVectored might return byte buffers that are not 
positioned at 0 which might be the underlying API contract for other readers 
like ORC.
   
   ### How was this patch tested?
   The patch was tested locally.
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> ChecksumFileSystem::readVectored might return byte buffers not positioned at 0
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-18530
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18530
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: 3.3.5
>            Reporter: Harshit Gupta
>            Priority: Blocker
>
> Checksystem::readVectored method returns the byte buffers that are not 
> positioned at 0, which might be the underlying assumption for the readers 
> like ORC.
>  
> cc:/ [~mthakur] [~rbalamohan] [[email protected]]



--
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