> It's obviously still in progress, but CASSANDRA-16052
> <https://issues.apache.org/jira/browse/CASSANDRA-16052> may introduce
> some breaking changes to the 2i API.
>


Can you elaborate Caleb? To my understanding, we do not want (and this
thread is not about) permitting breaking changes from one version to the
next. Are there deprecated 2i APIs in 4.x that you will need removed for
16052 ?

Reply via email to