[ 
https://issues.apache.org/jira/browse/CASSANDRA-15135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402194#comment-17402194
 ] 

Stefan Miklosovic commented on CASSANDRA-15135:
-----------------------------------------------

3.11 branch https://github.com/apache/cassandra/pull/1141/files
4.0 branch https://github.com/apache/cassandra/pull/1162

4.0 https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1053/
3.11 https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1052/

https://app.circleci.com/pipelines/github/adelapena/cassandra/789/workflows/81313de5-e1ef-4d07-9dff-c9979c89ccfb
https://app.circleci.com/pipelines/github/adelapena/cassandra/790/workflows/216952c5-1cfe-483c-8c15-ee491186d2e6


> SASI tokenizer options not validated before being added to schema
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-15135
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15135
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Feature/SASI
>            Reporter: Vincent White
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>             Fix For: 3.11.x, 4.0.x, 4.x
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> If you attempt to create a SASI index with an illegal argument combination 
> the index will be added to the schema tables before trying instantiate the 
> tokenizer which causes a RuntimeException. Since the index was written to the 
> schema tables, cassandra will hit the same exception and fail to start when 
> it tries to load the schema on boot.
>  The branch below includes a unit test to reproduce the issue.
> ||3.11||
> |[PoC|https://github.com/vincewhite/cassandra/commit/089547946d284ae3feb0d5620067b85b8fd66ebc]|
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to