[
https://issues.apache.org/jira/browse/MAPREDUCE-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108335#comment-13108335
]
Joep Rottinghuis commented on MAPREDUCE-3039:
---------------------------------------------
Ok, I'll take that back.
When heeding my own advice in HADOOP-7646 about clearing out the
~/.ivy2/repository cache the avro 1.3.2 jar disappeared from the classpath and
the compilation error went away.
Back to my original question:
Should I remove the new Utf8(String...) code and put straight Strings into the
map in JobSubmittedEvent?
My concern is that the map is defined as CharSequence and we're putting Utf8's
in the map. If any client tries to retrieve a key using a string, then they
will not get the value back as the key of type Utf8 will not equal String or
Charsequence types.
> Make mapreduce use same version of avro as HBase
> ------------------------------------------------
>
> Key: MAPREDUCE-3039
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3039
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/capacity-sched, contrib/fair-share,
> contrib/gridmix, contrib/mrunit, contrib/mumak, contrib/raid,
> contrib/streaming, jobhistoryserver
> Affects Versions: 0.22.0
> Reporter: Joep Rottinghuis
> Assignee: Joep Rottinghuis
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-3039-branch-0.22.patch
>
>
> HBase depends on avro 1.5.3 whereas hadoop-common depends on 1.3.2.
> When building HBase on top of hadoop, this should be consistent.
> Moreover, this should be consistent between common, hdfs, and mapreduce.
> Contribs seem to have declared a dependency on avro but are not in fact
> depending on it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
