When looking at the BufferedDeletesStream class, indeed it says:
// LUCENE MONITOR: We copied this class from Lucene, effectively overriding
it with our implementation
// if it comes first in the classpath, allowing for faster apply deletes
based on terms
which is the cause of the issue. Not sure if it will be a problem for
anyone else. Still looking for a solution using proguard configuration,
just letting you know :).
When looking at the BufferedDeletesStream class, indeed it says:
// LUCENE MONITOR: We copied this class from Lucene, effectively
overriding it with our implementation
// if it comes first in the classpath, allowing for faster apply deletes
based on terms
which is the cause of the issue. Not sure if it will be a problem for
anyone else. Still looking for a solution using proguard configuration,
just letting you know :).
When looking at the BufferedDeletesStream class, indeed it says:
// LUCENE MONITOR: We copied this class from Lucene, effectively overriding it with our implementation
// if it comes first in the classpath, allowing for faster apply deletes based on terms
which is the cause of the issue. Not sure if it will be a problem for anyone else. Still looking for a solution using proguard configuration, just letting you know :).
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.