Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # dev >> table.offline behavior change in 1.6.0

Copy link to this message
Re: table.offline behavior change in 1.6.0
I disagree. The 1.5.0 code path waits by default. Offline() calls
doTableOperation, which calls doTableOperation with wait=true, which
causes waitForTableOperation to trigger. Unless there's weird casing
for waitForTableOperation, of which there does not appear to be, it will
On Wed, Dec 4, 2013 at 3:10 PM, Keith Turner <[EMAIL PROTECTED]> wrote:

> On Wed, Dec 4, 2013 at 2:33 PM, John Vines <[EMAIL PROTECTED]> wrote:
>> It has recently come to my attention that the default behavior for
>> TableOperations.offline(table) to immediately return. There is now an
>> additional command which offers a wait flag like the old behavior.
>> However,
>> I'm really not comfortable changing API behavior between major releases
>> like that. What is everyone else's thoughts on this?
> The old behavior did not wait.  The API preserves the old behavior.