[
https://issues.apache.org/jira/browse/CASSANDRA-14072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16268456#comment-16268456
]
Stefan Podkowinski commented on CASSANDRA-14072:
------------------------------------------------
As for "moving target", I was really thinking about more fundamental, long
standing issues here. We shouldn't have to update the page that frequently. I
also wouldn't structure it version dependent, but rather by feature. Users
should be able to go to that page when asking themselves "what do I need to
know in case I want to use X".
There are a couple of issues that come to my mind. But there are certainly more
that could be added.
* Materialized views: list issues that have been mentioned in recent discussion
that led to flagging it as experimental. Summarize in more detail what you need
to expect in case you still want to use MVs.
* Incremental repairs: design issues that may lead to data inconsistencies
before 4.0.
* Secondary indexes + SASI: ???
* Schema changes: potential operational issues on large and busy clusters due
to lack of strongly consistent schema changes, CASSANDRA-10699
* New VNode allocation (allocate_tokens_for_keyspace): known critical issues,
see CASSANDRA-13348
> Create "Known Issues" page
> --------------------------
>
> Key: CASSANDRA-14072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14072
> Project: Cassandra
> Issue Type: New Feature
> Components: Documentation and Website
> Reporter: Stefan Podkowinski
> Priority: Minor
>
> We have a couple of limitations, bugs and issues that users should be aware
> of, but haven't been documented outside Jira. I'd like to suggest creating a
> "Known Issues" page that would contain a summary of long standing issues,
> e.g. related to MVs, repairs, indexes, ..
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
