Re: Cannot mix counter and non counter columns in the same table

> I agree it makes code messier That's not a trivial point. It isn't just about doing two queries to read. Its also having to do two queries to write and remembering to do that in all the places. On Wed, Nov 2, 2016 at 1:56 AM, Cody Yancey wrote: > I agree it makes code

Re: Incremental repairs leading to unrepaired data

Can't say I have too many ideas. If load is low during the repair it shouldn't be happening. Your disks aren't overutilised correct? No other processes writing loads of data to them?

Re: Cannot mix counter and non counter columns in the same table

I agree it makes code messier, but you aren't really losing anything by separating them out into separate tables and then doing parallel queries. Counter tables already don't support atomic batch operations (all batch operations are unlogged), CAS operations (LWTs not supported) and have a whole

Schema not translated completely from Thrift protocol to CQL protocol

Hi, I am trying to move from using pycassa to native protocol in my project (which will let us upgrade the version of cassandra). My schema was defined using pycassa so it created a Column family using compact storage and it has 3 columns which are not part of the composite primary key (I know

Re: Cannot mix counter and non counter columns in the same table

Here is a solution that I have leverage. Ignore the count of the value and use a multi-part column name as it's value. For example: create column family stuff ( rowkey string, column string, value string. counter_to_ignore long, primary key( rowkey, column, value)); On Tue, Nov 1, 2016 at

Re: Cassandra reaper

ok thank you, I will try and update you. On Tue, Nov 1, 2016 at 10:57 AM, Alexander Dejanovski < a...@thelastpickle.com> wrote: > Running reaper with INFO level logging (that can be configured in the yaml > file), you should have a console output telling you what's going on. > > If you started

Re: commit log on NFS volume

The Second exception states there is a File of an sstable Missing. Is it possible you didnt only delete commit logs or nfs Mount is stale or Not mounted? Am 01.11.2016 19:52 schrieb "John Sanda" : > Using nfs for a distribited System like Cassandra is like putting a >>

Re: commit log on NFS volume

> > Using nfs for a distribited System like Cassandra is like putting a > Ferrari on a Truck and going for a Race with the Truck. It is simply > nonsense. As I mentioned in my original post, I am aware that using NFS is considered bad and even documented as an anti-pattern. Your analogy,

Re: native_transport_max_frame_size_in_mb vs max_value_size_in_mb

Since this is already commented this size check is disabled or its default set to 256MB and if we have higher sized SSTables those are going to mark currupted ? On Tue, Nov 1, 2016 at 11:47 AM, Lahiru Gamathige wrote: > Hi Users, > > I see that C* introduced

native_transport_max_frame_size_in_mb vs max_value_size_in_mb

Hi Users, I see that C* introduced max_value_size_in_mb and if a SSTable is larger than this it will be a currupted SSTable. In our current cluster I see tables with very large SSTables, and if we are migrating to new version should I increase this number ? But increasing max_value_size_in_mb to

Re: commit log on NFS volume

Using nfs for a distribited System like Cassandra is like putting a Ferrari on a Truck and going for a Race with the Truck. It is simply nonsense. Am 01.11.2016 19:39 schrieb "Vladimir Yudovin" : > Hi, > > it's not only performance issue. In case of network problem writer

Re: commit log on NFS volume

Hi, it's not only performance issue. In case of network problem writer tread can be blocked, also in case of failure loss of data can occur. Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Tue, 01 Nov 2016 14:10:10 -0400John

commit log on NFS volume

I know that using NFS is discouraged, particularly for the commit log. Can anyone shed some light into what kinds of problems I might encounter aside from performance? The reason for my inquiry is because I have some deployments with Cassandra 2.2.1 that use NFS and are experiencing some problems

Re: Cannot mix counter and non counter columns in the same table

Big Fat lol!!! Am 01.11.2016 19:02 schrieb "Ali Akhtar" : > ^ Stockholm syndrome :) > > On Tue, Nov 1, 2016 at 10:54 PM, Robert Wille wrote: > >> I used to think it was terrible as well. But it really isn’t. Just put >> your non-counter columns in a

Re: Cannot mix counter and non counter columns in the same table

^ Stockholm syndrome :) On Tue, Nov 1, 2016 at 10:54 PM, Robert Wille wrote: > I used to think it was terrible as well. But it really isn’t. Just put > your non-counter columns in a separate table with the same primary key. If > you want to query both counter and non-counter

Re: Cassandra reaper

Running reaper with INFO level logging (that can be configured in the yaml file), you should have a console output telling you what's going on. If you started reaper with memory back end, restarting it will reset it and you'll have to register your cluster again, but if you used postgres it will

Re: Cannot mix counter and non counter columns in the same table

I used to think it was terrible as well. But it really isn’t. Just put your non-counter columns in a separate table with the same primary key. If you want to query both counter and non-counter columns at the same time, just query both tables at the same time with asynchronous queries. On Nov

Re: Cassandra reaper

