[
https://issues.apache.org/jira/browse/HADOOP-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858011#action_12858011
]
Hong Tang commented on HADOOP-6708:
-----------------------------------
bq. Is this block offset/length index already maintained?
Yes.
bq. It sounds like the skip-to-the-next-block optimization is not already
implemented. Do you know what are the next steps required to make that happen?
Correct. There is no immediate plan for me to work on this. The implementation
could be quite simple but I'll need a bit more time to refresh my mind of the
code structure. Also, would you be able to help test this?
bq. The other thing that needs to happen is an API to support long-valued
lengths. Should I submit a patch that modifies the existing method signatures?
I think modifying the existing method signature is fine (not clear why we need
CountingInputStream in TFile, users should be able to create one on top of the
input stream we provide, right?).
> New file format for very large records
> --------------------------------------
>
> Key: HADOOP-6708
> URL: https://issues.apache.org/jira/browse/HADOOP-6708
> Project: Hadoop Common
> Issue Type: New Feature
> Components: io
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: lobfile.pdf
>
>
> A file format that handles multi-gigabyte records efficiently, with lazy disk
> access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
