Previously, during the upstream merging the code using newFramer was added (https://github.com/scylladb/gocql/pull/109) and it was forgotten to replace it with newFramerWithExts. That way, the flagLWT field is set to 0 by default, causing the driver to consider every query executed as a LWT query. For example simple INSERT or SELECT queries are marked as LWT (SELECT pk, ck, v FROM keyspace1.table1 WHERE pk = x;)
This can potentially impact the performance if we want to use ShuffleReplicas() in TokenAwareHostPolicy. If query is marked as LWT the replica shuffling would be disabled.
When LWT optimization was implemented in gocql (https://github.com/scylladb/gocql/pull/49), all
newFramercalls were replaced withnewFramerWithExtscalls.Previously, during the upstream merging the code using
newFramerwas added (https://github.com/scylladb/gocql/pull/109) and it was forgotten to replace it withnewFramerWithExts. That way, theflagLWTfield is set to 0 by default, causing the driver to consider every query executed as a LWT query. For example simpleINSERTorSELECTqueries are marked as LWT (SELECT pk, ck, v FROM keyspace1.table1 WHERE pk = x;)This can potentially impact the performance if we want to use
ShuffleReplicas()inTokenAwareHostPolicy. If query is marked as LWT the replica shuffling would be disabled.