Yep Tyler is right
It seems I have trailing *\u* (null) characters , (one column name is
mymed_embrun.ma...@gmail.com the other mymed_embrun.ma...@gmail.com\u\u
for example)
I'm trying to know at what point they are created...
Thx
2012/9/21 Tyler Hobbs
> If you're seeing that in cas
Yep Tyler is right
It seems I have trailing *\u* (null) characters , (one column name is
mymed_embrun.ma...@gmail.com the other mymed_embrun.ma...@gmail.com\u\u
for example)
I'm trying to know at what point they are created...
Thx
2012/9/21 Tyler Hobbs
> If you're seeing that in cas
If you're seeing that in cassandra-cli, it's possible that there are some
non-printable characters in the name that the cli doesn't display, like the
NUL char (ascii 0). I opened a ticket for that somewhere, but in the
meantime, you may want to verify that they are identical with a real client.
O
They are. Can you provide some more information ?
What happens when you read the super column ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 18/09/2012, at 5:33 AM, Cyril Auburtin wrote:
> First sorry but I'm using an old version 0.
?
Kind regards,
Pieter Callewaert
From: Yuki Morishita [mailto:mor.y...@gmail.com]
Sent: dinsdag 22 mei 2012 16:21
To: user@cassandra.apache.org
Subject: Re: supercolumns with TTL columns not being compacted correctly
Data will not be deleted when those keys appear in other stables outside of
t; I am
> >> 100% sure all the data is invalid.
> >>
> >>
> >>
> >> Kind regards,
> >>
> >> Pieter Callewaert
> >>
> >>
> >>
> >> From: samal [mailto:samalgo...@gmail.com]
> >> Sent: dinsdag 2
written to the new one, while I am
>> 100% sure all the data is invalid.
>>
>>
>>
>> Kind regards,
>>
>> Pieter Callewaert
>>
>>
>>
>> From: samal [mailto:samalgo...@gmail.com]
>> Sent: dinsdag 22 mei 2012 14:33
>> To: user@cassandra
to the new one, while I am
> 100% sure all the data is invalid.
>
>
>
> Kind regards,
>
> Pieter Callewaert
>
>
>
> From: samal [mailto:samalgo...@gmail.com]
> Sent: dinsdag 22 mei 2012 14:33
> To: user@cassandra.apache.org
> Subject: Re: supercolumns with TTL c
>
>
> From: samal [mailto:samalgo...@gmail.com]
> Sent: dinsdag 22 mei 2012 14:33
> To: user@cassandra.apache.org (mailto:user@cassandra.apache.org)
> Subject: Re: supercolumns with TTL columns not being compacted correctly
>
>
>
>
> Data will remain till next compa
gc_grace is 0, but still
the data from the sstable is being written to the new one, while I am 100% sure
all the data is invalid.
Kind regards,
Pieter Callewaert
From: samal [mailto:samalgo...@gmail.com]
Sent: dinsdag 22 mei 2012 14:33
To: user@cassandra.apache.org
Subject: Re: supercolumns with TTL
Data will remain till next compaction but won't be available. Compaction
will delete old sstable create new one.
On 22-May-2012 5:47 PM, "Pieter Callewaert"
wrote:
> Hi,
>
> ** **
>
> I’ve had my suspicions some months, but I think I am sure about it.
>
> Data is being written by the SST
Hi,
I've had my suspicions some months, but I think I am sure about it.
Data is being written by the SSTableSimpleUnsortedWriter and loaded by the
sstableloader.
The data should be alive for 31 days, so I use the following logic:
int ttl = 2678400;
long timestamp = System.currentTimeMillis() * 1
Hmm .. it would be great if the supercolumns API remains. Also I
believe we can replace the full functionality of supercolumns through
composite column names in case this issue (related to reading multiple
column ranges) is
resolved:https://issues.apache.org/jira/browse/CASSANDRA-2710
On Sun
On Sat, Jan 7, 2012 at 5:42 PM, Rustam Aliyev wrote:
>> My suggestion is simple: don't use any deprecated stuff out there. In
>> practically any case there is a good reason why it's deprecated.
>
>
> SuperColumns are not deprecated.
The supercolumn API will remain:
My suggestion is simple: don't use any deprecated stuff out there. In
practically any case there is a good reason why it's deprecated.
SuperColumns are not deprecated.
On Sat Jan 7 19:51:55 2012, R. Verlangen wrote:
My suggestion is simple: don't use any deprecated stuf
heers
2012/1/7 Aklin_81
> I read entire columns inside the supercolumns at any time but as for
> writing them, I write the columns at different times. I don't have the
> need to update them except that die after their TTL period of 60 days.
> But since they are going to be depr
I read entire columns inside the supercolumns at any time but as for
writing them, I write the columns at different times. I don't have the
need to update them except that die after their TTL period of 60 days.
But since they are going to be deprecated, I don't know if it would be
really
supercolumn API/abstraction
to remain at least for backwards compatibility.
Please understand that under the hood, supercolumns are merely groups of
columns serialized as a single block of data.
The fact that there is a specialized and hardcoded way to serialize these
column groups into supercolumns
Any comments please ?
On Thu, Jan 5, 2012 at 11:07 AM, Aklin_81 wrote:
> I have seen supercolumns usage been discouraged most of the times.
> However sometimes the supercolumns seem to fit the scenario most
> appropriately not only in terms of how the data is stored but also in
> ter
I have seen supercolumns usage been discouraged most of the times.
However sometimes the supercolumns seem to fit the scenario most
appropriately not only in terms of how the data is stored but also in
terms of how is it retrieved. Some of the queries supported by SCs are
uniquely capable of doing
ave ids steve or greg.
Cheers,
Steve
-Original Message-
From: Jeremiah Jordan [mailto:jeremiah.jor...@morningstar.com]
Sent: Tuesday, January 03, 2012 3:12 PM
To: user@cassandra.apache.org
Cc: Asil Klin
Subject: Re: Replacing supercolumns with composite columns; Getting
the eq
n that case, you can easily tell the names of all columns
you want to retrieve, so you can make a query to retrieve those list
of composite columns.
@Jeremiah,
So where is my best bet ? Should I leave the supercolumns as it is as
of now, since I can find a good way to use them incase I replace
ers between 4 and 10 which have ids
steve or greg.
Cheers,
Steve
-Original Message-
From: Jeremiah Jordan [mailto:jeremiah.jor...@morningstar.com]
Sent: Tuesday, January 03, 2012 3:12 PM
To: user@cassandra.apache.org
Cc: Asil Klin
Subject: Re: Replacing supercolumns with composite columns; Getting
Cheers,
Steve
From: rajkumar@gmail.com [mailto:rajkumar@gmail.com] On Behalf Of Asil
Klin
Sent: Wednesday, January 04, 2012 12:21 AM
To: user@cassandra.apache.org
Subject: Re: Replacing supercolumns with composite columns; Getting the
equivalent of retrieving a list of supercolumns by name
@Stephan: in that case, you can easily tell the names of all columns you
want to retrieve, so you can make a query to retrieve those list of
composite columns.
@Jeremiah,
So where is my best bet ? Should I leave the supercolumns as it is as of
now, since I can find a good way to use them incase
e ids
steve or greg.
Cheers,
Steve
-Original Message-
From: Jeremiah Jordan [mailto:jeremiah.jor...@morningstar.com]
Sent: Tuesday, January 03, 2012 3:12 PM
To: user@cassandra.apache.org
Cc: Asil Klin
Subject: Re: Replacing supercolumns with composite columns; Getting the
equivale
er columns, you can pull
all those out with a single multiget and you don't have to pull the rest
of the columns...
So there are pros and cons...
-Jeremiah
On 01/03/2012 01:58 PM, Asil Klin wrote:
I have a super columns family which I always use to retrieve a list of
supercolumns(wi
I have a super columns family which I always use to retrieve a list of
supercolumns(with all subcolumns) by name. I am looking forward to replace
all SuperColumns in my schema with the composite columns.
How could I design schema so that I could do the equivalent of retrieving a
list of
ct: Re: The use of SuperColumns
I'm also very curious about this. How deprecated/discouraged are super
columns? Are they going to go away? What are the downsides to using them?
Ernie
On Fri, Nov 4, 2011 at 5:13 PM, Dwight Smith
wrote:
There have been mentions that the use of SuperColumns i
I'm also very curious about this. How deprecated/discouraged are super
columns? Are they going to go away? What are the downsides to using them?
Ernie
On Fri, Nov 4, 2011 at 5:13 PM, Dwight Smith <
dwight.sm...@alcatel-lucent.com> wrote:
> There have been mentions that the use o
There have been mentions that the use of SuperColumns is not really
encouraged, recommendation to use composite columns instead. Will
SuperColumns be removed. Any comments greatly appreciated
g-in-cassandra-5495633
>
> Hani
>
>
> On Wed, Oct 12, 2011 at 12:18 PM, Dean Hiller wrote:
>
>> I heard cassandra may be going the direction of removing super column and
>> users are starting to just use prefixes in front of the column.
>>
>> The reason I a
cassandra may be going the direction of removing super column and
> users are starting to just use prefixes in front of the column.
>
> The reason I ask is I was going the way of only using supercolumns and then
> many tables were fixed with just one supercolumn per row as the struc
I heard cassandra may be going the direction of removing super column and
users are starting to just use prefixes in front of the column.
The reason I ask is I was going the way of only using supercolumns and then
many tables were fixed with just one supercolumn per row as the structure
for that
you'll find a response to this question on the phpcassa mailing list ...
where you asked the same question.
-sd
On Wed, Jun 8, 2011 at 10:22 AM, amrita wrote:
> Hi,
> Can u please tell me how to create a supercolumn and retrieve data from it
> using
> phpcassa???
>
> student_details{{,,{,}}}
>
Hi,
Can u please tell me how to create a supercolumn and retrieve data from it using
phpcassa???
student_details{{,,{,}}}
nhorn wrote:
>>
>>> Mike, my problem is that I have an database and codebase that already
>>> uses supercolumns. If I had to do it over, it wouldn't use them, for the
>>> reasons you point out. In fact, I have a feeling that over time supercolumns
>>> wi
> for older data).
>
> On Thu, Feb 10, 2011 at 12:32 AM, David Boxenhorn wrote:
>
>> Mike, my problem is that I have an database and codebase that already uses
>> supercolumns. If I had to do it over, it wouldn't use them, for the reasons
>> you point out. In
rt on the client side, but that is tedious and not logical
for older data).
On Thu, Feb 10, 2011 at 12:32 AM, David Boxenhorn wrote:
> Mike, my problem is that I have an database and codebase that already uses
> supercolumns. If I had to do it over, it wouldn't use them, for the reasons
Mike, my problem is that I have an database and codebase that already uses
supercolumns. If I had to do it over, it wouldn't use them, for the reasons
you point out. In fact, I have a feeling that over time supercolumns will
become deprecated de facto, if not de jure. That's why I wou
: Wednesday, February 09, 2011 20:59
To: user@cassandra.apache.org
Subject: Re: Do supercolumns have a purpose?
I still think super-columns are useful you just need to be aware of
the limitations...
Bye,
Norman
2011/2/9 Mike Malone :
> On Tue, Feb 8, 2011 at 2:03 AM, David Boxenhorn wr
On Thu, 2011-02-03 at 15:35 -0800, Mike Malone wrote:
> In my dealings with the Cassandra code, super columns end up making a
> mess all over the place when algorithms need to be special cased and
> branch based on the column/supercolumn distinction.
>
>
> I won't even mention what it does to t
. I can't easily stop using supercolumns. I need an upgrade path.
>
> David,
> Cassandra is open source and community developed. The right thing to do is
> what's best for the community, which sometimes conflicts with what's best
> for individual users. Such strife should b
On Tue, Feb 8, 2011 at 2:03 AM, David Boxenhorn wrote:
> Shaun, I agree with you, but marking them as deprecated is not good enough
> for me. I can't easily stop using supercolumns. I need an upgrade path.
>
David,
Cassandra is open source and community developed. The right
Shaun, I agree with you, but marking them as deprecated is not good enough
for me. I can't easily stop using supercolumns. I need an upgrade path.
On Tue, Feb 8, 2011 at 3:53 AM, Shaun Cutts wrote:
>
> I'm a newbie here, but, with apologies for my presumptuousness, I th
I'm a newbie here, but, with apologies for my presumptuousness, I think you
should deprecate SuperColumns. They are already distracting you, and as the
years go by the cost of supporting them as you add more and more functionality
is only likely to get worse. It would be better to concen
regular column families have.
My data model is full of supercolumns. I used them, even though I knew it
didn't *have to*, "because they were there", which implied to me that I was
supposed to use them for some good reason. Now I suspect that they will
gradually become less and less fun
On Fri, Feb 4, 2011 at 12:35 AM, Mike Malone wrote:
> On Thu, Feb 3, 2011 at 6:44 AM, Sylvain Lebresne wrote:
>
>> On Thu, Feb 3, 2011 at 3:00 PM, David Boxenhorn wrote:
>>
>>> The advantage would be to enable secondary indexes on supercolumn
>>> families.
>>>
>>
>> Then I suggest opening a ticke
On Thu, Feb 3, 2011 at 3:35 PM, Mike Malone wrote:
> It seems to me that super columns are a historical artifact from Cassandra's
> early life as Facebook's inbox storage system. They needed posting lists of
> messages, sharded by user. So that's what they built. In my dealings with
> the Cassandr
On Thu, Feb 3, 2011 at 6:44 AM, Sylvain Lebresne wrote:
> On Thu, Feb 3, 2011 at 3:00 PM, David Boxenhorn wrote:
>
>> The advantage would be to enable secondary indexes on supercolumn
>> families.
>>
>
> Then I suggest opening a ticket for adding secondary indexes to supercolumn
> families and vo
On Thu, Feb 3, 2011 at 6:49 AM, Jonathan Ellis wrote:
> On Thu, Feb 3, 2011 at 6:44 AM, Sylvain Lebresne wrote:
>> On Thu, Feb 3, 2011 at 3:00 PM, David Boxenhorn wrote:
>>>
>>> The advantage would be to enable secondary indexes on supercolumn
>>> families.
>>
>> Then I suggest opening a ticket
and vote
>>> for it. Don't expect too much support tough :)
>>>
>>>
>>>> What if supercolumn families were supported as regular column families +
>>>> an index (on what used to be supercolumn keys)? Would that solve some
>>>> p
On Thu, Feb 3, 2011 at 6:44 AM, Sylvain Lebresne wrote:
> On Thu, Feb 3, 2011 at 3:00 PM, David Boxenhorn wrote:
>>
>> The advantage would be to enable secondary indexes on supercolumn
>> families.
>
> Then I suggest opening a ticket for adding secondary indexes to supercolumn
> families and voti
on what used to be supercolumn keys)? Would that solve some
>>> problems?
>>>
>>
>> You'd still have to remember for each CF if it has this index on what used
>> to be supercolumn keys and handle those differently. Really not convince
>> this would mak
gt; this would make the code cleaner that how it is now. And making the code
> cleaner is really the only reason I can thing of for wanting to get rid of
> super columns internally, so ...
>
>
>>
>>
>> On Thu, Feb 3, 2011 at 2:00 PM, Sylvain Lebresne wrote:
>>
now. And making the code
cleaner is really the only reason I can thing of for wanting to get rid of
super columns internally, so ...
>
>
> On Thu, Feb 3, 2011 at 2:00 PM, Sylvain Lebresne wrote:
>
>> > Is there any advantage to using supercolumns
>> >
to be supercolumn keys)? Would that solve some problems?
On Thu, Feb 3, 2011 at 2:00 PM, Sylvain Lebresne wrote:
> > Is there any advantage to using supercolumns
> > (columnFamilyName[superColumnName[columnName[val]]]) instead of regular
> > columns with concatenated keys
> > (col
> Is there any advantage to using supercolumns
> (columnFamilyName[superColumnName[columnName[val]]]) instead of regular
> columns with concatenated keys
> (columnFamilyName[superColumnName@columnName[val]])?
>
> When I designed my data model, I used supercolumns wherever I need
Is there any advantage to using supercolumns
(columnFamilyName[superColumnName[columnName[val]]]) instead of regular
columns with concatenated keys
(columnFamilyName[superColumnName@columnName[val]])?
When I designed my data model, I used supercolumns wherever I needed two
levels of key depth
deleted. CheersAaron On 20 Jan, 2011,at 03:21 AM, Andy Burgess wrote:
In reply to my own question, I'm clearly talking nonsense.
SuperColumns
are cleared out when empty (because really,
what's the difference from the client point of view?) and so setting
In reply to my own question, I'm clearly talking nonsense.
SuperColumns are cleared out when empty (because really,
what's the difference from the client point of view?) and so setting
TTL at the Column level is plainly good enough. This was actually
solved b
e I've set
the TTL on my Columns, but actually, I need the SuperColumns to expire
too - I believe that my sstables remain large because I (probably) have
a lot of empty SuperColumns. Unfortunately, I can't see a way to set a
TTL on a SuperColumn.
Does anyone have any suggestio
o now it's behaving :)
#define ntohll(x) (((_int64)(ntohl((int)((x << 32) >> 32))) << 32) |
(unsigned int)ntohl(((int)(x >> 32
string result;
result.resize(sizeof(long long));
long long bigendian = htonll(l);
memcpy(&result[0], &bigendian, sizeof(long long));
=> (super_column=1291668233,
uh, ok I was just copying :P
string result;
result.resize(sizeof(long long));
memcpy(&result[0], &l, sizeof(long long));
I'll try and let you know
many thanks!
On Mon, Dec 6, 2010 at 4:29 PM, Tyler Hobbs wrote:
> How are you packing the longs into strings? The large negative numbers
+1
I'm doing this in my C++ client so contact me offlist if you need code
David
Sent from my iPhone
On Dec 6, 2010, at 1:33 PM, Tyler Hobbs wrote:
> Also, thought I should mention:
>
> When you make a std::string out of the char[], make sure to use the
> constructor with the size_t parameter
Also, thought I should mention:
When you make a std::string out of the char[], make sure to use the
constructor with the size_t parameter (size 8).
- Tyler
On Mon, Dec 6, 2010 at 12:29 PM, Tyler Hobbs wrote:
> That should be "big-endian".
>
>
> On Mon, Dec 6, 2010 at 12:29 PM, Tyler Hobbs wro
That should be "big-endian".
On Mon, Dec 6, 2010 at 12:29 PM, Tyler Hobbs wrote:
> How are you packing the longs into strings? The large negative numbers
> point to that being done incorrectly.
>
> Bitshifting and putting each byte of the long into a char[8] then
> stringifying the char[] is th
How are you packing the longs into strings? The large negative numbers
point to that being done incorrectly.
Bitshifting and putting each byte of the long into a char[8] then
stringifying the char[] is the best way to go. Cassandra expects
big-ending longs, as well.
- Tyler
On Mon, Dec 6, 2010
I'm using thrift in C++ and inserting the results in a vector of pairs, so
client-side-mangling does not seem to be the problem.
Also I'm using a "test" column where I insert the same value I'm using as
super column name (in this case the same date converted to string) and when
queried using cassa
What client are you using? Is it storing the results in a hash map or some
other type of
non-order preserving dictionary?
- Tyler
On Mon, Dec 6, 2010 at 10:11 AM, Guillermo Winkler wrote:
> Hi, I've the following schema defined:
>
> EventsByUserDate : {
> UserId : {
> epoch: { // SC
> IID,
>
Hi, I've the following schema defined:
EventsByUserDate : {
UserId : {
epoch: { // SC
IID,
IID,
IID,
IID
},
// and the other events in time
epoch: {
IID,
IID,
IID
}
}
}
Where I'm expecting to store all the event ids for a user ordered by date
(it's seconds since epoch as long long), I'm usin
On Fri, Nov 12, 2010 at 7:33 AM, Aditya Muralidharan
wrote:
> Thanks for the response. We're trying to get a general idea of the insert and
> retrieval performance, and we figured BinaryMemtable would be a great enabler
> for our bulk import scenarios. Normal thrift inserts are certainly fast, b
e our throughput.
Are you able to share some general performance numbers for thrift/avro/bmt?
Thanks.
AD
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Thursday, November 11, 2010 8:23 PM
To: user
Subject: Re: Cassandra 0.7 beta3 BinaryMemtable and Superco
>
> at
> org.apache.cassandra.db.RowMutationSerializer.deserialize(RowMutation.java:336)
>
> at
> org.apache.cassandra.db.RowMutationMessageSerializer.deserialize(RowMutationMessage.java:84)
>
> at
> org.apache.cassandra.db.BinaryVerbHandler.doVerb(BinaryVerbHand
at
org.apache.cassandra.db.BinaryVerbHandler.doVerb(BinaryVerbHandler.java:42)
... which is basically because the CFSerializer is (rightly) expecting to
deserialize a super column though the bmt_example serialized a Standard CF.
Any help on BMT with supercolumns would be appreciated.
Thanks.
AD
Is it possible for BinaryMemtable RowMutations to a ColumnFamily with
supercolumns?
I'll post the solution.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/how-to-retrieve-data-from-supercolumns-by-phpcassa-tp5416141p5419803.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
Thanks Justus,
I'll check it
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/how-to-retrieve-data-from-supercolumns-by-phpcassa-tp5416141p5419536.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
e similar.
/Justus
-Ursprungligt meddelande-
Från: lisek [mailto:m.lisow...@powerprice.pl]
Skickat: den 12 augusti 2010 15:49
Till: cassandra-u...@incubator.apache.org
Ämne: how to retrieve data from supercolumns by phpcassa ?
Hi all,
I've got cassandra superlcolumn lookin
get->('client', '2a3909c0-
a612-11df-b27e-346336336631') - but with no results... maybe I should
convert this "2a3909c0-a612-11df-b27e-346336336631" somehow before I
put it to get() ?
or maybe I'm thinking wrong way...
regards
--
View this message in
get_slice() as result, i got the super columns I
passed in the list with ALLl their columns in one call.
so now, just IF I WANTED TO, would it be possible to get just a subset
of columns contained in those supercolumns instead of all of them
assuming that the amount of columns are lot and for
Hi Aaron, the problem I have is that those UUIDs are random numbers.
2,3,4 are not sequential unfortunately. I don't think there is an API
like mutiget_slice for key but for Super Column names.
Is there any other way to specify a list of super column names to read
where those names are not sequent
Take a look at the get_slice function http://wiki.apache.org/cassandra/APIYou could send one with a ColumnParent that only specifies the ColumnFamily and a SlicePredicate with a SliceRange where the start and finish values are empty strings. Set the count to an appropriate level to get them all (
Hi all, apologize before hand if this question sounds a bit dumb but I
don't see what API I should use (if there is any)
this is my model:
row key A:
SC_UUID_1:
Col1, Col2, Col3
SC_UUID_2:
org
Subject: Re: Understanding SuperColumns
On Sun, Jun 27, 2010 at 7:36 PM, Anthony Ikeda
wrote:
Say my query is: Get all Work addresses in New York and the
address owner. Steps to get the data would be:
If this is the query you want to run, then you probably just want to put
t
On Sun, Jun 27, 2010 at 7:36 PM, Anthony Ikeda <
anthony.ik...@cardlink.com.au> wrote:
> Say my query is: Get all Work addresses in New York and the address
> owner. Steps to get the data would be:
>
>
>
If this is the query you want to run, then you probably just want to put the
owner in the in
So no one is able to help?
From: Anthony Ikeda [mailto:anthony.ik...@cardlink.com.au]
Sent: Monday, 28 June 2010 12:36 PM
To: user@cassandra.apache.org
Subject: Understanding SuperColumns
I seem to be scratching my head about how to model Super Columns
properly and how they relate to a 1
I seem to be scratching my head about how to model Super Columns
properly and how they relate to a 1 to many kind of relationship.
For example:
UserAccounts = {
"PB12345": {
firstname: "Paul",
surname: "Brown",
address: {street: "Main St", suburb: "Springfield", state: "
> can anybody give interface to create supercolumn in supercolumn and fill the
> data...in cassandra with example
That would be hard since you cannot have supercolumns in supercolumns.
Supercolumns give you one more level of nesting but that's it.
--
Sylvain
hi all,
can anybody give interface to create supercolumn in supercolumn and fill the
data...in cassandra with example
Thanks
bujji
Ok, thanks both
2010/4/15 Ted Zlatanov
> On Wed, 14 Apr 2010 23:34:52 -0700 Vijay wrote:
>
> V> On Wed, Apr 14, 2010 at 10:28 PM, Christian Torres >wrote:
>
> >> I'm defining a ColumnFamily (Table) type Super, It's posible to have a
> >> SuperCol
On Wed, 14 Apr 2010 23:34:52 -0700 Vijay wrote:
V> On Wed, Apr 14, 2010 at 10:28 PM, Christian Torres wrote:
>> I'm defining a ColumnFamily (Table) type Super, It's posible to have a
>> SuperColumn inside another SuperColumn or SuperColumns can only have normal
&g
Yes a super column can only have columns in it.
Regards,
On Wed, Apr 14, 2010 at 10:28 PM, Christian Torres wrote:
> I'm defining a ColumnFamily (Table) type Super, It's posible to have a
> SuperColumn inside another SuperColumn or SuperColumns can only have
I'm defining a ColumnFamily (Table) type Super, It's posible to have a
SuperColumn inside another SuperColumn or SuperColumns can only have normal
columns?
--
Christian Torres * Desarrollador Web * Guegue.com *
Celular: +505 84 65 92 62 * Loving of the Programming
Juan,
check the attached source file .
Cao Jiguang
2010-03-17
casablinca126.com
发件人： Juan Manuel Garcia del Moral
发送时间： 2010-03-17 00:09:53
收件人： user@cassandra.apache.org
抄送：
主题： Re: Re: SuperColumns in C++ API
Many thanks for your code, would you please send me the get_slice
g(chTmp);
> col_path.column.assign(strCol);
> client.insert(strKeyspace,strKey, col_path, strValue,time(NULL), ONE);
>}
> }
> catch(TException &tx)
> {
>printf("ERROR: %s\n", tx.what());
>error_num ++ ;
> }
>
RLEN];
string str_zeros;
while(iclose();
}
//---
cheers,
Cao Jiguang
2010-03-16
casablinca126.com
发件人： Juan Manuel Garcia del Moral
发送时间： 2010-03-16 05:16:50
收件人： user@cassandra.apache.org
抄送：
主题： Re: SuperColumns in C++ API
Ok, I'll c
>> >
> >> > any ideas?
> >> >
> >> > thanks in advance
> >> >
> >> > Juan
> >> >
> >> >
> >> > 2010/3/15 Jonathan Ellis
> >> >>
> >> >> check the server log for exception
l
>> >> wrote:
>> >> > Many thanks!
>> >> >
>> >> > That seems to be useful,
>> >> >
>> >> > But now I'm getting
>> >> > The error message: "Internal error processi
:
>> >> > Many thanks!
>> >> >
>> >> > That seems to be useful,
>> >> >
>> >> > But now I'm getting
>> >> > The error message: "Internal error processing insert"
>> >> >
>> >>
1 - 100 of 108 matches
Mail list logo
