Hi Junwen, The difference between ACCUMULO-3532 and the change you are referring to is that ACCUMULO-3532 addressed a bug in MiniAccumuloCluster's public API. The enum you are referring to is in an implementation class and is not public API, and has no guarantees of API compatibility, since it is intended for internal use only.
Additionally, the change you mentioned in 1.7.1 is quite old and has been included in many releases since the change occurred. The only currently supported version of 1.x is now 1.10.1. We appreciate the report, but unless I'm missing something, I don't think there's anything to fix for this. Thanks, Christopher On Sun, Apr 25, 2021 at 6:34 PM junwen yang <[email protected]> wrote: > > Similar to https://issues.apache.org/jira/browse/ACCUMULO-3532, 1.7.1 has > added a TokenSource.JOB to the enum, which causes it to lose backward > compatibility. > > Commit that introduces the new value: > https://github.com/apache/accumulo/commit/2c983317179634d6ddc10726defff303be4ae708#diff-abffdacb11d32dd39ae31b9795eecf4f90a6ee815d0af09d1faadd66f9cd091eR70 > > The TokenSource enum in > accumulo/core/src/main/java/org/apache/accumulo/core/client/mapreduce/lib/impl/ConfiguratorBase.java > before and after is: > > FILE, INLINE; > > FILE, INLINE, JOB; > > Best, > Junwen
