[cassandra driver] Assign consistency level of BatchStatement to first BoundStatement #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In getQueryPlan(Session session, BatchStatement batch), the first BoundStatement is used to construct UpHostIterator.
If the consistency level of BatchStatement is set but that of the first BoundStatement is not set, we should assign consistency level of BatchStatement to first BoundStatement.
Thanks to Aravind for the observation.
Without this fix, ConsistencyLevel.YB_CONSISTENT_PREFIX would be used for the first BoundStatement (whose ConsistencyLevel is not set).
which would result in shuffling of the hosts, leaving leader not in the front: