7;s
> another topic.
>
> C*heers
> ---
> Alain Rodriguez - al...@thelastpickle.com
> France / Spain
>
> The Last Pickle - Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> Le mar. 4 juin 2019 à 18:31, William R a écrit :
>
>> Hi Al
possible scope of those, such as good practices, testing
> and automations.
>
> C*heers,
> ---
> Alain Rodriguez - al...@thelastpickle.com
> France / Spain
>
> The Last Pickle - Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> Le mar. 4 juin
Hi,
Was an accidental decommissioning of a node and we really need to to cancel
it.. is there any way? At the moment we keep the node down before figure out a
way to cancel that.
Thanks
nts of data, I like nodes that have about 2.5 – 3
>> TB of usable SSD disk.
>>
>>
>>
>> It is possible that your nodes might be under-utilized, especially at first.
>> But if the hardware is already available, you have to use what you have.
>>
>&g
Hi all,
In our small company we have 10 nodes of (2 x 3 TB HD) 6 TB each, 128 GB ram
and 64 cores and we are thinking to use them as Cassandra nodes. From what I am
reading around, the community recommends that every node should not keep more
than 1 TB data so in this case I am wondering if it
What would/could take so long for the nodes to agree? It's a small cluster (7
nodes) all on local LAN and not being used by anything else.
I think a delete & refresh might be in order...
Thanks!
Bill-
On 02/15/2011 09:13 PM, Jonathan Ellis wrote:
"command never returns" means "it's waiting f
I know nothing about postgis and little about spacial data, but if you're simply
talking about data that relates to some latitude & longitude pair, you could
have your row key simply be the concatenation of the two: lat:long.
Can you provide more details about the type of data you're looking to
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 that reminder.
On Wed, Feb 2, 2011 at 9:19 PM, William R
JJ you need to be sending this to: user-unsubscr...@cassandra.apache.org
Cheers...
Bill-
On 02/02/2011 10:58 AM, JJ wrote:
Sent from my iPad
n a preferable choice for this ? Can there be a better
schema than this ?
-Aditya Narayan
On Wed, Feb 2, 2011 at 8:54 PM, William R Speirs wrote:
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 t
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
I'm still very new to Cassandra, but when I started reading about it the first
thing I thought about was a session store. It's based (in part from what I
understand) on Dynamo which is (again, I could be wrong) used at Amazon as the
session store for your shopping cart.
So I would certainly re
I'm very new to Cassandra, but I'll pitch in my $0.02.
Row look-ups are super fast, why do you think it would be more efficient to
store these two rows "together" in the super column method you describe?
Why would you not just look-up the rows, one after the other?
If I understand correctly,
Ah, sweet... thanks for the link!
Bill-
On 01/26/2011 08:20 PM, buddhasystem wrote:
Bill, it's all explained here:
http://wiki.apache.org/cassandra/MemtableThresholds#JVM_Heap_Size,the
Watch the number of CFs and the memtable sizes.
In my experience, this all matters.
It makes sense that the single row for a system (with a growing number of
columns) will reside on a single machine.
With that in mind, here is my updated schema:
- A single column family for all the messages. The row keys will be the TimeUUID
of the message with the following columns: date/tim
15 matches
Mail list logo
