I've studied DataStax .Net driver and it doesn't satisfy all of my needs. I wish it met 50% of my needs, but it doesn't. In theory, Nectar could use the DataStax .Net driver for native protocol, but I'd have to do a lot more work to make it fit with Hector's API. Some use cases can stick with CQL for 100%, but not the kinds of use cases I have.
The modeler we built for Cassandra takes advantage of types, generics, Solr and tries to make it more friendly. We provide a JPA like interface for running queries and behind the scene the framework executes the queries against solr and cassandra. I know with DSE you can do a similar thing, but the developer has to build multiple queries themselves and tell cassandra to query solr. We take a model driven approach, so our schema modeler knows how to take advantage of the framework to run queries with "like" clauses. To the developer it's 1 query, not n queries. hopefully DataStax will accept my talk for september and we can show the stuff we built. On Mon, Jun 2, 2014 at 9:21 AM, Colin Clark <co...@clark.ws> wrote: > Peter, > > There's very little reason today to write your own Cassandra driver for > .net, java, or python. Those firms that do are now starting to wrap those > drivers with any specific functionality they might require, like Netflix, > for example. Have you looked at DataStax's .NET driver? > > -- > Colin > +1 320 221 9531 > > > > On Mon, Jun 2, 2014 at 7:38 AM, Peter Lin <wool...@gmail.com> wrote: > >> >> thanks for the correction. Maybe it's just me, but I wish the >> implementation were also in apache's repo. It's not a big thing, but having >> multiple github forks to keep track of is a bit annoying. I'd rather spend >> time coding instead of screwing with git on windows. >> >> >> On Mon, Jun 2, 2014 at 8:29 AM, Benedict Elliott Smith < >> belliottsm...@datastax.com> wrote: >> >>> The native protocol specification has always been in the Apache >>> Cassandra repository. The implementations are not. >>> >>> >>> On 2 June 2014 13:25, Peter Lin <wool...@gmail.com> wrote: >>> >>>> >>>> There's nothing preventing support for native protocol going forward. >>>> It was easier to go with thrift and I happen to like thirft. Native >>>> protocol is still relatively new, so I'm taking a wait and see approach.Is >>>> the native protocol specification and drivers still in DataStax's git? >>>> >>>> If it's going to be the "standard" protocol, then it really should be >>>> in apache's repo. That's my bias opinion. >>>> >>>> >>>> >>>> >>>> On Mon, Jun 2, 2014 at 8:16 AM, Colin Clark <co...@clark.ws> wrote: >>>> >>>>> Unless a cassandra driver is using the native protocol, it's going to >>>>> have a very short life going forward. >>>>> >>>>> -- >>>>> Colin >>>>> +1 320 221 9531 >>>>> >>>>> >>>>> >>>>> On Mon, Jun 2, 2014 at 7:10 AM, Peter Lin <wool...@gmail.com> wrote: >>>>> >>>>>> >>>>>> it is using thrift. I've updated the project page to state that info. >>>>>> >>>>>> >>>>>> On Mon, Jun 2, 2014 at 8:08 AM, Colin Clark <co...@clark.ws> wrote: >>>>>> >>>>>>> Is your version of Hector using native protocol or thrift? >>>>>>> >>>>>>> -- >>>>>>> Colin >>>>>>> +1 320 221 9531 >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, Jun 2, 2014 at 6:41 AM, Peter Lin <wool...@gmail.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> I'm happy to announce Concord has decided to open source our port >>>>>>>> of Hector to .Net. >>>>>>>> >>>>>>>> The project is hosted on google code >>>>>>>> https://code.google.com/p/nectar-client/ >>>>>>>> >>>>>>>> I'm still adding code documentation and wiki pages. It has been >>>>>>>> tested against 1.1.x, 2.0.x >>>>>>>> >>>>>>>> thanks >>>>>>>> >>>>>>>> peter >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
