Would you stand by that statement in case all colums inside the super
column need to be read? Why?
Thanks
Le 28 déc. 2011 19:26, "Edward Capriolo" a écrit :
> Super columns have the same fundamental problem and perform worse in
> general. So switching from composites to super columns is NEVER a
@Edward: Perhaps you missed to notice that I need to always retrieve 'all
columns' under the supercolumn at any time.. and as per my query
requirements if I use composite columns instead of supercolumns then it is
impossible to do wildcard queries like the ones asked in this thread's
headline but w
Also point worth noticing is that there might be at max 8-10 subcolumns
per supercolumn.
I need to write a subcolumn at a time( but always read entire supercolumn
at any time).
On Fri, Dec 30, 2011 at 12:20 AM, Aditya wrote:
> @Edward: Perhaps you missed to notice that I need to always retrieve
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 do not confirm to
a '
The use case in question was: Only accessing some columns.
Even if that is not the case:
SuperColumns: 1 extra level of nesting
Composite Colunns: Arbitrary levels of nesting
SuperColumns: More overhead (space on disk) then using your own delimiter '_'
SuperColumns: Likely going to be replaced i
Hi,
I am working on Cassandra 1.0.2 and thrift 0.6.1. I was trying to use Async
thrift libary to perform batch mutate operation on Cassandra. I tried
Cassandra server with both Sync and Async RPC server mode.
While the insert operation works like charm, batch mutate fails to write
even a single r
Hum...
Do you have this?
scf [b][1][a]=value
scf [b][1][x]=value
scf [b][7][b]=value
and you want to slice:
scf [b][1][*]
Which would result in
scf [b][1][a]=value
scf [b][1][x]=value
?
The composite version of this would be:
cf [b][1:a]=value
cf [b][1:x]=value
cf [b][7:b]=value
I am not sur
On Fri, Dec 30, 2011 at 1:42 AM, Edward Capriolo wrote:
> Hum...
>
> Do you have this?
> scf [b][1][a]=value
> scf [b][1][x]=value
> scf [b][7][b]=value
>
> and you want to slice:
> scf [b][1][*]
>
> Which would result in
>
> scf [b][1][a]=value
> scf [b][1][x]=value
>
> ?
>
Exactly I have this!
Hi Edward,
Thanks...although it looks from CASSANDRA-1377 comments that perhaps the
reserved characters in CF and keyspace names haven't been decided yet?
If it hasn't been decided yet I would suggest making it as relaxed as
possible (allowing '.' in addition to '-' and perhaps others...if
p
On 12/29/11, Scott Lewis wrote:
> Hi Edward,
>
> Thanks...although it looks from CASSANDRA-1377 comments that perhaps the
> reserved characters in CF and keyspace names haven't been decided yet?
> If it hasn't been decided yet I would suggest making it as relaxed as
> possible (allowing '.' in add
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).
On 12/29/11, Edward Capriolo wrote:
> On 12/29/11, Scott Lewis wrote:
>> Hi Edward,
>>
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
vi ./src/java/org/apache/cassandra/db/marshal/CompositeType.java
'end-of-component' byte should always be 0 for actual column name.
* However, it can set to 1 for query bounds. This allows to query for the
* equivalent of 'give me the full super-column'. That is, if during a slice
* query uses:
On Thu, Dec 29, 2011 at 3:13 PM, Edward Capriolo wrote:
>
> You seen to say you can query for a list of supercolumns, I am not
> sure how this works because the ColumnParent seems to only accept a
> single SuperColumn, but if you can do it I am not calling you a liar.
>
If you don't specify a sup
Thanks for the response Peter! I checked everything and it look good to me.
I am stuck with this for almost 2 days now. Has anyone had this issue?
Thanks,
Kamal
On Wed, Dec 28, 2011 at 2:05 PM, Kamal Bahadur wrote:
> Hi All,
>
> My Cassandra cluster has 4 nodes with a RF of 2. I am trying to ve
> Thanks for the response Peter! I checked everything and it look good to me.
>
> I am stuck with this for almost 2 days now. Has anyone had this issue?
While it is certainly possible that you're running into a bug, it
seems unlikely to me since it is the kind of bug that would affect
almost anyon
So you can do this with Cassandra, but you need more logic in your code.
Basically, you get the last safe number, M, then get N..M, if there are any
gaps, you try again reading those numbers. As long as you are not over writing
data, and you only update the last safe number after a successful
17 matches
Mail list logo
