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

Berenguer Blasi edited comment on CASSANDRA-16476 at 3/12/21, 5:26 AM:
-----------------------------------------------------------------------

I like 'compact storage' better bc when grepping or searching for 'compact' 
compaction gets in the way. Whereas searching for 'compact storage' gets you 
where you intended. My 2cts :-)

Regarding the CQL.html iirc that's the help cqlsh brings up when it can't 
connect to the apache docs on a browser. Think a DC with limited outside 
connectivity. So I'd say it is important we update that specially since we've 
had bugs of users in that area confirming it is being used, even if little.


was (Author: bereng):
I like 'compact storage' better bc when grepping or searching for 'compact' 
compaction gets in the way. Whereas searching for 'compact storage' gets you 
where you intended. My 2cts :-)

> Update the Compact Storage related docs
> ---------------------------------------
>
>                 Key: CASSANDRA-16476
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16476
>             Project: Cassandra
>          Issue Type: Task
>          Components: Legacy/Local Write-Read Paths
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Low
>             Fix For: 4.0-rc
>
>
> Compact Storage partial support was returned recently. 
> We need to elaborate in the docs on what does this mean to the users.
>  * Compact Storage support was returned, except for the supercolumn tables.
>  * This was done because during the big 4.0 beta testing changes of behavior 
> after DROP COMPACT STORAGE usage were revealed.   
> /CC [~ifesdjeen]



--
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