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

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

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

   
   Add new reference field; verifies it remains in merging.
   
   also fix up those tests which used string comparison of range values into 
actual field checking.
   
   
   ### 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?
   
   




> VectorIO FileRange type to support a "reference" field
> ------------------------------------------------------
>
>                 Key: HADOOP-18507
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18507
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: 3.3.5
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>
> to use in libraries, it is really good to be able to connect a FileRange back 
> to the application/library level structure (chunk/split data, usually). 
> Proposed: add an {{Object reference)) field which can be given arbitrary data 
> or null, and queried for by app. it is not used in the API at all



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