-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExecuteBatchCAS not applied
, MapExecuteBatchCAS is applied
#1746
Comments
@danthegoodman1 Hello, I am investigating this issue. For now, I can verify that When using Also, If the data state matches the condition (like |
@testisnullus I'm not sure you've understood the issue, or rather I was likely not clear enough. The issue is that |
@danthegoodman1 I am testing on the Cassandra 4.1.4 version. The
I've called the
If I println the Could you please provide more information about your issues with the |
No errors, I noticed purely that it would never apply (checking the DB shows that it indeed did not apply), but if I simply swapped it with the |
Here is the keyspace and table I used func createKeyspace(s *gocql.Session) error {
if err := s.Query("CREATE KEYSPACE if not exists test WITH replication = {'class': 'NetworkTopologyStrategy', 'replication_factor' : 1}").Exec(); err != nil {
return fmt.Errorf("error creating keyspace: %w", err)
}
return nil
}
func createTable(s *gocql.Session) error {
if err := s.Query("create table if not exists testkv (key text, col text, ts bigint, val blob, primary key (key, col, ts)) with clustering order by (col desc, ts desc)").Exec(); err != nil {
return fmt.Errorf("error creating table: %w", err)
}
return nil
} |
@danthegoodman1 Hello, I've tested the The table looks like this after batch operation:
I can share the full code snippet with you also:
The |
Just tested on the latest ScyllaDB image (scylladb/scylla:latest), and it also works well without any issues. What version of GoCQL and Scylla do you use now? |
Scylla is still latest, gocql was version |
I was also quite confused considering I changed nothing on the query and simply swapped out |
@danthegoodman1 I cannot reproduce the issue for now :( |
I had just swapped out for the map one with no issues.
…On Mon, May 6, 2024 at 4:20 AM Danylo Savchenko ***@***.***> wrote:
@danthegoodman1 <https://github.com/danthegoodman1> I cannot reproduce
the issue for now :(
Does the issue affect executing queries for you or can you easily use the
MapExecuteBatchCAS() function for your operations? I will be tracking
this issue and will try to test the ExecuteBatchCAS() more closely to
identify this problem's root cause.
—
Reply to this email directly, view it on GitHub
<#1746 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEH3JLEDM2EDBGFGBXZCTK3ZA44MHAVCNFSM6AAAAABF3LN6KCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVGQZTEOJSGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Interestingly, I'm also having the same issue happen to me. What's even more strange is that even though |
Using the latest version of scylla on docker, I have the following code:
When using
ExecuteBatchCAS(b)
, theapplied
return would always befalse
, but when usingMapExecuteBatchCAS(b, make(map[string]interface{}))
(despite not actaully binding to anything),applied
would betrue
.Why is this? My understand is that it si a difference of binding only.
The text was updated successfully, but these errors were encountered: