Thanks Josh and Adam! My bad, I looked at the code again, actually we only call flush in the end (that override function we have only called at the end), so I have another issue here, which is the mutation will be lost when the app crash. I will think about more on how to mitigate this issue.
Thanks for mentioning about the batch writer semantic. Luckily for our case, the count doesn't need to be so accurate, as it's more like for the optimizer to re-order the queries based on cardinality. The stats discrepancy needs to be big enough to screw the result, otherwise it won't matter much. This is good tips though, and I'll pay attention on it in the future. Thanks, Z -- View this message in context: http://apache-accumulo.1065345.n5.nabble.com/using-combiner-vs-building-stats-cache-tp14979p15003.html Sent from the Developers mailing list archive at Nabble.com.
