[
https://issues.apache.org/jira/browse/PHOENIX-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell updated PHOENIX-6769:
-----------------------------------------
Description:
There is a well known incompatibility between old versions of mockito-all and
mockito-core and newer versions.
The fix is to align your use of mockito (mockito-core) with downstreamers.
HBase uses mockito-core 2.28.2 on branch-2.4 and branch-2.5. (Phoenix is on
1.10.19.) I checked Hadoop branch-3.3 and it's also on 2.28.2.
I recently opened a PR for OMID-226 to fix the same problem in phoenix-omid.
was:
There is a well known incompatibility between old versions of mockito-all and
mockito-core and newer versions. I'm not exactly sure what the trigger was,
perhaps PHOENIX-6753, but tests fail for me when run locally exhibiting the
classic symptom of this problem.
The fix is to align your use of mockito (mockito-core) with downstreamers.
HBase uses mockito-core 2.28.2 on branch-2.4 and branch-2.5. (Phoenix is on
1.10.19.) I checked Hadoop branch-3.3 and it's also on 2.28.2.
I recently opened a PR for OMID-226 to fix the same problem in phoenix-omid.
For example
{noformat}
ERROR]
org.apache.phoenix.hbase.index.write.recovery.TestPerRegionIndexWriteCache.testMultipleAddsForSingleRegion
Time elapsed: 0.035 s <<< ERROR!
java.lang.IncompatibleClassChangeError: Found interface
org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:623)
at
org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:53)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:190)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:160)
at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:723)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:129)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:833)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:547)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:488)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:160)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62)
at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:295)
at
org.apache.phoenix.hbase.index.write.recovery.TestPerRegionIndexWriteCache.setUp(TestPerRegionIndexWriteCache.java:109)
{noformat}
> Unit tests failing with IncompatibleClassChangeError
> ----------------------------------------------------
>
> Key: PHOENIX-6769
> URL: https://issues.apache.org/jira/browse/PHOENIX-6769
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.3.0
> Reporter: Andrew Kyle Purtell
> Priority: Major
> Fix For: 5.3.0
>
>
> There is a well known incompatibility between old versions of mockito-all and
> mockito-core and newer versions.
> The fix is to align your use of mockito (mockito-core) with downstreamers.
> HBase uses mockito-core 2.28.2 on branch-2.4 and branch-2.5. (Phoenix is on
> 1.10.19.) I checked Hadoop branch-3.3 and it's also on 2.28.2.
> I recently opened a PR for OMID-226 to fix the same problem in phoenix-omid.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
