[
https://issues.apache.org/jira/browse/CASSANDRA-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785246#comment-16785246
]
Joseph Lynch commented on CASSANDRA-14866:
------------------------------------------
[~adelapena] I think that this may have broken 2.2 dtests in test teardown. Can
you try running 2.2 dtests on circle and see if they pass for you?
For me I get a lot of "test teardown failure" because of the
enable_materialized_views included in the yaml now:
{noformat}
test teardown failure
Unexpected error found in node logs (see stdout for full details). Errors:
[ERROR [main] 2019-03-06 05:05:04,639 CassandraDaemon.java:670 - Exception
encountered during startup
org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml. Please
remove properties [enable_materialized_views] from your cassandra.yaml
at
org.apache.cassandra.config.YamlConfigurationLoader$MissingPropertiesChecker.check(YamlConfigurationLoader.java:146)
~[main/:na]
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:113)
~[main/:na]
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:85)
~[main/:na]
at
org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:151)
~[main/:na]
at
org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:133)
~[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:531)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:657)
[main/:na], ERROR [main] 2019-03-06 05:05:04,639 CassandraDaemon.java:670 -
Exception encountered during startup
org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml. Please
remove properties [enable_materialized_views] from your cassandra.yaml
at
org.apache.cassandra.config.YamlConfigurationLoader$MissingPropertiesChecker.check(YamlConfigurationLoader.java:146)
~[main/:na]
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:113)
~[main/:na]
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:85)
~[main/:na]
at
org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:151)
~[main/:na]
at
org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:133)
~[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:531)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:657)
[main/:na]]
{noformat}
For example, a run after your dtest change: [73
fails|https://circleci.com/gh/jolynch/cassandra/524#tests/containers/9]
Versus a run without your dtest change: [1
fail|https://circleci.com/gh/jolynch/cassandra/528#tests/containers/74]
> Issue a CQL native protocol warning if SASI indexes are enabled on a table
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-14866
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14866
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/SASI
> Reporter: Andrés de la Peña
> Assignee: Andrés de la Peña
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0, 3.11.x, 4.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If someone enables SASI indexes then we should return a native protocol
> warning that will be printed by cqlsh saying that they are beta quality still
> and you need to be careful with using them in production.
> This is motivated not only by [the existing bugs and
> limitations|https://issues.apache.org/jira/browse/CASSANDRA-12674?jql=project%20%3D%20CASSANDRA%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20sasi]
> but for the fact that they haven't been extensively tested yet.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
