Hi Jonathan - Does cqlengine have support for python 2.6 ?
On Tue, Nov 26, 2013 at 4:17 PM, Jonathan Haddad <j...@jonhaddad.com> wrote: > cqlengine supports batch queries, see the docs here: > http://cqlengine.readthedocs.org/en/latest/topics/queryset.html#batch-queries > > > On Tue, Nov 26, 2013 at 11:53 AM, Kumar Ranjan <winnerd...@gmail.com>wrote: > >> Jon - Any comment on batching? >> — >> Sent from Mailbox <https://www.dropbox.com/mailbox> for iPhone >> >> >> On Tue, Nov 26, 2013 at 2:52 PM, Laing, Michael < >> michael.la...@nytimes.com> wrote: >> >>> That's not a problem we have faced yet. >>> >>> >>> On Tue, Nov 26, 2013 at 2:46 PM, Kumar Ranjan <winnerd...@gmail.com>wrote: >>> >>>> How do you insert huge amount of data? >>>> — >>>> Sent from Mailbox <https://www.dropbox.com/mailbox> for iPhone >>>> >>>> >>>> On Tue, Nov 26, 2013 at 2:31 PM, Laing, Michael < >>>> michael.la...@nytimes.com> wrote: >>>> >>>>> I think thread pooling is always in operation - and we haven't seen >>>>> any problems in that regard going to the 6 local nodes each client >>>>> connects >>>>> to. We haven't tried batching yet. >>>>> >>>>> >>>>> On Tue, Nov 26, 2013 at 2:05 PM, Kumar Ranjan <winnerd...@gmail.com>wrote: >>>>> >>>>>> Michael - thanks. Have you tried batching and thread pooling in >>>>>> python-driver? For now, i would avoid object mapper cqlengine, just >>>>>> because >>>>>> of my deadlines. >>>>>> — >>>>>> Sent from Mailbox <https://www.dropbox.com/mailbox> for iPhone >>>>>> >>>>>> >>>>>> On Tue, Nov 26, 2013 at 1:52 PM, Laing, Michael < >>>>>> michael.la...@nytimes.com> wrote: >>>>>> >>>>>>> We use the python-driver and have contributed some to its >>>>>>> development. >>>>>>> >>>>>>> I have been careful to not push too fast on features until we need >>>>>>> them. For example, we have just started using prepared statements - >>>>>>> working >>>>>>> well BTW. >>>>>>> >>>>>>> Next we will employ futures and start to exploit the async nature of >>>>>>> new interface to C*. >>>>>>> >>>>>>> We are very familiar with libev in both C and python, and are happy >>>>>>> to dig into the code to add features and fix bugs as needed, so the >>>>>>> rewards >>>>>>> of bypassing the old and focusing on the new seem worth the risks to us. >>>>>>> >>>>>>> ml >>>>>>> >>>>>>> >>>>>>> On Tue, Nov 26, 2013 at 1:16 PM, Jonathan Haddad >>>>>>> <j...@jonhaddad.com>wrote: >>>>>>> >>>>>>>> So, for cqlengine (https://github.com/cqlengine/cqlengine), we're >>>>>>>> currently using the thrift api to execute CQL until the native driver >>>>>>>> is >>>>>>>> out of beta. I'm a little biased in recommending it, since I'm one of >>>>>>>> the >>>>>>>> primary authors. If you've got cqlengine specific questions, head to >>>>>>>> the >>>>>>>> mailing list: >>>>>>>> https://groups.google.com/forum/#!forum/cqlengine-users >>>>>>>> >>>>>>>> If you want to roll your own solution, it might make sense to take >>>>>>>> an approach like we did and throw a layer on top of thrift so you don't >>>>>>>> have to do a massive rewrite of your entire app once you want to go >>>>>>>> native. >>>>>>>> >>>>>>>> Jon >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Nov 26, 2013 at 9:46 AM, Kumar Ranjan <winnerd...@gmail.com >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> I have worked with Pycassa before and wrote a wrapper to use >>>>>>>>> batch mutation & connection pooling etc. But >>>>>>>>> http://wiki.apache.org/cassandra/ClientOptions recommends now to >>>>>>>>> use CQL 3 based api because Thrift based api (Pycassa) will be >>>>>>>>> supported >>>>>>>>> for backward compatibility only. Apache site recommends to use Python >>>>>>>>> api >>>>>>>>> written by DataStax which is still in Beta (As per their >>>>>>>>> documentation). >>>>>>>>> See warnings from their python-driver/README.rst file >>>>>>>>> >>>>>>>>> *Warning* >>>>>>>>> >>>>>>>>> This driver is currently under heavy development, so the API and >>>>>>>>> layout of packages,modules, classes, and functions are subject to >>>>>>>>> change. >>>>>>>>> There may also be serious bugs, so usage in a production environment >>>>>>>>> is >>>>>>>>> *not* recommended at this time. >>>>>>>>> >>>>>>>>> DataStax site http://www.datastax.com/download/clientdrivers >>>>>>>>> recommends >>>>>>>>> using DB-API 2.0 plus legacy api's. Is there more? Has any one >>>>>>>>> compared >>>>>>>>> between CQL 3 based apis? Which stands out on top? Answers based on >>>>>>>>> facts >>>>>>>>> will help the community so please refrain from opinions. >>>>>>>>> >>>>>>>>> Please help ?? >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Jon Haddad >>>>>>>> http://www.rustyrazorblade.com >>>>>>>> skype: rustyrazorblade >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > > > -- > Jon Haddad > http://www.rustyrazorblade.com > skype: rustyrazorblade >
