[
https://issues.apache.org/jira/browse/HADOOP-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477579
]
David Bowen commented on HADOOP-1053:
-------------------------------------
> The three referenced o.a.h.io classes currently have no other dependencies.
I don't think that is true. WritableComparator references DataInputBuffer, and
WritableUtils imports from other packages.
Even if it were true, it would be a fragile "solution" to the identified
problem, since additional dependencies will creep in over time.
> The stated goal "independent of Hadoop" is nonsensical, as record io is a
> part of hadoop.
Yes, we should rephrase it. The goal is or was to make the record i/o
functionality modular. I.e. there should be some identifiable (proper) subset
of Hadoop which supports the record i/o functionality and can be used
separately. Clearly we do not have a consensus that this is a worthwhile goal.
If we did, I'm sure we could find a better solution, but given that we don't,
there isn't much point in wasting more time on it.
> Make Record I/O usable from independent of Hadoop
> -------------------------------------------------
>
> Key: HADOOP-1053
> URL: https://issues.apache.org/jira/browse/HADOOP-1053
> Project: Hadoop
> Issue Type: Improvement
> Components: record
> Affects Versions: 0.11.2
> Environment: All
> Reporter: Milind Bhandarkar
> Assigned To: Milind Bhandarkar
> Fix For: 0.13.0
>
> Attachments: jute-patch.txt
>
>
> This issue has been created to separate one proposal originally included in
> HADOOP-941, for which no consensus could be reached. For earlier discussion
> about the issue, please see HADOOP-941.
> I will summarize the proposal here. We need to provide a way for some users
> who want to use record I/O framework outside of Hadoop.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
