[jira] [Commented] (CASSANDRA-15081) LegacyLayout does not have same behavior as 2.x when handling unknown column names
[ https://issues.apache.org/jira/browse/CASSANDRA-15081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980398#comment-16980398 ] Pierre Belanger apache.org commented on CASSANDRA-15081: Title of this issue points to 2.x but comments refer mainly to 2.1. Does this relate or not to 2.2 as well? > LegacyLayout does not have same behavior as 2.x when handling unknown column > names > -- > > Key: CASSANDRA-15081 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15081 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Local Write-Read Paths >Reporter: Cameron Zemek >Assignee: Cameron Zemek >Priority: High > Labels: patch, pull-request-available > Fix For: 3.11.6 > > Attachments: 15081.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Due to a bug I haven't been able to reproduce the production cluster had > unknown column names. To replicate the issue for this test I did the > following: > {noformat} > $ ccm create -v 2.1.19 -n 1 -s bug > $ cat > schema.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text, "paylo!d" > text); > EOF > $ ccm node1 cqlsh -f schema.cql > $ export CASSANDRA_INCLUDE=~/.ccm/bug/node1/bin/cassandra.in.sh > $ cat > bug.json << 'EOF' > [ > {"key": "1", > "cells": [["","",1554432501209207], > ["paylo!d","hello world",1554432501209207], > ["payload","hello world",1554432501209207]]} > ] > EOF > $ ~/.ccm/repository/2.1.19/tools/bin/json2sstable -K test -c unknowntest > ~/bug.json > ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-Data.db{noformat} > Then test the behavior of unknown columns in 2.1: > {noformat} > $ ccm stop > $ ccm create -v 2.1.19 -n 1 -s bug2_1_19 > $ cat > schema2.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text); > EOF > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug2_1_19/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug2_1_19 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 2.1.19 | CQL spec 3.2.1 | Native protocol v3] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > id | payload > +- > 1 | hello world > (1 rows){noformat} > Compared to 3.11.4 which did the following: > {noformat} > $ ccm stop > $ ccm create -v 3.11.4 -n 1 -s bug3_11_4 > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug3_11_4/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug3_11_4 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read] > message="Operation failed - received 0 responses and 1 failures" > info={'failures': 1, 'received_responses': 0, 'required_responses': 1, > 'consistency': 'ONE'} > {noformat} > In the logs this resulted in an IllegalStateException from LegacyLayout line > 1127 > The expected behavior would be to ignore the column and return results the > same as in 2.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15081) LegacyLayout does not have same behavior as 2.x when handling unknown column names
[ https://issues.apache.org/jira/browse/CASSANDRA-15081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975187#comment-16975187 ] Michael Semb Wever commented on CASSANDRA-15081: We have no CI currently that runs [upgrade tests|https://github.com/apache/cassandra-dtest/tree/master/upgrade_tests] (unless you have a paid circleci account). To run the upgrade test in question i did the following (first time i've ever used the upgrade dtests locally). {code} # $cassandra_src needs to be a git clone, checked out to patched branch cd cassandra-dtest source ~/dtest/bin/activate export LOCAL_GIT_REPO=$cassandra_src python -m pytest --execute-upgrade-tests --cassandra-dir=$cassandra_src upgrade_tests/storage_engine_upgrade_test.py::TestStorageEngineUpgrade::test_update_and_drop_column python -m pytest --execute-upgrade-tests --cassandra-dir=$cassandra_src -s --keep-test-dir upgrade_tests/storage_engine_upgrade_test.py::TestBootstrapAfterUpgrade::test_update_and_drop_column // when done deactivate {code} > LegacyLayout does not have same behavior as 2.x when handling unknown column > names > -- > > Key: CASSANDRA-15081 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15081 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Local Write-Read Paths >Reporter: Cameron Zemek >Assignee: Cameron Zemek >Priority: High > Labels: patch, pull-request-available > Attachments: 15081.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Due to a bug I haven't been able to reproduce the production cluster had > unknown column names. To replicate the issue for this test I did the > following: > {noformat} > $ ccm create -v 2.1.19 -n 1 -s bug > $ cat > schema.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text, "paylo!d" > text); > EOF > $ ccm node1 cqlsh -f schema.cql > $ export CASSANDRA_INCLUDE=~/.ccm/bug/node1/bin/cassandra.in.sh > $ cat > bug.json << 'EOF' > [ > {"key": "1", > "cells": [["","",1554432501209207], > ["paylo!d","hello world",1554432501209207], > ["payload","hello world",1554432501209207]]} > ] > EOF > $ ~/.ccm/repository/2.1.19/tools/bin/json2sstable -K test -c unknowntest > ~/bug.json > ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-Data.db{noformat} > Then test the behavior of unknown columns in 2.1: > {noformat} > $ ccm stop > $ ccm create -v 2.1.19 -n 1 -s bug2_1_19 > $ cat > schema2.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text); > EOF > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug2_1_19/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug2_1_19 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 2.1.19 | CQL spec 3.2.1 | Native protocol v3] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > id | payload > +- > 1 | hello world > (1 rows){noformat} > Compared to 3.11.4 which did the following: > {noformat} > $ ccm stop > $ ccm create -v 3.11.4 -n 1 -s bug3_11_4 > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug3_11_4/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug3_11_4 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read] > message="Operation failed - received 0 responses and 1 failures" > info={'failures': 1, 'received_responses': 0, 'required_responses': 1, > 'consistency': 'ONE'} > {noformat} > In the logs this resulted in an IllegalStateException from LegacyLayout line > 1127 > The expected behavior would be to ignore the column and return results the > same as in 2.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15081) LegacyLayout does not have same behavior as 2.x when handling unknown column names
[ https://issues.apache.org/jira/browse/CASSANDRA-15081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968120#comment-16968120 ] Michael Semb Wever commented on CASSANDRA-15081: Thanks [~cam1982]. I believe you're correct. But it needs to be checked. I believe there's an upgrade dtest relevant. Will check it out and get back to you. > LegacyLayout does not have same behavior as 2.x when handling unknown column > names > -- > > Key: CASSANDRA-15081 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15081 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Local Write-Read Paths >Reporter: Cameron Zemek >Priority: High > Labels: patch, pull-request-available > Attachments: 15081.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Due to a bug I haven't been able to reproduce the production cluster had > unknown column names. To replicate the issue for this test I did the > following: > {noformat} > $ ccm create -v 2.1.19 -n 1 -s bug > $ cat > schema.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text, "paylo!d" > text); > EOF > $ ccm node1 cqlsh -f schema.cql > $ export CASSANDRA_INCLUDE=~/.ccm/bug/node1/bin/cassandra.in.sh > $ cat > bug.json << 'EOF' > [ > {"key": "1", > "cells": [["","",1554432501209207], > ["paylo!d","hello world",1554432501209207], > ["payload","hello world",1554432501209207]]} > ] > EOF > $ ~/.ccm/repository/2.1.19/tools/bin/json2sstable -K test -c unknowntest > ~/bug.json > ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-Data.db{noformat} > Then test the behavior of unknown columns in 2.1: > {noformat} > $ ccm stop > $ ccm create -v 2.1.19 -n 1 -s bug2_1_19 > $ cat > schema2.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text); > EOF > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug2_1_19/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug2_1_19 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 2.1.19 | CQL spec 3.2.1 | Native protocol v3] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > id | payload > +- > 1 | hello world > (1 rows){noformat} > Compared to 3.11.4 which did the following: > {noformat} > $ ccm stop > $ ccm create -v 3.11.4 -n 1 -s bug3_11_4 > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug3_11_4/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug3_11_4 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read] > message="Operation failed - received 0 responses and 1 failures" > info={'failures': 1, 'received_responses': 0, 'required_responses': 1, > 'consistency': 'ONE'} > {noformat} > In the logs this resulted in an IllegalStateException from LegacyLayout line > 1127 > The expected behavior would be to ignore the column and return results the > same as in 2.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15081) LegacyLayout does not have same behavior as 2.x when handling unknown column names
[ https://issues.apache.org/jira/browse/CASSANDRA-15081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968072#comment-16968072 ] Cameron Zemek commented on CASSANDRA-15081: --- [~mck] no input. As far as I could tell CASSANDRA-13939 shouldn't be affected by this, but to be honest I didn't fully understand that issue. I thought I mentioned it in just in case it might and someone more knowledgable might be able to injected if they see an issue. The unit tests passed so hoping that means I haven't broken anything elsewhere. > LegacyLayout does not have same behavior as 2.x when handling unknown column > names > -- > > Key: CASSANDRA-15081 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15081 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Local Write-Read Paths >Reporter: Cameron Zemek >Priority: High > Labels: patch, pull-request-available > Attachments: 15081.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Due to a bug I haven't been able to reproduce the production cluster had > unknown column names. To replicate the issue for this test I did the > following: > {noformat} > $ ccm create -v 2.1.19 -n 1 -s bug > $ cat > schema.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text, "paylo!d" > text); > EOF > $ ccm node1 cqlsh -f schema.cql > $ export CASSANDRA_INCLUDE=~/.ccm/bug/node1/bin/cassandra.in.sh > $ cat > bug.json << 'EOF' > [ > {"key": "1", > "cells": [["","",1554432501209207], > ["paylo!d","hello world",1554432501209207], > ["payload","hello world",1554432501209207]]} > ] > EOF > $ ~/.ccm/repository/2.1.19/tools/bin/json2sstable -K test -c unknowntest > ~/bug.json > ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-Data.db{noformat} > Then test the behavior of unknown columns in 2.1: > {noformat} > $ ccm stop > $ ccm create -v 2.1.19 -n 1 -s bug2_1_19 > $ cat > schema2.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text); > EOF > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug2_1_19/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug2_1_19 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 2.1.19 | CQL spec 3.2.1 | Native protocol v3] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > id | payload > +- > 1 | hello world > (1 rows){noformat} > Compared to 3.11.4 which did the following: > {noformat} > $ ccm stop > $ ccm create -v 3.11.4 -n 1 -s bug3_11_4 > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug3_11_4/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug3_11_4 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read] > message="Operation failed - received 0 responses and 1 failures" > info={'failures': 1, 'received_responses': 0, 'required_responses': 1, > 'consistency': 'ONE'} > {noformat} > In the logs this resulted in an IllegalStateException from LegacyLayout line > 1127 > The expected behavior would be to ignore the column and return results the > same as in 2.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15081) LegacyLayout does not have same behavior as 2.x when handling unknown column names
[ https://issues.apache.org/jira/browse/CASSANDRA-15081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965633#comment-16965633 ] Michael Semb Wever commented on CASSANDRA-15081: Thanks [~cam1982]. ||branch||circleci||asf jenkins tests||asf jenkins dtests|| |[cassandra-3.11_15081|https://github.com/apache/cassandra/compare/trunk...instaclustr:3.11-15081]|[circleci|https://circleci.com/gh/instaclustr/workflows/cassandra/tree/3.11-15081]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/29//badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/29/]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/700//badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/700]| > LegacyLayout does not have same behavior as 2.x when handling unknown column > names > -- > > Key: CASSANDRA-15081 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15081 > Project: Cassandra > Issue Type: Bug >Reporter: Cameron Zemek >Priority: High > Labels: patch, pull-request-available > Attachments: 15081.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Due to a bug I haven't been able to reproduce the production cluster had > unknown column names. To replicate the issue for this test I did the > following: > {noformat} > $ ccm create -v 2.1.19 -n 1 -s bug > $ cat > schema.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text, "paylo!d" > text); > EOF > $ ccm node1 cqlsh -f schema.cql > $ export CASSANDRA_INCLUDE=~/.ccm/bug/node1/bin/cassandra.in.sh > $ cat > bug.json << 'EOF' > [ > {"key": "1", > "cells": [["","",1554432501209207], > ["paylo!d","hello world",1554432501209207], > ["payload","hello world",1554432501209207]]} > ] > EOF > $ ~/.ccm/repository/2.1.19/tools/bin/json2sstable -K test -c unknowntest > ~/bug.json > ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-Data.db{noformat} > Then test the behavior of unknown columns in 2.1: > {noformat} > $ ccm stop > $ ccm create -v 2.1.19 -n 1 -s bug2_1_19 > $ cat > schema2.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text); > EOF > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug2_1_19/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug2_1_19 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 2.1.19 | CQL spec 3.2.1 | Native protocol v3] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > id | payload > +- > 1 | hello world > (1 rows){noformat} > Compared to 3.11.4 which did the following: > {noformat} > $ ccm stop > $ ccm create -v 3.11.4 -n 1 -s bug3_11_4 > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug3_11_4/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug3_11_4 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read] > message="Operation failed - received 0 responses and 1 failures" > info={'failures': 1, 'received_responses': 0, 'required_responses': 1, > 'consistency': 'ONE'} > {noformat} > In the logs this resulted in an IllegalStateException from LegacyLayout line > 1127 > The expected behavior would be to ignore the column and return results the > same as in 2.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15081) LegacyLayout does not have same behavior as 2.x when handling unknown column names
[ https://issues.apache.org/jira/browse/CASSANDRA-15081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16964623#comment-16964623 ] Cameron Zemek commented on CASSANDRA-15081: --- Unit test created https://github.com/apache/cassandra/pull/373/commits > LegacyLayout does not have same behavior as 2.x when handling unknown column > names > -- > > Key: CASSANDRA-15081 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15081 > Project: Cassandra > Issue Type: Bug >Reporter: Cameron Zemek >Priority: High > Labels: patch, pull-request-available > Attachments: 15081.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Due to a bug I haven't been able to reproduce the production cluster had > unknown column names. To replicate the issue for this test I did the > following: > {noformat} > $ ccm create -v 2.1.19 -n 1 -s bug > $ cat > schema.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text, "paylo!d" > text); > EOF > $ ccm node1 cqlsh -f schema.cql > $ export CASSANDRA_INCLUDE=~/.ccm/bug/node1/bin/cassandra.in.sh > $ cat > bug.json << 'EOF' > [ > {"key": "1", > "cells": [["","",1554432501209207], > ["paylo!d","hello world",1554432501209207], > ["payload","hello world",1554432501209207]]} > ] > EOF > $ ~/.ccm/repository/2.1.19/tools/bin/json2sstable -K test -c unknowntest > ~/bug.json > ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-Data.db{noformat} > Then test the behavior of unknown columns in 2.1: > {noformat} > $ ccm stop > $ ccm create -v 2.1.19 -n 1 -s bug2_1_19 > $ cat > schema2.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text); > EOF > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug2_1_19/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug2_1_19 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 2.1.19 | CQL spec 3.2.1 | Native protocol v3] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > id | payload > +- > 1 | hello world > (1 rows){noformat} > Compared to 3.11.4 which did the following: > {noformat} > $ ccm stop > $ ccm create -v 3.11.4 -n 1 -s bug3_11_4 > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug3_11_4/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug3_11_4 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read] > message="Operation failed - received 0 responses and 1 failures" > info={'failures': 1, 'received_responses': 0, 'required_responses': 1, > 'consistency': 'ONE'} > {noformat} > In the logs this resulted in an IllegalStateException from LegacyLayout line > 1127 > The expected behavior would be to ignore the column and return results the > same as in 2.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15081) LegacyLayout does not have same behavior as 2.x when handling unknown column names
[ https://issues.apache.org/jira/browse/CASSANDRA-15081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955264#comment-16955264 ] Michael Semb Wever commented on CASSANDRA-15081: ||branch||circleci||asf jenkins testall||asf jenkins dtests|| |[cassandra-3.11_15081|https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/cassandra-3.11_15081]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck/cassandra-3.11_15081]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-testall/62//badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-testall/62/]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/697//badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/697]| > LegacyLayout does not have same behavior as 2.x when handling unknown column > names > -- > > Key: CASSANDRA-15081 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15081 > Project: Cassandra > Issue Type: Bug >Reporter: Cameron Zemek >Priority: High > Labels: patch > Attachments: 15081.patch > > > Due to a bug I haven't been able to reproduce the production cluster had > unknown column names. To replicate the issue for this test I did the > following: > {noformat} > $ ccm create -v 2.1.19 -n 1 -s bug > $ cat > schema.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text, "paylo!d" > text); > EOF > $ ccm node1 cqlsh -f schema.cql > $ export CASSANDRA_INCLUDE=~/.ccm/bug/node1/bin/cassandra.in.sh > $ cat > bug.json << 'EOF' > [ > {"key": "1", > "cells": [["","",1554432501209207], > ["paylo!d","hello world",1554432501209207], > ["payload","hello world",1554432501209207]]} > ] > EOF > $ ~/.ccm/repository/2.1.19/tools/bin/json2sstable -K test -c unknowntest > ~/bug.json > ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-Data.db{noformat} > Then test the behavior of unknown columns in 2.1: > {noformat} > $ ccm stop > $ ccm create -v 2.1.19 -n 1 -s bug2_1_19 > $ cat > schema2.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text); > EOF > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug2_1_19/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug2_1_19 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 2.1.19 | CQL spec 3.2.1 | Native protocol v3] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > id | payload > +- > 1 | hello world > (1 rows){noformat} > Compared to 3.11.4 which did the following: > {noformat} > $ ccm stop > $ ccm create -v 3.11.4 -n 1 -s bug3_11_4 > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug3_11_4/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug3_11_4 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read] > message="Operation failed - received 0 responses and 1 failures" > info={'failures': 1, 'received_responses': 0, 'required_responses': 1, > 'consistency': 'ONE'} > {noformat} > In the logs this resulted in an IllegalStateException from LegacyLayout line > 1127 > The expected behavior would be to ignore the column and return results the > same as in 2.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15081) LegacyLayout does not have same behavior as 2.x when handling unknown column names
[ https://issues.apache.org/jira/browse/CASSANDRA-15081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812053#comment-16812053 ] Cameron Zemek commented on CASSANDRA-15081: --- [^15081.patch] I don't believe this patch causes regression for https://issues.apache.org/jira/browse/CASSANDRA-13939 {noformat} Connected to bug_patch at 127.0.0.1:9042. [cqlsh 5.0.1 | Cassandra 3.11.4-SNAPSHOT | CQL spec 3.4.4 | Native protocol v4] Use HELP for help. cqlsh> select * from test.unknowntest where id = 1; id | payload +- 1 | hello world (1 rows){noformat} Can see the patch fixes this bug. > LegacyLayout does not have same behavior as 2.x when handling unknown column > names > -- > > Key: CASSANDRA-15081 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15081 > Project: Cassandra > Issue Type: Bug >Reporter: Cameron Zemek >Priority: High > Attachments: 15081.patch > > > Due to a bug I haven't been able to reproduce the production cluster had > unknown column names. To replicate the issue for this test I did the > following: > {noformat} > $ ccm create -v 2.1.19 -n 1 -s bug > $ cat > schema.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text, "paylo!d" > text); > EOF > $ ccm node1 cqlsh -f schema.cql > $ export CASSANDRA_INCLUDE=~/.ccm/bug/node1/bin/cassandra.in.sh > $ cat > bug.json << 'EOF' > [ > {"key": "1", > "cells": [["","",1554432501209207], > ["paylo!d","hello world",1554432501209207], > ["payload","hello world",1554432501209207]]} > ] > EOF > $ ~/.ccm/repository/2.1.19/tools/bin/json2sstable -K test -c unknowntest > ~/bug.json > ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-Data.db{noformat} > Then test the behavior of unknown columns in 2.1: > {noformat} > $ ccm stop > $ ccm create -v 2.1.19 -n 1 -s bug2_1_19 > $ cat > schema2.cql << 'EOF' > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': '1'} AND durable_writes = true; > CREATE TABLE test.unknowntest (id int primary key, payload text); > EOF > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug2_1_19/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug2_1_19 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 2.1.19 | CQL spec 3.2.1 | Native protocol v3] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > id | payload > +- > 1 | hello world > (1 rows){noformat} > Compared to 3.11.4 which did the following: > {noformat} > $ ccm stop > $ ccm create -v 3.11.4 -n 1 -s bug3_11_4 > $ ccm node1 cqlsh -f schema2.cql > $ ccm stop > $ cp ~/.ccm/bug/node1/data0/test/unknowntest-/test-unknowntest-ka-1-* > ~/.ccm/bug3_11_4/node1/data0/test/unknowntest-/ > $ ccm start > $ ccm node1 cqlsh > Connected to bug3_11_4 at 127.0.0.1:9042. > [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4] > Use HELP for help. > cqlsh> select * from test.unknowntest where id = 1; > ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read] > message="Operation failed - received 0 responses and 1 failures" > info={'failures': 1, 'received_responses': 0, 'required_responses': 1, > 'consistency': 'ONE'} > {noformat} > In the logs this resulted in an IllegalStateException from LegacyLayout line > 1127 > The expected behavior would be to ignore the column and return results the > same as in 2.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org