[
https://issues.apache.org/jira/browse/CASSANDRA-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002190#comment-14002190
]
Jonathan Ellis commented on CASSANDRA-6962:
-------------------------------------------
bq. Looks like it was lowered across the board and not on a per-platform basis.
Yeah, nobody *really* needs keyspace names that long; not worth explaining why
your linux snapshot broke when you moved to windows if we can avoid it.
bq. On snapshots we'll be using 204 chars worst-case (48 KS, 48 CF, *2 each, 9
for "snapshots", 3 for slashes) so that doesn't leave us a lot of breathing
room on path for data_file_directories.
So... review this for 3.0? It's not a ton of code.
> 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: 2.1 rc1
>
> Attachments: 6962-2.1.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)
