[
https://issues.apache.org/jira/browse/CASSANDRA-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042415#comment-14042415
]
Joshua McKenzie commented on CASSANDRA-6962:
--------------------------------------------
w/len 48 CF and KS and a long username (30 chars), on Windows path length still
allows a bit over 50 chars for a secondary index name - should be plenty.
File names look good, tmp names, snapshots, secondary indexes all check out on
both linux and windows.
+1
> examine shortening path length post-5202
> ----------------------------------------
>
> Key: CASSANDRA-6962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6962
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Brandon Williams
> Assignee: Yuki Morishita
> Fix For: 3.0
>
> Attachments: 6962-2.1.txt, 6962-3.0.txt
>
>
> From CASSANDRA-5202 discussion:
> {quote}
> Did we give up on this?
> Could we clean up the redundancy a little by moving the ID into the directory
> name? e.g., ks/cf-uuid/version-generation-component.db
> I'm worried about path length, which is limited on Windows.
> Edit: to give a specific example, for KS foo Table bar we now have
> /var/lib/cassandra/flush/foo/bar-2fbb89709a6911e3b7dc4d7d4e3ca4b4/foo-bar-ka-1-Data.db
> I'm proposing
> /var/lib/cassandra/flush/foo/bar-2fbb89709a6911e3b7dc4d7d4e3ca4b4/ka-1-Data.db
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
