I don't think you can avoid that.
I'd suggest making it CQL-only if we do doubles -- no backwards
incompatibility required there.
On Mon, Jun 27, 2011 at 7:07 PM, Jason wrote:
> Sorry, I should have been more clear; I was speaking to the question of how
> to avoid modifying the thrift interface
Sorry, I should have been more clear; I was speaking to the question of how to
avoid modifying the thrift interface.
- Jason
On Jun 27, 2011, at 7:58 PM, Joseph Stein wrote:
> hmmm, well Jason it is not as accurate as I would have thought at first and
> the increments on the long are whacked
hmmm, well Jason it is not as accurate as I would have thought at first and
the increments on the long are whacked (which now that I think about it more
makes sense since a +1 of the bits as long for the double would not
necessarly represent the +1 on the double).
So I am setting the increment to
I will give that a shot, seems that it will work fantastically, thanks!
I will keep trolling JIRA then for something I feel I can get my feet wet
with and contribute then.
On Mon, Jun 27, 2011 at 7:33 PM, Jason Fager wrote:
> Longs and Doubles are both 64-bit values and are pretty easily
> conv
Longs and Doubles are both 64-bit values and are pretty easily
convertible. Check out Double.doubleToLongBits and
Double.longBitsToDouble in the JDK; you can also read more about the
details of the conversion and get some pointers to some code in a post
I wrote last year:
http://jasonfager.com/770
So has anyone considered using the CounterColumn for summing?
I wanted to-do this over the weekend until I realized it was only a long :(
so using it for things like duration (as an example for me this would have
been great to keep track of aggregate durations of ad impressions) are not
possible (
Thanks!
On Mon, Jun 27, 2011 at 4:30 PM, Joseph Stein wrote:
> Thanks Jonathan, that worked great. I also had to build the source so I
> added both of these steps to the Wiki (hopefully that is ok was not sure
> the etiquette)
>
> On Mon, Jun 27, 2011 at 3:47 PM, Jonathan Ellis wrote:
>
>> inst
Thanks Jonathan, that worked great. I also had to build the source so I
added both of these steps to the Wiki (hopefully that is ok was not sure
the etiquette)
On Mon, Jun 27, 2011 at 3:47 PM, Jonathan Ellis wrote:
> install cql first. check out from
> https://svn.apache.org/repos/asf/cassandr
+1
On Fri, Jun 24, 2011 at 11:03 AM, Sylvain Lebresne wrote:
> Alright, third time's not always the charm, my mistake. Let's try again.
> I propose the following artifacts for release as 0.8.1:
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8.1@r1139326
> Artifacts:
+1
On Fri, Jun 24, 2011 at 11:03 AM, Sylvain Lebresne wrote:
> Alright, third time's not always the charm, my mistake. Let's try again.
> I propose the following artifacts for release as 0.8.1:
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8.1@r1139326
> Artifacts:
install cql first. check out from
https://svn.apache.org/repos/asf/cassandra/drivers; cd drivers/py;
python setup.py build; sudo python setup.py install
On Mon, Jun 27, 2011 at 2:40 PM, Joseph Stein wrote:
> So this is probably the first of a few noob questions and I am happy to
> update the Wik
So this is probably the first of a few noob questions and I am happy to
update the Wiki or try to help contribute fixes (if it is not something
stupid I am doing of course) as I learn the answers :)
So by following the http://wiki.apache.org/cassandra/HowToContribute
I am getting this error
Hi Joseph,
JIRA tickets are classified into trivial, minor, major and blocker. You can
start with trivial/minor without any assignee, I guess. But also take a look
at the other categories, because it may have anything you feel comfortable
with. ;) Nevertheless, Cassandra commiters may suggest some
Hey Jake, thanks!
Is there any label like "newbie" that are things folks can jump in on to
search for when trying to first contribute getting into the swing of things?
Or should i just look at anything not assigned?
Slyvain: just read your update to CASSANDRA-2495 will follow-up in the
ticket wi
On Mon, Jun 27, 2011 at 12:45 PM, Peter Schuller
wrote:
>> [1]: http://goo.gl/qbvPB (CHANGES.txt)
>> [2]: http://goo.gl/7uQXl (NEWS.txt)
>
> CASSANDRA-2280 (https://issues.apache.org/jira/browse/CASSANDRA-2280)
> is not listed (and I don't see the change in the branch), which I
> suspect may be on
> [1]: http://goo.gl/qbvPB (CHANGES.txt)
> [2]: http://goo.gl/7uQXl (NEWS.txt)
CASSANDRA-2280 (https://issues.apache.org/jira/browse/CASSANDRA-2280)
is not listed (and I don't see the change in the branch), which I
suspect may be on purpose? However, if so the JIRA ticket should
probably be update
16 matches
Mail list logo
