Re: splitting CQL parser & spec into separate repo

This is a great idea +1 (non-binding) On 22 March 2017 at 07:04, Edward Capriolo wrote: > On Tue, Mar 21, 2017 at 3:24 PM, Mark Dewey wrote: > > > I can immediately think of a project I would use that in. +1 > > > > On Tue, Mar 21, 2017 at 12:18 PM

Re: splitting CQL parser & spec into separate repo

I can immediately think of a project I would use that in. +1 On Tue, Mar 21, 2017 at 12:18 PM Jonathan Haddad wrote: > I created CASSANDRA-13284 a few days ago with the intent of starting a > discussion around the topic of breaking the CQL parser out into a separate >

splitting CQL parser & spec into separate repo

I created CASSANDRA-13284 a few days ago with the intent of starting a discussion around the topic of breaking the CQL parser out into a separate project. I see a few benefits to doing it and was wondering what the folks here thought as well. First off, the Java CQL parser would obviously

[GitHub] cassandra pull request #:

Github user Baddaboo commented on the pull request: https://github.com/apache/cassandra/commit/5b8b1ce26cd073a44ddf7c7a6750da409a343eba#commitcomment-21412404 Maybe @belliottsmith was just writing this printout in [Italian](https://translate.google.com/#eo/en/datata), referring to a