Re: [VOTE] Release Apache Cassandra 1.2.3

2013-03-18 Thread Sylvain Lebresne 
Including my own, I count 5 binding +1, 2 other +1 and no -1, the vote
passes.
I'll get the artifacts published.

--
Sylvain


On Sun, Mar 17, 2013 at 5:27 AM, Eric Evans  wrote:

> [ Sylvain Lebresne ]
> > Some important bug fixed since 1.2.2, I propose the following artifacts
> for
> > release as 1.2.3.
> >
> > sha1: f07804e0d0cf57bc6e1e2924a7b926d55408f640
> > Git:
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.3-tentative
> > Artifacts:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-002/org/apache/cassandra/apache-cassandra/1.2.3/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-002/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~slebresne/
> >
> > The vote will be open for 72 hours (longer if needed).
>
> +1
>
> --
> Eric Evans
> eev...@sym-link.com
>

Unable to fetch large amount of rows

2013-03-18 Thread Pushkar Prasad 
Hi,

 

I have following schema:

 

TimeStamp

MACAddress

Data Transfer

Data Rate

LocationID

 

PKEY is (TimeStamp, MACAddress). That means partitioning is on TimeStamp,
and data is ordered by MACAddress, and stored together physically (let me
know if my understanding is wrong). I have 1000 timestamps, and for each
timestamp, I have 500K different MACAddress. 

 

When I run the following query, I get RPC Timeout exceptions:

 

 

Select * from db_table where Timestamp='...'

 

>From my understanding, this should give all the rows with just one disk
seek, as all the records for a particular timeStamp. This should be very
quick, however, clearly, that doesn't seem to be the case. Is there
something I am missing here? Your help would be greatly appreciated.

 

Thanks

PP

RE: Unable to fetch large amount of rows

2013-03-18 Thread Viktor Jevdokimov 
Please, stop flooding this mail list, your questions are not about Cassandra 
development, but about using it.

For Cassandra users there's users mail list: u...@cassandra.apache.org
Subscribe to Cassandra users mail list: user-subscr...@cassandra.apache.org





Best regards / Pagarbiai

Viktor Jevdokimov
Senior Developer

Email: viktor.jevdoki...@adform.com
Phone: +370 5 212 3063
Fax: +370 5 261 0453

J. Jasinskio 16C,
LT-01112 Vilnius,
Lithuania



Disclaimer: The information contained in this message and attachments is 
intended solely for the attention and use of the named addressee and may be 
confidential. If you are not the intended recipient, you are reminded that the 
information remains the property of the sender. You must not use, disclose, 
distribute, copy, print or rely on this e-mail. If you have received this 
message in error, please contact the sender immediately and irrevocably delete 
this message and any copies.> -Original Message-
> From: Pushkar Prasad [mailto:pushkar.pra...@airtightnetworks.net]
> Sent: Monday, March 18, 2013 16:30
> To: dev@cassandra.apache.org
> Subject: Unable to fetch large amount of rows
>
> Hi,
>
>
>
> I have following schema:
>
>
>
> TimeStamp
>
> MACAddress
>
> Data Transfer
>
> Data Rate
>
> LocationID
>
>
>
> PKEY is (TimeStamp, MACAddress). That means partitioning is on TimeStamp,
> and data is ordered by MACAddress, and stored together physically (let me
> know if my understanding is wrong). I have 1000 timestamps, and for each
> timestamp, I have 500K different MACAddress.
>
>
>
> When I run the following query, I get RPC Timeout exceptions:
>
>
>
>
>
> Select * from db_table where Timestamp='...'
>
>
>
> From my understanding, this should give all the rows with just one disk seek,
> as all the records for a particular timeStamp. This should be very quick,
> however, clearly, that doesn't seem to be the case. Is there something I am
> missing here? Your help would be greatly appreciated.
>
>
>
> Thanks
>
> PP