[
https://issues.apache.org/jira/browse/HADOOP-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-3048:
----------------------------------
Attachment: 3048-alt.patch
Attached is an example of your patch that avoids GenericsUtil. It contains only
a single, commented SuppressWarnings annotation for loadArray, necessary
because Array.newInstance returns Object. Most of what it does is move the
load/store functionality from static methods- that create instances of
DefaultSerializer- to instance methods that maintain the modest type safety
that generics can guarantee. It also keeps the class object one passes in to
the constructor. Other than those minor tweaks, the rest of the functionality
remains as you had it in your last patch.
You've convinced me of the utility of getClass(T t), though. Do you think it
could go into ReflectionUtils?
> Stringifier
> -----------
>
> Key: HADOOP-3048
> URL: https://issues.apache.org/jira/browse/HADOOP-3048
> Project: Hadoop Core
> Issue Type: New Feature
> Affects Versions: 0.17.0
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: 3048-alt.patch, stringifier_v1.patch,
> stringifier_v2.patch, stringifier_v3.patch, stringifier_v4.patch,
> stringifier_v5.patch, stringifier_v6.patch
>
>
> Storing arbitrary objects in the configuration has been discussed before in
> HADOOP-449 and HADOOP-1873. Although enabling such functionality has the risk
> of encouraging people to put big binary objects in the configuration, for
> some use cases passing objects to tasks is absolutely necessary.
> This issue will track the implementation of a Stringifier interface which
> stringifies and destringifies objects. Using this implementation, developers
> can store objects in the configuration and restore them later.
> Any thoughts ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
