We had many discussions around this back when this was added. There is a
transition ability in place. Users can set a native protocol flag to have the
server return results as if DROP COMPACT STORAGE was already run. In this way
you can update your applications to support the new way results
+1 to making DROP CS experimental (i.e. disabling it by default) w/ a link
to the docs explaining the possible side effects
The sooner we do that, the more defensible
https://issues.apache.org/jira/browse/CASSANDRA-16675 (a proposed solution
to the query performance issue mentioned above) becomes.
Thank you for bringing this subject up.
> not ready for production use unless users fully understand what they are
doing.
Thing is, there's no easy way around dropping compact storage. At the
moment of writing of 10857, we have collectively decided that we'll
document that the new columns are go
> We have three logos.
>
> 1. https://apache.org/logos/res/cassandra/cassandra-1.pdf
> 2. https://apache.org/logos/res/cassandra/cassandra-2.svg
> 3. https://apache.org/logos/res/cassandra/cassandra-3.svg
> …
> 4. https://apache.org/logos/res/cassandra/cassandra-4.png
Correction:
2.
https://svn
>
> I don't think it ever makes sense to log a password in plaintext, so
> my feeling is we should obfuscate there as well.
+1
Le ven. 4 juin 2021 à 22:06, Brandon Williams a écrit :
> On Fri, Jun 4, 2021 at 10:32 AM Stefan Miklosovic
> wrote:
> > I would re-iterate on FQL logging though. Wha
We have three logos.
1. https://apache.org/logos/res/cassandra/cassandra-1.pdf
2. https://apache.org/logos/res/cassandra/cassandra-2.svg
3. https://apache.org/logos/res/cassandra/cassandra-3.svg
The website displays the logo similar to the third version using a
text-less image and some text. I'
