Sorry, I missed your reply. Yes it is what you described.
Le jeu. 10 mars 2022 à 11:25, Claude Warren
a écrit :
> I found it in https://github.com/antlr/grammars-v4.git and I suspected it
> was wrong. I assume it should be that the tuple can contain 1 or more
> elements and the elements may be
I found it in https://github.com/antlr/grammars-v4.git and I suspected it
was wrong. I assume it should be that the tuple can contain 1 or more
elements and the elements may be of type tuple, constant, map, list or
set.
Does that make sense? I think that is what I saw in the code base.
On Thu,
Hi Claude,
I am not aware of the CqlParser.g4 file in our code base. Where did you
find that file?
At first glance effectively something looks wrong in the syntax. The
construct ((4 ,5 ), 6, (7, 8)) should be legal in CQL.
Le jeu. 10 mars 2022 à 06:50, Claude Warren
a écrit :
> I have been loo
I think getting the CQL parser submitted upstream to pygments is a great
idea.
Anyone have experience with pygments?
On Mon, Jun 1, 2020 at 6:34 AM Mike Adamson wrote:
> The correct code location is:
>
> https://github.com/apache/cassandra/tree/trunk/doc/source/_util
>
> On Mon, 1 Jun 2020 at 1
The correct code location is:
https://github.com/apache/cassandra/tree/trunk/doc/source/_util
On Mon, 1 Jun 2020 at 14:21, Lorina Poland wrote:
> Some time back, someone (Sylvain?) wrote some code to use CQL with
> pygments. Can I interest anyone in picking up that work, perhaps doing some
> up
On Wed, Aug 31, 2016 at 11:56 PM, Ben Frank wrote:
> Interestingly it's still dog slow while (presumably) doing the
> deserialization in python, so although the trace reports good results it's
> still taking ~3 seconds to load data into python wall clock time.
>
If you're not doing this already,
Thanks Tyler!
I wasn't aware of frozen collections - the tracing shows pretty similar
timing characteristics between frozen collection and binary schemas.
Interestingly it's still dog slow while (presumably) doing the
deserialization in python, so although the trace reports good results it's
st
The map version of the schema needs to deserialize, serialize, and then
deserialize about 85 times more cells, if your average map has 85
elements. I would assume that's where most of the performance slowdown is
coming from. If you can take the time to run that through a profiler, that
would be u
No, I didn't test, I was just reading the code, but I hadn't checked for
all occurrences of K_COUNT, so I hadn't noticed that it also occurs in the
allowedFunctionName grammar production rule. And I found the code that
dynamically creates a count function for each type here:
https://github.com/apac
Hi Jack,
You are looking at the wrong place. count() is a native
function. There nothing specific for it in the parser syntax.
Benjamin
On Mon, Apr 18, 2016 at 3:50 PM, Jack Krupansky
wrote:
> The CQL spec for COUNT says:
>
> "It also can be used to count the non null value of a given column.
May be I misunderstood you.
Do you mean that you tested it and that it is not working on the version
you used?
On Mon, Apr 18, 2016 at 3:50 PM, Jack Krupansky
wrote:
> The CQL spec for COUNT says:
>
> "It also can be used to count the non null value of a given column.
> Example:
>
> SELECT COUNT
The storage engine design doesn't support this; we just write the new data
(or tombstone for delete). This is much more performant than having to
check first if the row exists.
On Tue, Aug 26, 2014 at 5:51 PM, Sékine Coulibaly
wrote:
> SQL allows for sqlca.sqlerrd[0] to yield valuable informat
We actually have some jython tests for a few test suites we wanted to use
the java driver with: https://github.com/riptano/cassandra-dtest-jython
On Thu, May 22, 2014 at 2:36 PM, Jake Luciani wrote:
> Jython! :D
>
>
> On Thu, May 22, 2014 at 12:09 PM, Benedict Elliott Smith <
> belliottsm...@da
Jython! :D
On Thu, May 22, 2014 at 12:09 PM, Benedict Elliott Smith <
belliottsm...@datastax.com> wrote:
> I would for defining the cql tests in a way that permits them being run as
> both dtests and unit tests. But since we're on python for dtests that could
> be troublesome.
>
>
> On 22 May 20
I would for defining the cql tests in a way that permits them being run as
both dtests and unit tests. But since we're on python for dtests that could
be troublesome.
On 22 May 2014 17:03, Jeremiah D Jordan wrote:
> The only thing I worry about here is that the unit tests don't come into
> the
The only thing I worry about here is that the unit tests don't come into the
system the same way user queries will. So we still need the system level
dtests. So I don't think all CQL tests should be unit tests, but I am all for
there being unit level CQL tests.
On May 22, 2014, at 10:58 AM, S
On Wed, May 21, 2014 at 10:46 PM, Jonathan Ellis wrote:
> I do think that CQL tests in general make more sense as unit tests,
> but I'm not so anal that I'm going to insist on rewriting existing
> ones. But in theory, if I had an infinite army of interns, sure. I'd
> have one of them do that. :)
On Wed, May 21, 2014 at 4:06 AM, Sylvain Lebresne wrote:
> Having tests that are
> intrinsically
> the same kind of tests in two places bugs me a bit more however.
I do think that CQL tests in general make more sense as unit tests,
but I'm not so anal that I'm going to insist on rewriting existi
The standard reasoning for unit tests is specificity of errors. Well
written tests suites tell you where you screwed up exactly just by the
success and failure pattern, often cutting down the need for a debugger.
System tests standard rational is validating these units are wired up
correctly. Henc
Just to be clear, I'm not strongly opposed to having CQL tests in the unit
tests suite per-se (I happen to find dtests easier to work with, probably
because I don't use debuggers, but I'm good with saying that this just mean
I'm crazy and shouldn't be taken into account). Having tests that are
intr
On Tue, May 20, 2014 at 6:42 PM, Jonathan Ellis wrote:
> So my preferred approach is, unit test when possible without writing a lot
> of scaffolding and mock superstructure. Mocking is your code telling you to
> write a system test.
This.
+1 unit tests
On 21 May 2014 02:36, "Jake Luciani" wrote:
> I think having cql unit tests is certainly a good idea. It doesn't replace
> dtests but makes it easier to have better coverage locally.
>
>
> On Tue, May 20, 2014 at 7:10 PM, Tyler Hobbs wrote:
>
> > Sylvain and I have been having a d
I think having cql unit tests is certainly a good idea. It doesn't replace
dtests but makes it easier to have better coverage locally.
On Tue, May 20, 2014 at 7:10 PM, Tyler Hobbs wrote:
> Sylvain and I have been having a discussion about testing CQL in unit tests
> vs dtests. I'd like to hea
Given a unit and a system test that cover the same code, the unit test is
10x more useful when something breaks. It's difficult to run dtests locally
at all, let alone attach your debugger to the right instance at the right
time to troubleshoot deeper.
So my preferred approach is, unit test when p
Added!
On Sun, Mar 16, 2014 at 2:26 AM, Saurabh Rawat
wrote:
> Hi,
>
> I have written a CQL client for Scala. I was wondering if this could be
> added to the client options page. I tried to add it but the page is not
> editable.
>
> Link to client: https://github.com/eklavya/Scqla
>
> Regards,
>
Eric
do you have any numbers for this?
-Jake
On Tue, Aug 6, 2013 at 10:34 AM, Eric Evans wrote:
> [ Nulik Nol ]
> > I need a client in C (not C++) to work with Cassandra, so since there
> > is no one yet I would do my own. So far I have checked, I can do it
> > through Thrift RPC port, or thro
The problem was that utf8 representation of the string was confusing emacs
buffer for some reason by nicely removing the metadata part at the correct
place. Emacs is really nice, isn't it! It became obvious once I tried to
look at the binary. Thanks for providing the clue.
Yes, I am writing a O
Can you also describe the query you're running and paste the actual entire
binary response (from the header to the end)?
By the way, are you writing a new client?
On Wed, Aug 14, 2013 at 6:37 PM, Mosfeq Rashid wrote:
>
> Thanks for the quick response.
>
> This is what I am getting:
>
> ...
>
>
Thanks for the quick response.
This is what I am getting:
...
As you see, there is no metadata before the row-count.
All the others messages I have tried like create, error, etc. are sending
response as expected in the spec.
By I am running Ubuntu 13.04 and the binary distribution.
--
Mosfeq
Can you provide more details on exactly what's being returned? As far as I
know, ResultMessages of type "ROWS" should always start with metadata, and
I haven't seen a case where it's missing in 1.2.
On Wed, Aug 14, 2013 at 6:05 PM, Mosfeq Rashid wrote:
>
> The response to the Select query is s
[ Nulik Nol ]
> I need a client in C (not C++) to work with Cassandra, so since there
> is no one yet I would do my own. So far I have checked, I can do it
> through Thrift RPC port, or through CQL port. As I understand, CQL
> doesn't support direct "mutate" or "get_range_slices" calls like
> Thrif
Hi Aswani Kumar,
Please let me know, any specific reasons that you're recommending thrift?
Thanks
Murali.
On Tue, Aug 6, 2013 at 11:16 AM, Aswani Kumar Vonteddu <
as.wins.c...@hotmail.com> wrote:
> I'd recommend Thrift.
>
> > Date: Mon, 5 Aug 2013 14:08:52 -0500
> > Subject: CQL or Thrift ?
> >
Why? Please give me 3 reasons why this is good advice to the OP.
The frame based binary protocol will be 100% easier to implement in C than
the never-been-out-of-alpha libc Thrift implementation. I¹ve worked with
that code for a while, it¹s *not* pretty.
I can¹t think of one reason, other than ³I
I'd recommend Thrift.
> Date: Mon, 5 Aug 2013 14:08:52 -0500
> Subject: CQL or Thrift ?
> From: nulik...@gmail.com
> To: dev@cassandra.apache.org
>
> Hi,
> I need a client in C (not C++) to work with Cassandra, so since there
> is no one yet I would do my own. So far I have checked, I can do it
You want to use CQL. Push notifications of cluster changes alone are worth it.
On Mon, Aug 5, 2013 at 2:08 PM, Nulik Nol wrote:
> Hi,
> I need a client in C (not C++) to work with Cassandra, so since there
> is no one yet I would do my own. So far I have checked, I can do it
> through Thrift RPC
+1. Thrift should be all about raw data cells.
-Vivek
From: Jonathan Ellis
To: dev@cassandra.apache.org
Sent: Thursday, July 18, 2013 2:48 AM
Subject: Re: CQL vs Thrift
On Wed, Jul 17, 2013 at 4:03 PM, Tyler Hobbs wrote:
> I'll leave it to somebody
If you understand how cql collections are written you can decode them and
work with them from thrift. It's quite a chore and i would not suggest
trying yo do it however.
(I suspect tyler tried it and jonathan broke his hand jk)
There is a perl cassandra driver that did something like this.
On We
On Wed, Jul 17, 2013 at 4:03 PM, Tyler Hobbs wrote:
> I'll leave it to somebody else to comment on adding collections, etc to
> Thrift.
Doesn't make sense, since Thrift is all about the raw data cells, and
collections are an abstraction layer on top of that.
--
Jonathan Ellis
Project Chair, Apa
On Wed, Jul 17, 2013 at 3:18 PM, Vladimir Prudnikov
wrote:
> I read somewhere that it will be for backward compatibility, but does it
> mean that new features
> will not be added to the Thrift interface
Yes, the thrift interface will remain stable and not be changing.
-Brandon
Hi, I'm the maintainer of pycassa and the DataStax python-driver. I just
broke some fingers, so I will be brief.
Regarding performance, the python driver is brand new and still has some
issues to be worked out around performance (C extension, locking and
signaling). How you use it has a big impa
Better question for the users list, but everything about your cluster is
available in the system column family and accessible with CQL.
On 7/10/13, 11:46 PM, "Murali" wrote:
>Hi experts,
>
>Can we use CQL 3.0 to get the partition / cluster information from
>cassandra server?
>
>
>Thanks,
>Murali
I tried Googling the question but it seems there is no relevant result for
CQL. You may try raw API or some higher-level API like Hector/Astyanax:
http://stackoverflow.com/questions/4538123/fetching-records-withing-given-range-of-timestamp-from-cassandra
http://gettingstartedwithcassandra.blogspot.
Please can any body help me to solve the above problem. I stuck with that
problem in my project. help me
Thanks for the explanation(s).
I'm going to give a "Create your first java app for Cassandra" webinar on
Wednesday, and I was trying to embrace schema creation in CQL, but didn't
want to have to use CompositeType's right off the bat. (I'll go with
compact storage)
I think I can explain away the
There is some more details in
http://www.datastax.com/dev/blog/thrift-to-cql3 but to answer your
questions:
> Question 1:
> What is the empty column/value?
The technical reasons are here:
https://issues.apache.org/jira/browse/CASSANDRA-4361. But basically, it's a
CQL3 implementation detail.
Qu
I had complains that my preceding mail was unreadable (thanks gmailfor
fucking my formatting up), so I've posted the same thing with nice
formatting on the JIRA ticket.
--
Sylvain
On Tue, Jan 3, 2012 at 7:08 PM, Sylvain Lebresne wrote:
> Ok, I think I'm warming up to what we're getting at. I wou
Ok, I think I'm warming up to what we're getting at. I would change
thesyntax of the VALUE() thing however. Instead of:CREATE TABLE
timeline ( userid int, posted_at uuid, body string, PRIMARY
KEY(user_id, posted_at), VALUE(body))I would prefer:CREATE COMPACT
TABLE timeline ( userid int,
On Mon, Jan 2, 2012 at 12:55 PM, Jonathan Ellis wrote:
> On Mon, Jan 2, 2012 at 10:53 AM, Eric Evans wrote:
>> In SQL, PRIMARY KEY is a modifier to a column spec, and here PRIMARY
>> KEY(user_id, posted_at, posted_by) reads like a PRIMARY modifier
>> applied to a KEY() function. It's also a litt
On Mon, Jan 2, 2012 at 10:53 AM, Eric Evans wrote:
> In SQL, PRIMARY KEY is a modifier to a column spec, and here PRIMARY
> KEY(user_id, posted_at, posted_by) reads like a PRIMARY modifier
> applied to a KEY() function. It's also a little strange the way it
> appears in the grouping of column spe
Maybe the ship on this has sailed, but I am a bit miffed on "create
table". CQL is going out of its way to make things so easy for people. But
if someone does not understand the concept of a column family making it
easy for them to design something that is an anti-pattern is odd to me.
As an admi
On Sat, Dec 31, 2011 at 1:12 PM, Jonathan Ellis wrote:
> On Fri, Dec 30, 2011 at 12:30 PM, Eric Evans wrote:
>>> CREATE TABLE timeline (
>>> user_id int,
>>> posted_at uuid,
>>> body string,
>>> posted_by string,
>>> PRIMARY KEY(user_id, posted_at, posted_by),
>>> VALUE(body)
>>
On Fri, Dec 30, 2011 at 12:30 PM, Eric Evans wrote:
>> CREATE TABLE timeline (
>> user_id int,
>> posted_at uuid,
>> body string,
>> posted_by string,
>> PRIMARY KEY(user_id, posted_at, posted_by),
>> VALUE(body)
>> );
>
> I think the value declaration also helps in that it's one
On Fri, Dec 30, 2011 at 11:12 AM, Rick Shaw wrote:
> +1 on Gamma
> +1 on haveing capability to specify a value.
>
> My only reservation is the choice of the keword "TABLE", which is going to
> be a source of continued confusion.
TABLE is an alias for COLUMNFAMILY (pretty much always has been); I
On Fri, Dec 30, 2011 at 10:58 AM, Jonathan Ellis wrote:
> I think we're closing in on something workable.
I agree.
> Dropping TRANSPOSED from Gamma as redundant with respect to the
> composite PRIMARY KEY definition.
+1
> Should we support column values in non-sparse rows by adding a
> VALUE(c
+1 on Gamma
+1 on haveing capability to specify a value.
My only reservation is the choice of the keword "TABLE", which is going to
be a source of continued confusion.
On Fri, Dec 30, 2011 at 11:58 AM, Jonathan Ellis wrote:
> I think we're closing in on something workable.
>
> Dropping TRANSPO
I think we're closing in on something workable.
Dropping TRANSPOSED from Gamma as redundant with respect to the
composite PRIMARY KEY definition.
Should we support column values in non-sparse rows by adding a
VALUE(column_name) section?
CREATE TABLE timeline (
user_id int,
posted_at uuid
https://issues.apache.org/jira/browse/CASSANDRA-3685
On Thu, Dec 29, 2011 at 6:34 PM, Eric Evans wrote:
> On Thu, Dec 29, 2011 at 3:44 PM, Jonathan Ellis wrote:
>> That's to allow defining column names that are not text/utf8. So you
>> could have column name "92d21d0a-d6cb-437c-9d3f-b67aa733a19
On Thu, Dec 29, 2011 at 3:44 PM, Jonathan Ellis wrote:
> That's to allow defining column names that are not text/utf8. So you
> could have column name "92d21d0a-d6cb-437c-9d3f-b67aa733a19f" be an
> actual 128-bit uuid binary value internally, not its string
> representation. Put another way, thi
That's to allow defining column names that are not text/utf8. So you
could have column name "92d21d0a-d6cb-437c-9d3f-b67aa733a19f" be an
actual 128-bit uuid binary value internally, not its string
representation. Put another way, this would affect the CqlMetadata
name_types map.
However, we alre
On Wed, Dec 28, 2011 at 1:05 PM, Jonathan Ellis wrote:
> Gamma proposal update:
>
> The more I think about it the less happy I am with omitting support
> for sparse columns. Remember that dense composites may only be
> inserted and deleted, not updated, since they are just a tuple of
> values wit
On Thu, Dec 29, 2011 at 12:04 PM, Jonathan Ellis wrote:
> I've updated the wiki page at
> http://wiki.apache.org/cassandra/Cassandra2474 with a more in-depth
> Background section that hopefully clears up where I'm going with this
> sparse/dense business.
>
> Eric mentioned on IRC that he's uneasy
I've updated the wiki page at
http://wiki.apache.org/cassandra/Cassandra2474 with a more in-depth
Background section that hopefully clears up where I'm going with this
sparse/dense business.
Eric mentioned on IRC that he's uneasy about the PRIMARY KEY syntax
implicitly using the first element of P
Gamma proposal update:
The more I think about it the less happy I am with omitting support
for sparse columns. Remember that dense composites may only be
inserted and deleted, not updated, since they are just a tuple of
values with "column names" determined by schema and/or convention.
I think w
On Sat, Dec 24, 2011 at 9:22 AM, Jonathan Ellis wrote:
> Hmm, I thought I sent this but it was sitting in my Drafts box.
>
> Anyway, I've updated http://wiki.apache.org/cassandra/Cassandra2474 to
> flesh out the earlier proposals and editorialize a little in
> "Discussion Summary" sections.
>
> I'
Hmm, I thought I sent this but it was sitting in my Drafts box.
Anyway, I've updated http://wiki.apache.org/cassandra/Cassandra2474 to
flesh out the earlier proposals and editorialize a little in
"Discussion Summary" sections.
I'm skeptical that splitting dicussion across Jira and the ML is a big
Hi,
I +1 Gamma.
Best Regards
--
Pavel Yaskevich
On Sun, Sep 4, 2011 at 10:12 AM, Eric Evans wrote:
>> I'm rather fond of how user-friendly the Python suite is (taking care
>> of server setup/teardown transparently) but realistically, now that we
>> have robust truncate, it's probably fine to require an existing server
>> and just use that.
>
>
On Sat, Sep 3, 2011 at 10:21 PM, Jonathan Ellis wrote:
> On Sat, Sep 3, 2011 at 9:36 PM, Rick Shaw wrote:
>> For what it is worth, my preference would be to have unit tests that would
>> form a regression testing package in the tree with the client sources.
>
> Ditto.
>
>> I think that makes me
On Sat, Sep 3, 2011 at 9:36 PM, Rick Shaw wrote:
> For what it is worth, my preference would be to have unit tests that would
> form a regression testing package in the tree with the client sources.
Ditto.
> I think that makes me favor option #3.
I'm rather fond of how user-friendly the Python
For what it is worth, my preference would be to have unit tests that would form
a regression testing package in the tree with the client sources. Ideally the
build package (whether dedicated or mixed in with the server) would have
specific tasks to build, test and install/deploy devoted to the i
On Fri, Sep 2, 2011 at 3:49 PM, Jonathan Ellis wrote:
> On Thu, Sep 1, 2011 at 9:08 AM, Eric Evans wrote:
>> I posed a similar question about the JDBC driver in CASSANDRA-2936.
>>
>> Should these tests be considered functional tests of Cassandra, and
>> left be left where they are? I know that w
On Thu, Sep 1, 2011 at 9:08 AM, Eric Evans wrote:
> On Wed, Aug 31, 2011 at 10:58 PM, Jonathan Ellis wrote:
>> On Wed, Aug 31, 2011 at 4:24 PM, Eric Evans wrote:
>>> CASSANDRA-2936 is in progress (patches attached), but is there any
>>> reason not to get started with the Python driver now?
>>
>>
On Thu, Sep 1, 2011 at 9:08 AM, Eric Evans wrote:
> I posed a similar question about the JDBC driver in CASSANDRA-2936.
>
> Should these tests be considered functional tests of Cassandra, and
> left be left where they are? I know that was my intention WRT
> test_cql.py (the driver itself has a fe
On Wed, Aug 31, 2011 at 10:58 PM, Jonathan Ellis wrote:
> On Wed, Aug 31, 2011 at 4:24 PM, Eric Evans wrote:
>> CASSANDRA-2936 is in progress (patches attached), but is there any
>> reason not to get started with the Python driver now?
>
> Heads up that test/system/test_cql.py depends on the Pyth
On Wed, Aug 31, 2011 at 4:24 PM, Eric Evans wrote:
> CASSANDRA-2936 is in progress (patches attached), but is there any
> reason not to get started with the Python driver now?
Heads up that test/system/test_cql.py depends on the Python driver.
It should probably be moved to the Python driver's te
On Tue, Aug 30, 2011 at 8:26 AM, Jonathan Ellis wrote:
> On Mon, Aug 29, 2011 at 10:16 PM, Eric Evans wrote:
>> No one else has sounded off on this, does that mean it's safe to
>> assume there is consensus on this?
>
> Looks like it. The opinions on irc were positive, too.
>
>> If so, is it Apac
I agree that apache extras makes better sense sense it's Branded (tm) and
has git.
On Tue, Aug 30, 2011 at 10:04 AM, Eric Evans wrote:
> On Tue, Aug 30, 2011 at 5:34 AM, Robert Jackson
> wrote:
> > On Aug 29, 2011, at 11:17 PM, Eric Evans wrote:
> >> If so, is it Apache Extras or Github (eithe
On Tue, Aug 30, 2011 at 5:34 AM, Robert Jackson
wrote:
> On Aug 29, 2011, at 11:17 PM, Eric Evans wrote:
>> If so, is it Apache Extras or Github (either would be fine by me).
>>
> Either would be good, but I have a preference for GitHub (easier workflow).
Generally I prefer Github too, but the b
On Mon, Aug 29, 2011 at 10:16 PM, Eric Evans wrote:
> No one else has sounded off on this, does that mean it's safe to
> assume there is consensus on this?
Looks like it. The opinions on irc were positive, too.
> If so, is it Apache Extras or Github (either would be fine by me).
No strong feel
On Aug 29, 2011, at 11:17 PM, Eric Evans wrote:
>>
>>>
>>
> No one else has sounded off on this, does that mean it's safe to
> assume there is consensus on this?
>
I definitely think this is the right move.
> If so, is it Apache Extras or Github (either would be fine by me).
>
Either woul
On Thu, Aug 25, 2011 at 1:49 PM, Eric Evans wrote:
> On Wed, Aug 24, 2011 at 11:57 PM, Jonathan Ellis wrote:
>> The git mirror is also a symptom of a deeper problem. Managing the
>> drivers from the same Jira system as core is awkward too. Nor does
>> three-day release voting or patch-oriented
Eric did some preliminary testing that showed competitive speed w/
traditional Thrift API but the next step in accuracy would be to add
CQL support to stress.java. Aaron has a work in progress on
https://issues.apache.org/jira/browse/CASSANDRA-2268 -- I'm sure he
wouldn't mind if you wanted to jum
On Wed, Aug 24, 2011 at 11:57 PM, Jonathan Ellis wrote:
> The JDBC problems can be subdivided into two categories: too-tight
> coupling that having it in-tree masks (but is really a problem either
> way), and java build systems being a PITA. By the second part I mean,
> yes, we had JDBC building
So to summarize the problems with the original move,
1) the git problem
2) the JDBC build problems
3) the cqlsh problem
In reverse order:
The cqlsh problem is not the same as the JDBC problem. The cqlsh
problem is simply, "if we have a cql shell that we ship, it would be
convenient to have th
On Wed, Aug 24, 2011 at 10:09 PM, Gary Dusbabek wrote:
> On Wed, Aug 24, 2011 at 17:22, Eric Evans wrote:
>> There are some workarounds that have been proposed for moving the
>> drivers back under Cassandra's source tree while creating independent
>> releases from there. For example, keeping the
On Wed, Aug 24, 2011 at 17:22, Eric Evans wrote:
> There's been discussion happening in #2761
> (https://issues.apache.org/jira/browse/CASSANDRA-2761) on and off now
> for more than 3 months, and I think it could benefit from some wider
> exposure.
>
> The issue was created in the wake of the driv
On Wed, 2011-01-12 at 05:21 +0100, Tristan Tarrant wrote:
> what we need now is a jdbc driver...
https://issues.apache.org/jira/browse/CASSANDRA-1710
> On Jan 12, 2011 3:00 AM, "Courtney Robinson" wrote:
> > ?On Tue, Jan 11, 2011 at 7:27 PM, Courtney Robinson
> > wrote:
> >> ?Having been pointe
what we need now is a jdbc driver...
On Jan 12, 2011 3:00 AM, "Courtney Robinson" wrote:
> ?On Tue, Jan 11, 2011 at 7:27 PM, Courtney Robinson
> wrote:
>> ?Having been pointed to
>> https://issues.apache.org/jira/browse/CASSANDRA-1704
>> I wanted to know what the state of that was.
>> Eric Evans
?On Tue, Jan 11, 2011 at 7:27 PM, Courtney Robinson
wrote:
?Having been pointed to
https://issues.apache.org/jira/browse/CASSANDRA-1704
I wanted to know what the state of that was.
Eric Evans said changes had been pushed to SVN, can I check out the latest
head and play with it?
Yes.
Checki
On Tue, Jan 11, 2011 at 7:27 PM, Courtney Robinson wrote:
> ?Having been pointed to https://issues.apache.org/jira/browse/CASSANDRA-1704
> I wanted to know what the state of that was.
> Eric Evans said changes had been pushed to SVN, can I check out the latest
> head and play with it?
Yes.
> Loo
90 matches
Mail list logo
