[ https://issues.apache.org/jira/browse/CASSANDRA-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940444#comment-17940444 ]
Caleb Rackliffe commented on CASSANDRA-20402: --------------------------------------------- bq. So I'd say changing testReadOnlyIndex and testWriteOnlyIndex exceptions is probably the right way to fix this. Caleb Rackliffe, what do you think? Sounds good to me. > Create new RequestFailureReason - INDEX_BUILDING and return it to end users > while an index is building > ------------------------------------------------------------------------------------------------------ > > Key: CASSANDRA-20402 > URL: https://issues.apache.org/jira/browse/CASSANDRA-20402 > Project: Apache Cassandra > Issue Type: Improvement > Components: Feature/2i Index, Feature/SAI > Reporter: Ekaterina Dimitrova > Assignee: Ekaterina Dimitrova > Priority: Normal > Fix For: 5.x > > > Currently, we return INDEX NOT AVAILABLE to the users while an index is > building, which makes it unclear to users whether the index is building or > there is an issue. > Differentiate the two cases by adding INDEX_BUILDING. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org