Re: Request to review feature-freeze proposed tickets

2018-11-20 Thread kurt greaves
Thanks Vinay. While I suspect this will be subject to heated debate, I'm also for this. The time to review for this project is incredibly demotivating, and it stems from a lack of contributors that are interested in the general health of the project. I think this can be quite easily remedied by

Re: Request to review feature-freeze proposed tickets

2018-11-20 Thread Jonathan Haddad
If nobody has any objections to CASSANDRA-14303 (default RF) being merged in I can take care of it. It's a significant usability improvement, looks well tested and will prevent a number of headaches. I'll try to get to it tomorrow. Thanks for bringing these up, Vinay. Jon On Tue, Nov 20, 2018

RE: [External]Re: I/O threads busy error

2018-11-20 Thread Vishal1.Sharma
This issue is mainly being observed when the table whose data is being fetched contains a column which stores a very large text(12.5 KB). Could this be a possible reason? How can I solve the issue? Which settings do I have to change? -Original Message- From:

Re: [External]Re: I/O threads busy error

2018-11-20 Thread Jorge Bay Gondra
Hi Vishal, This might be an indication that you are sending several requests in parallel without waiting for a response and you need to introduce throttling in your application, as Dinesh mentioned. This issue is related to the usage of the DataStax C++ driver, you should consider starting a new

Re: I/O threads busy error

2018-11-20 Thread dinesh.jo...@yahoo.com.INVALID
You're probably hitting this -  https://github.com/datastax/cpp-driver/blob/2.0/src/session.cpp#L740 >From my reading it feels you may want to throttle your queries or play around >with the driver settings. Essentially it seems the number of queries you're >issuing is greater than what the

Re: Request to review feature-freeze proposed tickets

2018-11-20 Thread Ariel Weisberg
Hi, I would like to get as many of these as is feasible in. Before the feature freeze started 1 out of 17 JIRAs that were patch available were reviewed and committed. If you didn’t have access reviewers and committers, as the one out of the 17 did, it has been essentially impossible to get

RES: Implicit Casts for Arithmetic Operators

2018-11-20 Thread Versátil
PLEASE TAKE MY EMAIL FROM THIS SHIT !! -Mensagem original- De: Michael Burman [mailto:y...@iki.fi] Enviada em: terça-feira, 20 de novembro de 2018 13:51 Para: dev@cassandra.apache.org Assunto: Re: Implicit Casts for Arithmetic Operators Yep, that's a good approach. - Micke On

Re: Implicit Casts for Arithmetic Operators

2018-11-20 Thread Benedict Elliott Smith
FWIW, my meaning of arithmetic in this context extends to any features we have already released (such as aggregates, and perhaps other built-in functions) that operate on the same domain. We should be consistent, after all. Whether or not we need to revisit any existing functionality we can

Re: RES: Implicit Casts for Arithmetic Operators

2018-11-20 Thread Michael Shuler
On 11/20/18 9:53 AM, Versátil wrote: > > PLEASE TAKE MY EMAIL FROM THIS SHIT !! FYI, mailing list subscriptions (and unsubscriptions) are self-serve. In general, you subscribed yourself, so you are responsible to unsubscribe. The email address to do so is appended to every plain text message to

RES: RES: Implicit Casts for Arithmetic Operators

2018-11-20 Thread Versátil
I already requested as you said and it did not help. And I NEVER asked to enter into this discussion. Please request to withdraw my email -Mensagem original- De: Michael Shuler [mailto:mshu...@pbandjelly.org] Em nome de Michael Shuler Enviada em: terça-feira, 20 de novembro de

Re: RES: RES: Implicit Casts for Arithmetic Operators

2018-11-20 Thread Michael Shuler
On 11/20/18 10:15 AM, Versátil wrote: > > I already requested as you said and it did not help. And I NEVER asked to > enter into this discussion. Please request to withdraw my email | | | | | | | | | | \/\/\/\/\/\/\/\/\/\/ > >

Re: Implicit Casts for Arithmetic Operators

2018-11-20 Thread Michael Burman
Yep, that's a good approach. - Micke On Tue, Nov 20, 2018 at 5:12 PM Ariel Weisberg wrote: > Hi, > > +1 > > This is a public API so we will be much better off if we get it right the > first time. > > Ariel > > > On Nov 16, 2018, at 10:36 AM, Jonathan Haddad wrote: > > > > Sounds good to me.