18 PM, Adam Venturella wrote:
> So, it looks like it supports multipart user-data:
> Line 86 here:
> https://github.com/riptano/ComboAMI/blob/2.4/ds2_configure.py
>
>
> I make my multipart user data,
>
> text/plaintext
> text/cloud-config
>
> I need to do some confi
So, it looks like it supports multipart user-data:
Line 86 here:
https://github.com/riptano/ComboAMI/blob/2.4/ds2_configure.py
I make my multipart user data,
text/plaintext
text/cloud-config
I need to do some configuration and hook the cluster up to my puppet master.
The cluster get's configur
I am currently running 4 nodes, @ 1.2.2.
I was curious if it mattered what node I have my clients connect to. Using
the python cql driver :
https://pypi.python.org/pypi/cql/
It doesn't give me the option to specify multiple client addresses, just
one. Will this be an issue?
My assumption is that
TL;DR:
Is it possible to use WHERE IN on wide rows but only have it return the 1st
column of each of the rows in the IN()?
First, I am aware that WHERE IN (id1, id2, id3...N) is not the most
performant, and should not be used on large sets.
Assuming there is also little difference from just issui
Perfect! Thanks for the response Sylvain!
On Friday, March 1, 2013, Sylvain Lebresne wrote:
> On Fri, Mar 1, 2013 at 5:16 PM, Adam Venturella
>
> > wrote:
>
>> My ColumnFamily is defined as follows:
>>
>>
>> CREATE TABLE UserProfileHistory(
>&g
My ColumnFamily is defined as follows:
CREATE TABLE UserProfileHistory(
username text,
timestamp bigint, -- millis since epoch
data text, -- JSON
PRIMARY KEY (username, timestamp)
) WITH CLUSTERING ORDER BY (timestamp DESC);
Each insert on the username adds to the wide row. The
> Aaron Morton
> Freelance Cassandra Developer
> New Zealand
> @aaronmorton
> http://www.thelastpickle.com
> On 21/02/2013, at 7:43 AM, Adam Venturella wrote:
>> My data needs only require me to store JSON, and I can handle this in 1
>> column family by
My data needs only require me to store JSON, and I can handle this in 1
column family by prefixing row keys with a type, for example:
comments:{message_id}
Where comments: represents the prefix and {message_id} represents some row
key to a message object in the same column family.
In this case c
t;
>
> On 02/07/2013 11:04 PM, Adam Venturella wrote:
>
>> Has anyone encountered this before?
>> What did I most likely break or how do I fix it?
>>
>
>
Has anyone encountered this before?
What did I most likely break or how do I fix it?
In my experience, if you foresee needing to do a lot of updates where a
"master" record would need to propagate its changes to other
records, then in general a non-sql based data store may be the wrong fit
for your data.
If you have a lot of data that doesn't really change or is not linked in
some
Jared, how do you guys handle data backups for your ephemeral based cluster?
I'm trying to move to ephemeral drives myself, and that was my last
sticking point; asking how others in the community deal with backup in case
the VM explodes.
On Wed, Jan 16, 2013 at 1:21 PM, Jared Biel
wrote:
> We'
I have been using this successfully so far:
http://pypi.python.org/pypi/cql
On Sun, Jan 6, 2013 at 11:18 AM, Andreas Jung wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Are there any up-to-date Python bindings available that
> work with Cassandra 1.2?
>
> - -aj
> -BEGIN PGP S
Nevermind...
help CREATE_KEYSPACE; works wonders..
CREATE KEYSPACE
WITH replication = {'class':'SimpleStrategy',
'replication_factor':3};
=)
On Sat, Dec 29, 2012 at 1:27 PM, Adam Venturella wrote:
> When I create a keyspace with a SimpleS
When I create a keyspace with a SimpleStrategy as outlined here:
https://cassandra.apache.org/doc/cql3/CQL.html#createKeyspaceStmt
CREATE KEYSPACE Test
WITH strategy_class = SimpleStrategy
AND strategy_options:replication_factor = 1;
I receive the following error:
Bad Re
hotosAlbumsIndex WHERE user_name='the_user' AND
> photo_id=;
>
> It seems to want the album name as well since it's part of the PK.
> Admittedly, I don't know how to get around that and just delete everything
> where the first 2 components of the PK are true.
>
part of the PK.
Admittedly, I don't know how to get around that and just delete everything
where the first 2 components of the PK are true.
You would already possess the list of album names though, so it could be
BATCH that you need to perform for the deletes, specifying 1 delete per
album_n
I am pretty new to cassandra as well. But here goes nothing:
Assumptions:
- You are using a CQL3 client
- Remember I am a n00bsauce at this as well, so another member of the list
may, and probably does, have a better more enlightened answer than I.
Everyone was new to this a one time though, and
Trying to better grasp compound primary keys and what they are conceptually
doing under the hood. When you create a table with a compound primary key
in cql3 (http://www.datastax.com/dev/blog/schema-in-cassandra-1-1) the
first part of the key is the partition key. I get that and the subsequent
part
e columns)
>
> You can do something similar for the annotations.
>
> Depending on your use case I would use UNIX epoch time if possible rather
> than a time uuid.
>
> Hope that helps.
>
> -
> Aaron Morton
> Freelance Cassandra Developer
> New Zealand
My use case is capturing some information about Instagram photos from the
API. I have 2 use cases. One, I need to capture all of the media data for
an account and two I need to be able to privately annotate that data. There
is some nuance in this, multiple http queries for example, but ignoring
tha
21 matches
Mail list logo