> The problems occurs during the day where updates can be sent that possibly
> contain older data then the nightly batch update.
If you have a an application level sequence for updates (I used that term to
avoid saying timestamp) you could use it as the cassandra timestamp. As long as
you know
that is, data consists of of an account id with a timestamp column that
indicates when the account was updated. This is not to be confused with row
insertion/update times tamp maintained by Cassandra for conflict resolution
within the Cassanda Nodes. Furthermore the account has about 200 columns
an
Thanks Tyler!
On Thu, Feb 3, 2011 at 12:06 PM, Tyler Hobbs wrote:
> On Wed, Feb 2, 2011 at 3:27 PM, Aditya Narayan wrote:
>>
>> Can I have some more feedback about my schema perhaps somewhat more
>> criticisive/harsh ?
>
> It sounds reasonable to me.
>
> Since you're writing/reading all of the
On Wed, Feb 2, 2011 at 3:27 PM, Aditya Narayan wrote:
> Can I have some more feedback about my schema perhaps somewhat more
> criticisive/harsh ?
>
It sounds reasonable to me.
Since you're writing/reading all of the subcolumns at the same time, I would
opt for a standard column with the tags se
Can I have some more feedback about my schema perhaps somewhat more
criticisive/harsh ?
Thanks again,
Aditya Narayan
On Wed, Feb 2, 2011 at 10:27 PM, Aditya Narayan wrote:
> @Bill
> Thank you BIll!
>
> @Cassandra users
> Can others also leave their suggestions and comments about my schema, plea
@Bill
Thank you BIll!
@Cassandra users
Can others also leave their suggestions and comments about my schema, please.
Also my question about whether to use a superColumn or alternatively,
just store the data (that would otherwise be stored in subcolumns) as
serialized into a single column in standa
I did not understand before... sorry.
Again, depending upon how many reminders you have for a single user, this could
be a long/wide row. Again, it really comes down to how many reminders are we
talking about and how often will they be read/written. While a single row can
contain millions (may
You got me wrong perhaps..
I am already splitting the row on per user basis ofcourse, otherwise
the schema wont make sense for my usage. The row contains only
*reminders of a single user* sorted in chronological order. The
reminder Id are stored as supercolumn name and subcolumn contain tags
for t
Any time I see/hear "a single row containing all ..." I get nervous. That single
row is going to reside on a single node. That is potentially a lot of load
(don't know the system) for that single node. Why wouldn't you split it by at
least user? If it won't be a lot of load, then why are you usi
I think you got it exactly what I wanted to convey except for few
things I want to clarify:
I was thinking of a single row containing all reminders (& not split
by day). History of the reminders need to be maintained for some time.
After certain time (say 3 or 6 months) they may be deleted by ttl
To reiterate, so I know we're both on the same page, your schema would be
something like this:
- A column family (as you describe) to store the details of a reminder. One
reminder per row. The row key would be a TimeUUID.
- A super column family to store the reminders for each user, for each
Actually, I am trying to use Cassandra to display to users on my
applicaiton, the list of all Reminders set by themselves for
themselves, on the application.
I need to store rows containing the timeline of daily Reminders put by
the users, for themselves, on application. The reminders need to be
p
Hey all,
I need to store supercolumns each with around 8 subcolumns;
All the data for a supercolumn is written at once and all subcolumns
need to be retrieved together. The data in each subcolumn is not big,
it just contains keys to other rows.
Would it be preferred to have a supercolumn family o
> Our team decided to use Cassandra as storage solution to a dataset.
> I am very new to the NoSQL world and Cassandra so I am hoping to get
> some help from the community: The dataset is pretty simple, we have
> for each key a number of columns with values. Each day we compute a
> new version of
The former.
On 11/19/10 7:31 AM, Chen Xinli wrote:
> 查询是完全基于当天计算的数据吗 还是基于当天和历史数据的合并？
>
> Nanheng Wu 编写：
>
>
> Hi,
>
> Our team decided to use Cassandra as storage solution to a dataset.
> I am very new to the NoSQL world and Cassandra so I am hoping to get
> some help from the community: The data
查询是完全基于当天计算的数据吗 还是基于当天和历史数据的合并？
Nanheng Wu 编写：
Hi,
Our team decided to use Cassandra as storage solution to a dataset.
I am very new to the NoSQL world and Cassandra so I am hoping to get
some help from the community: The dataset is pretty simple, we have
for each key a number of columns with
There´s a simple comparison that helped me a lot taking my first steps with
cassandra:
keyspace = database
CF = table
;o)
And this one: http://arin.me/blog/wtf-is-a-supercolumn-cassandra-data-model
Btw, love the new secondary indexes in cassandra 0.7, this saves a lot of
time and work! But don
Hi,
Our team decided to use Cassandra as storage solution to a dataset.
I am very new to the NoSQL world and Cassandra so I am hoping to get
some help from the community: The dataset is pretty simple, we have
for each key a number of columns with values. Each day we compute a
new version of this
, 2010 2:02 PM
To: user
Subject: Re: Design Question
Hi Mubarak,
Did you see David Strauss's talk on queing at the Summit?
http://riptano.blip.tv/file/4015190/
What specifics can you give as to how your use case is similar to /
different from what David covered?
On Sun, Nov 7, 2010 at 7:
Is the slide deck for this presentation online somewhere?
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Monday, November 08, 2010 2:02 PM
To: user
Subject: Re: Design Question
Hi Mubarak,
Did you see David Strauss's talk on queing at the Summit?
Hi Mubarak,
Did you see David Strauss's talk on queing at the Summit?
http://riptano.blip.tv/file/4015190/
What specifics can you give as to how your use case is similar to /
different from what David covered?
On Sun, Nov 7, 2010 at 7:05 PM, Mubarak Seyed wrote:
> Hi All,
> Can someone please v
FWIW I would recommend first trying to solve the issue in your application rather than with Cages or Zoo Keeper. Although I do not have experience with Cages or Zoo Keeper, it's another major server component in your stack.If you really do have a queue and multiple simultaneous readers consider usi
If you go the home-grown route, check out these musings on adapting
Lamport's Bakery algorithm to a similar problem:
http://wiki.apache.org/cassandra/Locking
On Sun, Nov 7, 2010 at 5:05 PM, Mubarak Seyed wrote:
> Hi All,
> Can someone please validate and recommend a solution for the given design
Hi All,
Can someone please validate and recommend a solution for the given design
problem?
*Problem statement:* Need to de-queue data from Cassandra (from Standard
ColumnFamily) using a job but multiple instances of a job can run
simultaneously (kinda multiple threads), trying to access a same ro
Perfectly right Nick.
So i suppose that If I want to keep RandomPartionner ( I understand this is
the best for high volume applications), I could design database like this :
A CF with key = UUID will contain log message details => allows me to split
real data evenly between nodes
A CF with key
On 02.07.10 16:10, yaw wrote:
> Hi all,
> I'd like to store logs of my application into cassandra.
>
> I need to query logs by date (last X logs) or user (give me last X logs
> for user Y ) and I want to dispatch data among several servers.
>
>
> I think the best design way is following
Hi all,
I'd like to store logs of my application into cassandra.
I need to query logs by date (last X logs) or user (give me last X logs for
user Y ) and I want to dispatch data among several servers.
I think the best design way is following :
Each log identifier is a time based UUID.
27 matches
Mail list logo
