From the help for create column family in the CLI…
- name: Name of the new column family. Names may only contain letters,
numbers and underscores.
The CF name is used as part of a file name that includes other information and
the "-" is used as a separator.
Cheers
-
Hi Edward,
On 12/29/2011 12:51 PM, Edward Capriolo wrote:
I never use '.' or '-' in anything. It tends to get object mapping,
code generation libraries, and interpreters upset. I just use a-z and
lower case and know that no one can take that away from me
(hopefully).
I don't necessarily disagr
>>> ./build.xml:>> handledirsep="yes"
>>> />
>>> ./CHANGES.txt: matches a '^\w+' regex. (CASSANDRA-1377)
>>> ./NEWS.txt: to the '^\w+' regex convention.
>>> ./NEWS.txt: - Keyspace and column family names that
matches a '^\w+' regex. (CASSANDRA-1377)
>> ./NEWS.txt: to the '^\w+' regex convention.
>> ./NEWS.txt: - Keyspace and column family names that do not confirm to
>> a '^\w+' regex
>>
>> * disallow invalid keyspace and column
ard Capriolo wrote:
Use the source :)
[edward@ec cas-trunk]$ grep regex ./*
./build.xml:
./build.xml:
./build.xml:
./CHANGES.txt: matches a '^\w+' regex. (CASSANDRA-1377)
./NEWS.txt: to the '^\w+' regex convention.
./NEWS.txt: - Keyspace and column family names that
Use the source :)
[edward@ec cas-trunk]$ grep regex ./*
./build.xml:
./build.xml:
./build.xml:
./CHANGES.txt: matches a '^\w+' regex. (CASSANDRA-1377)
./NEWS.txt: to the '^\w+' regex convention.
./NEWS.txt: - Keyspace and column family names that
I've noticed when creating column families that the name of the column
family apparently has some restrictions...e.g. the presence of a '.'
character in the column family name seems to throw an exception. Is
there anywhere articulated the restrictions on column family names
Never mind. I've got a hard-coded Count on the KeyRange set to 2 billion, which
is apparently beyond the maximum allowable.
From: Stephen Pope [mailto:stephen.p...@quest.com]
Sent: Thursday, August 25, 2011 11:15 AM
To: user@cassandra.apache.org
Subject: RE: Column Family names
Hmm...I
ndra.apache.org
Subject: Column Family names
Using 0.8.2, I've created a column family called "_Schema" (without the
quotes). For some reason, I can't seem to list the rows in it from the cli:
I've tried:
[default@BIM] list _Schema;
Syntax error at position 5: unexpect
Using 0.8.2, I've created a column family called "_Schema" (without the
quotes). For some reason, I can't seem to list the rows in it from the cli:
I've tried:
[default@BIM] list _Schema;
Syntax error at position 5: unexpected "_" for `list _Schema;`.
[default@BIM] list '_Schema';
Syntax error a
On Tue, Aug 31, 2010 at 5:05 AM, Terje Marthinussen
wrote:
> No benefit?
> Making it easier to use column families as part of your data model is a
> fairly good benefit
No, it's not. (This is why I'm of the opinion that blog posts
encouraging thinking of the cassandra model as a 4-level nested h
Then make a CF in which you store the mappings from UTF8 (or byte[]!)
names to CFs. Now all clients can read the same mappings. Problem
solved.
Still not solved because you have arbitrary, uncontrolled clients
doing arbitrary, uncontrolled things in the same Cassandra cluster?
You're doing it wr
Sure, but as I am likely to have multiple clients (which I may not control)
accessing a single store, I would prefer to keep such custom mappings out of
the client for consistency reasons (much bigger problem than any of the
operational issues highlighted so far).
Terje
On 31 Aug 2010, at 23
It's not so hard to implement your mapping suggestion in your application,
rather than in Cassandra, if you really want it.
On Tue, Aug 31, 2010 at 1:05 PM, Terje Marthinussen wrote:
> No benefit?
> Making it easier to use column families as part of your data model is a
> fairly good benefit, at
No benefit?
Making it easier to use column families as part of your data model is a
fairly good benefit, at least given the somewhat special data model
cassandra offers. Much more of a benefit than the disadvantages I can
imagine.
fileprefix=`sometool -fileprefix tablename`
is something I would sa
This is not the Unix way for good reason: it creates all manner of
operational challenges for no benefit. This is how Windows does
everything and automation and operations for large-scale online
services is _hellish_ because of it. This horse is sufficiently
beaten, though.
b
On Mon, Aug 30, 2
Exactly.
On Mon, Aug 30, 2010 at 11:39 PM, Janne Jalkanen
wrote:
>
> I've been doing it for years with no technical problems. However, using "%"
> as the escape char tends to, in some cases, confuse a certain operating
> system whose name may or may not begin with "W", so using something else
> m
Another option would of course be to store a mapping between dir/filenames
and Keyspace/columns familes together with other info related to keyspaces
and column families. Just add API/command line tools to look up the
filenames and maybe store the values in the files as well for recovery
purposes.
I've been doing it for years with no technical problems. However,
using "%" as the escape char tends to, in some cases, confuse a
certain operating system whose name may or may not begin with "W", so
using something else makes sense.
However, it does require an extra cognitive step for th
Beyond aesthetics, specific reasons?
Terje
On Tue, Aug 31, 2010 at 11:54 AM, Benjamin Black wrote:
> URL encoding.
>
>
URL encoding.
On Mon, Aug 30, 2010 at 5:55 PM, Aaron Morton wrote:
> under scores or URL encoding ?
> Aaron
> On 31 Aug, 2010,at 12:27 PM, Benjamin Black wrote:
>
> Please don't do this.
>
> On Mon, Aug 30, 2010 at 5:22 AM, Terje Marthinussen
> wrote:
>> Ah, sorry, I forgot that underscore was
under scores or URL encoding ?AaronOn 31 Aug, 2010,at 12:27 PM, Benjamin Black wrote:Please don't do this.
On Mon, Aug 30, 2010 at 5:22 AM, Terje Marthinussen
wrote:
> Ah, sorry, I forgot that underscore was part of \w.
> That will do the trick for now.
>
> I do not see the big issue with file n
Please don't do this.
On Mon, Aug 30, 2010 at 5:22 AM, Terje Marthinussen
wrote:
> Ah, sorry, I forgot that underscore was part of \w.
> That will do the trick for now.
>
> I do not see the big issue with file names though. Why not expand the
> allowed characters a bit and escape the file names?
Ah, sorry, I forgot that underscore was part of \w.
That will do the trick for now.
I do not see the big issue with file names though. Why not expand the
allowed characters a bit and escape the file names? Maybe some sort of URL
like escaping.
Terje
On Mon, Aug 30, 2010 at 6:29 PM, Aaron Morton
Moving to the user list.
The new restrictions were added as part of CASSANDRA-1377 for 0.6.5 and 0.7,
AFAIK it's to ensure the file names created for the CFs can be correctly
parsed. So it's probably not going to change.
The names have to match the \w reg ex class, which includes the underscor
anted to get an open opinion.
Do you all use singular or plural column family names in your keyspaces?
I have been using plural for years and I have worked at jobs that use singular and the reason behind it made sense too.
Thanks!Regards,Michael
I know this is an age old question. Kinda like the chicken and the egg. I
know that everyone's solution is different but I wanted to get an open
opinion.
Do you all use singular or plural column family names in your keyspaces?
I have been using plural for years and I have worked at jobs tha
27 matches
Mail list logo