Cassandra version is 2.1.16 In my setup I don't see it is writting to any logs On Tue, Nov 1, 2016 at 10:25 AM, Alexander Dejanovski < a...@thelastpickle.com> wrote: > Do you have anything in the reaper logs that would show a failure of some > sort ? > Also, can you tell me which version of

Re: Cassandra reaper

Do you have anything in the reaper logs that would show a failure of some sort ? Also, can you tell me which version of Cassandra you're using ? Thanks On Tue, Nov 1, 2016 at 6:15 PM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thanks Alex, > > Forgot to mention but I did add the

Re: Cassandra reaper

Thanks Alex, Forgot to mention but I did add the cluster. See the status below. It says the status is running but I don't see any repair happening. this is in the same state from past 1 days. b/w there not much of data in cluster. [root@machine cassandra-reaper]# ./bin/spreaper status-repair 3

Re: Unsubscribe

That doesn't work. You need to send an email to user-unsubscribe@cassandra. apache.org On Sat, Oct 29, 2016 at 1:53 AM, dhanesh malviya wrote: > > > -- > Regards, > Dhanesh Malviya.. > -- *Scott Hirleman* *Head of US Marketing and Sales* www.smartcat.io

Re: Specifying multiple conditions for lightweight conditions?

Hi, Unfortunately CQL syntax doesn't allow use of OR operator in condition list: UPDATE [ keyspace_name. ] table_name [ USING TTL time_value | USING TIMESTAMP timestamp_value ] SET assignment [ , assignment ] . . . WHERE row_specification [ IF EXISTS | IF NOT EXISTS | IF condition [ AND

Re: Cassandra reaper

Hi, The first step in using reaper is to add a cluster to it, as it is a tool that can manage multiple clusters and does not need to be executed on a Cassandra node (you can run in on any edge node you want). You should run : ./bin/spreaper add-cluster 127.0.0.1 Where you'll replace 127.0.0.1 by

Re: Cannot mix counter and non counter columns in the same table

That's a terrible gotcha rule. On Tue, Nov 1, 2016 at 6:27 PM, Cody Yancey wrote: > In your table schema, you have KEYS and you have VALUES. Your KEYS are > text, but they could be any non-counter type or compound thereof. KEYS > obviously cannot ever be counters. > > Your

Re: Cannot mix counter and non counter columns in the same table

In your table schema, you have KEYS and you have VALUES. Your KEYS are text, but they could be any non-counter type or compound thereof. KEYS obviously cannot ever be counters. Your VALUES, however, must be either all counters or all non-counters. The official example you posted conforms to this

Re: Cannot mix counter and non counter columns in the same table

I'm not referring to the primary key, just to other columns. My primary key is a text, and my table contains a mix of texts, ints, and timestamps. If I try to change one of the ints to a counter and run the create table query, I get the error ' Cannot mix counter and non counter columns in the

Re: Cannot mix counter and non counter columns in the same table

For counter tables, non-counter types are of course allowed in the primary key. Counters would be meaningless otherwise. Thanks, Cody On Nov 1, 2016 7:00 AM, "Ali Akhtar" wrote: > In the documentation for counters: > >

Cannot mix counter and non counter columns in the same table

In the documentation for counters: https://docs.datastax.com/en/cql/3.1/cql/cql_using/use_counter_t.html The example table is created via: CREATE TABLE counterks.page_view_counts (counter_value counter, url_name varchar, page_name varchar, PRIMARY KEY (url_name, page_name) ); Yet if I

Specifying multiple conditions for lightweight conditions?

In the following query: UPDATE project SET last_due_at = '2013-01-01 00:00:00+0200' WHERE id = '1' IF last_due_at < '2013-01-01 00:00:00+0200'; The intent is to change the value of 'last_due_at' as long as 'last_due_at' isn't already set to a later date than the one I've supplied. The problem

Re: Incremental repairs leading to unrepaired data

That is not happening anymore since I am repairing a keyspace with much less data (the other one is still there in write-only mode). The command I am using is the most boring (even shed the -pr option so to keep anticompactions to a minimum): nodetool -h localhost repair It's executed

Re: Cassandra Poor Read Performance Response Time

+1 On Tue, Nov 1, 2016 at 2:10 AM, _ _ wrote: > Hi > > Currently i am running a cassandra cluster of 3 nodes (with it replicating > to both nodes) and am experiencing poor performance, usually getting second > response times when running queries when i am expecting/needing

Re: Does securing C*'s CQL native interface (running on port 9042) automatically secure its Thrift API interface (running on port 9160)?

It does, yes. Clients will be required to call the thrift login method with a valid set of credentials before performing any other RPC calls. btw, in versions of C* >= 2.2 the Thrift server is not enabled by default (CASSANDRA-9319). On Mon, Oct 31, 2016 at 4:50 PM, Li, Guangxing

Cassandra Poor Read Performance Response Time

Hi Currently i am running a cassandra cluster of 3 nodes (with it replicating to both nodes) and am experiencing poor performance, usually getting second response times when running queries when i am expecting/needing millisecond response times. Currently i have a table which looks like: