EdColeman

The timeout is a timeout for thrift calls, not a scan timeout. With a scanner, setting a batch timeout will control how long it will take to gather results -...

I bumped this to 3.1.0 - it is a new capability and may fit better there rather than a deprecation clean-up release (3.0.0). If this is ready before the 3.0.0...

This PR will be superseded by the changes with https://github.com/apache/accumulo/pull/3161

The version was removed as part of https://github.com/apache/accumulo/pull/3988. I've been running in uno without issues. I've not run that specific example, but I can create tables, add data, merge and...

To illustrate the issue I create a clone and then list the metadata files. The original table is tableA (id=1), the clone is cloneA (id=5). The resulting files for the...

I realize that this is contradictory to Dave's comment and the latest changes - likely its a matter of preference. Maybe updating (adding) the javadocs for those methods calling out...

Why was the logging left at warn? If that's appropriate, it's fine, just wanted to check that reducing the severity level was not overlooked.

Should there be a check to see if the system is up or if there running compactions? If this was run on a system with active compactions, would it find...

Are there any logging performance considerations? Particularity when we know ahead of time that a message could be quite spammy in certain situations? Defeating the message in code (at the...

I can see #4488 being useful for something like status reporting - one example that I can think of would be something like a loop that checks status (say its...