[
https://issues.apache.org/jira/browse/AVRO-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213012#comment-13213012
]
Scott Carey commented on AVRO-593:
----------------------------------
Re #1: its OK to have multiple packages in a single maven module, but not good
to have a package split across modules as it causes problems for OSGi and in
the future, Java 8 modules.
Re #2: This is OK, but a little confusing. Also, if we ever wanted to break
apart the mapred module in to two or three (e.g. avro-hadoop, avro-mapred,
avro-mapreduce with the common stuff in avro-hadoop and the two APIs in the
others) it will be less consistent.
Re #3: This is fairly clean, but is incompatible.
Re #4: This is decent, but I would propose:
org.apache.avro.{hadoop,mapreduce,mapred,hadoop.io,hadoop.file,hadoop.util}.
Then the current module would have o.a.a.{hadoop,mapreduce,mapred} and children
packages. A future split could divide on these cleanly. One reason to split
in the future is that some users may want hadoop stuff that is not related to
mapreduce -- sequence files, avro data file access via FileSytem+Path, etc. If
we split the module, avoiding moving classes around is important.
Is it possible to move AvroSequenceFile under o.a.a ? All classes in that
package need to be in the base avro maven module, and cannot depend on any
hadoop APIs.
> Avro mapreduce apis incompatible with hadoop 0.20.2
> ---------------------------------------------------
>
> Key: AVRO-593
> URL: https://issues.apache.org/jira/browse/AVRO-593
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.3.2, 1.3.3
> Environment: Avro 1.3.3, Hadoop 0.20.2
> Reporter: Steve Severance
> Assignee: Garrett Wu
> Attachments: AVRO-593.patch, AVRO-593.patch
>
>
> The avro api's for hadoop use the hadoop mapreduce api that has been
> deprecated. A new avro mapreduce api should be implemented for hadoop 0.20
> and higher.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
