-
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
Null tuple cause panic #1343
Comments
dahankzter
added a commit
to dahankzter/gocql
that referenced
this issue
Apr 2, 2020
In case the tuple value has never been written the unmarshalling used to panic. This is now handled by inspecting the data from the database and if it is missing (nil) it will set the tuple value to the corresponding default value. Fixes: apache#1343
dahankzter
added a commit
to scylladb/gocql
that referenced
this issue
Apr 3, 2020
In case the tuple value has never been written the unmarshalling used to panic. This is now handled by inspecting the data from the database and if it is missing (nil) it will set the tuple value to the corresponding default value. Fixes: apache#1343
Zariel
pushed a commit
that referenced
this issue
Apr 10, 2020
* tuples: correct unmarshalling of unset tuple values In case the tuple value has never been written the unmarshalling used to panic. This is now handled by inspecting the data from the database and if it is missing (nil) it will set the tuple value to the corresponding default value. Fixes: #1343 * tuples: scan target vars reset of unset tuple values
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please answer these questions before submitting your issue. Thanks!
What version of Cassandra are you using?
cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4
What version of Gocql are you using?
f6df828
What did you do?
What did you expect to see?
no panic
What did you see instead?
It happens while readInt function retrieves size from empty []byte
frame.go
marshal.go
There is comment on
Maybe this means that field should be category list<frozen<tuple<timeuuid, varchar>>>, but it's not panic case
The text was updated successfully, but these errors were encountered: