[
https://issues.apache.org/jira/browse/FLUME-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15680497#comment-15680497
]
Jeff Holoman commented on FLUME-2662:
-------------------------------------
Ran tests, LGTM
> Upgrade to Commons-IO 2.4
> -------------------------
>
> Key: FLUME-2662
> URL: https://issues.apache.org/jira/browse/FLUME-2662
> Project: Flume
> Issue Type: Bug
> Components: Build
> Affects Versions: v1.5.1
> Reporter: Roshan Naik
> Assignee: Roshan Naik
> Labels: Dependencies
> Attachments: FLUME-2662.patch
>
>
> Hadoop 2.7 is now switching to apache-commons-io v2.4. Hbase 1.0 is also
> using commons-io v2.4.
> Flume is currently at 2.1.
> Flume runs into issues like this when tests run against them:
> testSequenceFile(org.apache.flume.sink.hdfs.TestUseRawLocalFileSystem) Time
> elapsed: 77 sec <<< ERROR!
> java.lang.NoClassDefFoundError: org/apache/commons/io/Charsets
> at org.apache.hadoop.io.SequenceFile$Writer.<init>(SequenceFile.java:854)
> at org.apache.hadoop.io.SequenceFile.createWriter(SequenceFile.java:273)
> at org.apache.hadoop.io.SequenceFile.createWriter(SequenceFile.java:582)
> at org.apache.flume.sink.hdfs.HDFSSequenceFile.open(HDFSSequenceFile.java:98)
> at org.apache.flume.sink.hdfs.HDFSSequenceFile.open(HDFSSequenceFile.java:78)
> at org.apache.flume.sink.hdfs.HDFSSequenceFile.open(HDFSSequenceFile.java:69)
> at
> org.apache.flume.sink.hdfs.TestUseRawLocalFileSystem.testSequenceFile(TestUseRawLocalFileSystem.java:89)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> I am planning to submit a patch to upgrade commons-io to 2.4. Just wanted to
> be cautious and check if we have witnessed has been any issue in the past
> when upgrading apache commons libraries.
> Based on what I see here:
> http://commons.apache.org/proper/commons-io/upgradeto2_4.html and
> http://commons.apache.org/proper/commons-io/upgradeto2_2.html
> Commons-IO 2.4 is binary compat with 2.2 which is in turn binary compat
> with 2.1.
> There is what they call a "rare" case of source incompat as described in
> https://issues.apache.org/jira/browse/IO-318
> Doesnt look like we are affected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
