[jira] [Comment Edited] (CASSANDRA-6962) examine shortening path length post-5202
[ https://issues.apache.org/jira/browse/CASSANDRA-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997782#comment-13997782 ] Joshua McKenzie edited comment on CASSANDRA-6962 at 5/14/14 5:10 PM: - CASSANDRA-4110 and the limitations in Schema.java provide us some protection but there's really nothing to stop users nesting their cassandra data 250 characters deep in a path and having things blow up on them regardless of what length we limit ourselves to. On snapshots we'll be using 204 chars worst-case (48 KS, 48 CF, *2 each, 9 for "snapshots", 3 for \) so that doesn't leave us a lot of breathing room on path for data_file_directories. Maybe lowering the NAME_LENGTH in Schema.java would be appropriate given CASSANDRA-7136? Do we have a lot of users rolling out 40+ char KS and CF names in general, much less on Windows? was (Author: joshuamckenzie): CASSANDRA-4110 and the limitations in Schema.java provide us some protection but there's really nothing to stop users nesting their cassandra data 250 characters deep in a path and having things blow up on them regardless of what length we limit ourselves to. On snapshots we'll be using 204 chars worst-case (48 KS, 48 CF, *2 each, +9 for "snapshots", +3 for \) so that doesn't leave us a lot of breathing room on path for data_file_directories. Maybe lowering the NAME_LENGTH in Schema.java would be appropriate given CASSANDRA-7136? Do we have a lot of users rolling out 40+ char KS and CF names in general, much less on Windows? > 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)
[jira] [Comment Edited] (CASSANDRA-6962) examine shortening path length post-5202
[ https://issues.apache.org/jira/browse/CASSANDRA-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997782#comment-13997782 ] Joshua McKenzie edited comment on CASSANDRA-6962 at 5/14/14 5:10 PM: - CASSANDRA-4110 and the limitations in Schema.java provide us some protection but there's really nothing to stop users nesting their cassandra data 250 characters deep in a path and having things blow up on them regardless of what length we limit ourselves to. 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. Maybe lowering the NAME_LENGTH in Schema.java would be appropriate given CASSANDRA-7136? Do we have a lot of users rolling out 40+ char KS and CF names in general, much less on Windows? was (Author: joshuamckenzie): CASSANDRA-4110 and the limitations in Schema.java provide us some protection but there's really nothing to stop users nesting their cassandra data 250 characters deep in a path and having things blow up on them regardless of what length we limit ourselves to. On snapshots we'll be using 204 chars worst-case (48 KS, 48 CF, *2 each, 9 for "snapshots", 3 for \) so that doesn't leave us a lot of breathing room on path for data_file_directories. Maybe lowering the NAME_LENGTH in Schema.java would be appropriate given CASSANDRA-7136? Do we have a lot of users rolling out 40+ char KS and CF names in general, much less on Windows? > 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)