You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scylla version (or git commit hash): 4.3.rc2, 4.4.dev-0.20201207.0cd05dd0fdc with build-id f6b2d03ddf484e23702c303e8058015fc3e8fc55
Cluster size: 1
OS (RHEL/CentOS/Ubuntu/AWS AMI): CentOS
CREATETABLEtest ( id int, rand_id uuid, value text, PRIMARY KEY(rand_id, id) );
CREATEINDEXON test(id);
... insert some data...
SELECT*FROM test WHERE id =1AND id =2;
Scylla crashes on the last statement with assertion error:
void seastar::backtrace<seastar::backtrace_buffer::append_backtrace()::{lambda(seastar::frame)#1}>(seastar::backtrace_buffer::append_backtrace()::{lambda(seastar::frame)#1}&&) at ./build/release/seastar/./seastar/include/seastar/util/backtrace.hh:59
(inlined by) ?? at ./build/release/seastar/./seastar/src/core/reactor.cc:732
(inlined by) seastar::print_with_backtrace(seastar::backtrace_buffer&) at ./build/release/seastar/./seastar/src/core/reactor.cc:753
(inlined by) seastar::print_with_backtrace(char const*) at ./build/release/seastar/./seastar/src/core/reactor.cc:760
The text was updated successfully, but these errors were encountered:
… column' from Dejan Mircevski
There were two problems with handling conflicting equalities on the same PK column (eg, c=1 AND c=0):
1. When the column is indexed, Scylla crashed (#7772)
2. Computing ranges and slices was throwing an exception
This series fixes them both; it also happens to resolve some old TODOs from restriction_test.
Tests: unit (dev, debug)
Closes#7804
* github.com:scylladb/scylla:
cql3: Fix value_for when restriction is impossible
cql3: Fix range computation for p=1 AND p=1
Previously, single_column_restrictions::value_for() assumed that a
column's restriction specifies exactly one value for the column. But
since 37ebe52, multiple equalities on the same column are allowed,
so the restriction could be a conjunction of conflicting
equalities (eg, c=1 AND c=0). That violates an assert and crashes
Scylla.
This patch fixes value_for() by gracefully handling the
impossible-restriction case.
Fixesscylladb#7772
Signed-off-by: Dejan Mircevski <dejan@scylladb.com>
(cherry picked from commit 46b4b59)
Message-Id: <20210527205909.207481-3-dejan@scylladb.com>
Fixesscylladb#1741.
Installation details
Scylla version (or git commit hash): 4.3.rc2, 4.4.dev-0.20201207.0cd05dd0fdc with build-id f6b2d03ddf484e23702c303e8058015fc3e8fc55
Cluster size: 1
OS (RHEL/CentOS/Ubuntu/AWS AMI): CentOS
Scylla crashes on the last statement with assertion error:
Decoded:
The text was updated successfully, but these errors were encountered: