New Contributor
Posts: 1
Registered: ‎10-17-2018
Kudu table consistency on tablet servers using impala JDBC



I've an issue with updating an impala kudu table by cloudera impala JDBC driver version: 2.5.43


The case:

1. Application updates some kudu table by setting new value to some column.

2. Immediately after updating the application invokes sql request that query this table along with others

3. This application suppose that this table is updated however sometimes the query returns an old data.


The replication factor is 3 so I think that updating has happened on one tablet server but query has gone to other tablet server. The application works right if it waits for a couple of seconds between point 1 and 2.


Is it possible somehow to avoid such kind of inconsistency?


Who Me Too'd this topic