[
https://issues.apache.org/jira/browse/CASSANDRA-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253282#comment-16253282
]
Alex Petrov commented on CASSANDRA-14007:
-----------------------------------------
The patch is trivial and can be found
[here|https://github.com/apache/cassandra/compare/trunk...ifesdjeen:CASSANDRA-14007],
there was no real reason to have this table as compact and it doesn't change
any output in this case.
However, there are still plenty cqllib tests failing from what seems to be a
concurrency or capture issue:
{code}
AssertionError: unexpected echo 'select * from ascii_with_special_chars where k
in (0, 1,, 2, 3);' instead of 'select * from ascii_with_special_chars where k
in (0, 1, 2, 3);'
{code}
Other tests fail with other duplicated characters. However, this should
probably be handled outside of scope of this ticket.
> cqlshlib tests fail due to compact table
> ----------------------------------------
>
> Key: CASSANDRA-14007
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14007
> Project: Cassandra
> Issue Type: Bug
> Components: Testing
> Reporter: Joel Knighton
> Assignee: Alex Petrov
>
> The pylib/cqlshlib tests fail on initialization with the error
> {{SyntaxException: <Error from server: code=2000 \[Syntax error in CQL
> query\] message="Compact tables are not allowed in Cassandra starting with
> 4.0 version.">}}.
> The table {{dynamic_columns}} is created {{WITH COMPACT STORAGE}}. Since
> [CASSANDRA-10857], this is no longer supported. It looks like dropping the
> COMPACT STORAGE modifier is enough for the tests to run, but I haven't looked
> if we should instead remove the table and all related tests entirely, or if
> there's an interesting code path covered by this that we should test in a
> different way now. [~ifesdjeen] might know at a glance.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
