Accumulo's delete processing can cause Fluo to have O(N^2) read and commit processing when a key/value has lots of versions. To avoid this, Fluo uses reflection to remove the Accumulo delete iterator. Performance improvements made in Accumulo 2.0 by apache/accumulo#244 break Fluo's reflection code. The reflection code does not need to be fixed though, instead deletes can be turned off in Accumulo 2.0 using the option added in apache/accumulo#598.
[ Full content available at: https://github.com/apache/fluo/issues/1049 ] This message was relayed via gitbox.apache.org for [email protected]
