Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 47971 invoked from network); 31 Aug 2010 14:03:54 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 31 Aug 2010 14:03:54 -0000 Received: (qmail 74578 invoked by uid 500); 31 Aug 2010 14:03:52 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 74359 invoked by uid 500); 31 Aug 2010 14:03:49 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 74347 invoked by uid 99); 31 Aug 2010 14:03:49 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Aug 2010 14:03:49 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.213.44] (HELO mail-yw0-f44.google.com) (209.85.213.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Aug 2010 14:03:26 +0000 Received: by ywk9 with SMTP id 9so3095289ywk.31 for ; Tue, 31 Aug 2010 07:03:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.145.19 with SMTP id s19mr2023253ybd.276.1283263384664; Tue, 31 Aug 2010 07:03:04 -0700 (PDT) Received: by 10.151.39.17 with HTTP; Tue, 31 Aug 2010 07:03:04 -0700 (PDT) X-Originating-IP: [80.179.102.198] In-Reply-To: References: <968b952c-6621-ca3d-af24-974b81e174f7@me.com> <21AE7234-13D9-4315-8A0E-AA81B927A678@ecyrd.com> Date: Tue, 31 Aug 2010 17:03:04 +0300 Message-ID: Subject: Re: column family names From: David Boxenhorn To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=000e0cd519d8323cf2048f1f0a1f X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd519d8323cf2048f1f0a1f Content-Type: text/plain; charset=ISO-8859-1 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 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 say is a lot more unixy than windows like. > > Sorry, I don't share your concern for large scale operations here, but > sure, '_' does the trick for me now so thanks to Aaron for reminding me > about that. > > Some day I am sure there will be realized that unicode strings/byte arrays > are useful here like most other places in Cassandra (\w is a bit limited for > some of us living in the non-ascii part of the world...), but "what is the > XXX way" are not the type of topics I find interesting, so another time. > > Terje > > > > On Tue, Aug 31, 2010 at 5:30 PM, Benjamin Black wrote: > >> 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, 2010 at 11:55 PM, Terje Marthinussen >> wrote: >> > 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. >> > >> > Terje >> > >> > On Tue, Aug 31, 2010 at 3:39 PM, Janne Jalkanen < >> Janne.Jalkanen@ecyrd.com> >> > 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 >> >> makes sense. >> >> However, it does require an extra cognitive step for the maintainer, >> since >> >> the mapping between filenames and logical names is no longer >> immediately >> >> obvious. Especially with multiple files this can be a pain (e.g. >> Chinese >> >> logical names which map to pretty incomprehensible sequences that are >> >> laborious to look up). >> >> So my experience suggests to avoid it for ops reasons, and just go with >> >> simplicity. >> >> /Janne >> >> On Aug 31, 2010, at 08:39 , Terje Marthinussen wrote: >> >> >> >> Beyond aesthetics, specific reasons? >> >> >> >> Terje >> >> >> >> On Tue, Aug 31, 2010 at 11:54 AM, Benjamin Black wrote: >> >>> >> >>> URL encoding. >> >>> >> >> >> > >> > >> > > --000e0cd519d8323cf2048f1f0a1f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It's not so hard to implement your mapping suggestion = in your application, rather than in Cassandra, if you really want it.
<= br>
On Tue, Aug 31, 2010 at 1:05 PM, Terje Marthi= nussen <tma= rthinussen@gmail.com> wrote:
No benefit?
Ma= king it easier to use column families as part of your data model is a fairl= y good benefit, at least given the somewhat special data model cassandra of= fers. Much more of a benefit than the disadvantages I can imagine.

fileprefix=3D`sometool -fileprefix tablename`
is something I would s= ay is a lot more unixy than windows like.

Sorry, I don't share y= our concern for large scale operations here, but sure, '_' does the= trick for me now so thanks to Aaron for reminding me about that.

Some day I am sure there will be realized that unicode strings/byte arr= ays are useful here like most other places in Cassandra (\w is a bit limite= d for some of us living in the non-ascii part of the world...), but "w= hat is the XXX way" are not the type of topics I find interesting, so = another time.

Terje



On Tue, Aug 31, 2010 at 5:30 PM, Benjamin Black <b@b3k.us> wrote:
This is not the Unix way for good reason: it creates all manner of
operational challenges for no benefit. =A0This is how Windows does
everything and automation and operations for large-scale online
services is _hellish_ because of it. =A0This horse is sufficiently
beaten, though.


b

On Mon, Aug 30, 2010 at 11:55 PM, Terje Marthinussen
<tmarthinus= sen@gmail.com> wrote:
> Another option would of course be to store a mapping between dir/filen= ames
> and Keyspace/columns familes together with other info related to keysp= aces
> 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.
>
> Terje
>
> On Tue, Aug 31, 2010 at 3:39 PM, Janne Jalkanen <Janne.Jalkanen@ecyrd.com>= ;
> wrote:
>>
>> I've been doing it for years with no technical problems. Howev= er, 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 usin= g something else
>> makes sense.
>> However, it does require an extra cognitive step for the maintaine= r, since
>> the mapping between filenames and logical names is no longer immed= iately
>> obvious. Especially with multiple files this can be a pain (e.g. C= hinese
>> logical names which map to pretty incomprehensible sequences that = are
>> laborious to look up).
>> So my experience suggests to avoid it for ops reasons, and just go= with
>> simplicity.
>> /Janne
>> On Aug 31, 2010, at 08:39 , Terje Marthinussen wrote:
>>
>> Beyond aesthetics, specific reasons?
>>
>> Terje
>>
>> On Tue, Aug 31, 2010 at 11:54 AM, Benjamin Black <b@b3k.us> wrote:
>>>
>>> URL encoding.
>>>
>>
>
>


--000e0cd519d8323cf2048f1f0a1f--