impala-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Code Review)" <>
Subject [Impala-CR](cdh5-trunk) Re-enable Kudu in build using client stubs when needed
Date Wed, 30 Mar 2016 16:06:34 GMT
Todd Lipcon has posted comments on this change.

Change subject: Re-enable Kudu in build using client stubs when needed

Patch Set 8:

(1 comment)
File tests/common/

Line 259:             time.sleep(wait_secs_between_stmts)
> The writes arent always immediately visible.
Right, the issue is that in order to guarantee visibility of your own writes, you need Impala
to be configured with a consistency mode that only allows reading from the tablet leader,
which inhibits locality. The other option is for Impala to propagate timestamps from previous
writes to the next read, which would be somewhat tricky (we'd have to somehow get it from
the backend back up to the user's session in order to include it in the next query). I can
think of a couple other tricks we could play (eg introduce a 'sync' call which could be made
at the end of every write that waits for propagation) but should probably be deferred from

Another easy workaround for the purposes of tests is to create the Impala tables with a single
replica, but then we aren't testing the replica selection code as well.

Either way, I agree that sleeping is somewhat fragile.

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: I4bf1c964faf21722137adc4f7ba7f78654f0f712
Gerrit-PatchSet: 8
Gerrit-Project: Impala
Gerrit-Branch: cdh5-trunk
Gerrit-Owner: Casey Ching <>
Gerrit-Reviewer: Casey Ching <>
Gerrit-Reviewer: Dan Hecht <>
Gerrit-Reviewer: Internal Jenkins
Gerrit-Reviewer: Matthew Jacobs <>
Gerrit-Reviewer: Todd Lipcon <>
Gerrit-HasComments: Yes

View raw message