Re: Proposal: freeze Thrift starting with 2.1.0

This brainstorming idea has already been -1 ed in jira. ROFL. On Wed, Mar 12, 2014 at 12:26 PM, Tupshin Harper wrote: > OK, so I'm greatly encouraged by the level of interest in this. I went > ahead and created https://issues.apache.org/jira/browse/CASSANDRA-6846, > and will be starting to look

Re: Proposal: freeze Thrift starting with 2.1.0

On Wed, Mar 12, 2014 at 9:10 AM, Edward Capriolo wrote: > Again, I am glad that the project has officially ended support for thrift > with this clear decree. For years the project kept saying "Thrift is not > going anywhere". It was obviously meant literally like the project would do > the absolut

Re: Proposal: freeze Thrift starting with 2.1.0

nformation transmitted in this email message is for the intended >> recipient only and may contain confidential and/or privileged material. If >> you received this email in error and are not the intended recipient, or the >> person responsible to deliver it to the intended recipi

Re: Proposal: freeze Thrift starting with 2.1.0

Awesome! Thanks Tupshin (and everyone else). I'll put some of my thoughts up there shortly. On Wed, Mar 12, 2014 at 11:26 AM, Tupshin Harper wrote: > OK, so I'm greatly encouraged by the level of interest in this. I went > ahead and created https://issues.apache.org/jira/browse/CASSANDRA-6846, >

Re: Proposal: freeze Thrift starting with 2.1.0

OK, so I'm greatly encouraged by the level of interest in this. I went ahead and created https://issues.apache.org/jira/browse/CASSANDRA-6846, and will be starting to look into what the interface would have to look like. Anybody feel free to continue the discussion here, email me privately, or comm

Re: Proposal: freeze Thrift starting with 2.1.0

@Tupshin LOL, there's always enough rope to hang oneself. I agree it's badly needed for folks that really do need more "messy" queries. I was just discussing a similar concept with a co-worker and going over the pros/cons of various approaches to realizing the goal. I'm still digging into Presto. I

Re: Proposal: freeze Thrift starting with 2.1.0

>> >> This information transmitted in this email message is for the intended >> recipient only and may contain confidential and/or privileged material. If >> you received this email in error and are not the intended recipient, or the >> person responsible to deliver i

Re: Proposal: freeze Thrift starting with 2.1.0

Peter, I didn't specifically call it out, but the interface I just proposed in my last email would be very much with the goal of "make writing complex queries less painful and more efficient." by providing a deep integration mechanism to host that code. It's very much a "enough rope to hang ourse

Re: Proposal: freeze Thrift starting with 2.1.0

eter Lin Reply-To: Date: Wednesday, March 12, 2014 at 8:44 AM To: "user@cassandra.apache.org" Subject: Re: Proposal: freeze Thrift starting with 2.1.0 yes, I was looking at intravert last nite. For the kinds of reports my customers ask us to do, joins and subqueries are important. Having tr

Re: Proposal: freeze Thrift starting with 2.1.0

@Nate I don't want to change the separation of components in cassandra. My ultimate goal is "make writing complex queries less painful and more efficient." How that becomes reality is anyone's guess. There's different ways to get there. I also like having a plugging transport layer, which is why I

Re: Proposal: freeze Thrift starting with 2.1.0

or other use of, or taking any action in reliance upon, this > information by persons or entities other than the intended recipient is > strictly prohibited. > > > > > From: Peter Lin > Reply-To: > Date: Wednesday, March 12, 2014 at 8:44 AM > To: "user@cassan

Re: Proposal: freeze Thrift starting with 2.1.0

gt;>> >>> 2700 Horizon Drive * King of Prussia, PA * 19406 >>> >>> M: 215.588.6024 * @boneill42 <http://www.twitter.com/boneill42> * >>> >>> healthmarketscience.com >>> >>> >>> This information transmitted in this em

Re: Proposal: freeze Thrift starting with 2.1.0

IME/O one of the best things about Cassandra was the separation of (and I'm over-simplifying a bit, but still): - The transport/API layer - The Datacenter layer - The Storage layer > I don't think we're well-served by the "construction kit" approach. > It's difficult enough to evaluate NoSQL wit

Re: Proposal: freeze Thrift starting with 2.1.0

* 19406 >>> >>> M: 215.588.6024 * @boneill42 <http://www.twitter.com/boneill42> * >>> >>> healthmarketscience.com >>> >>> >>> This information transmitted in this email message is for the intended >>> recipient only and may contain

Re: Proposal: freeze Thrift starting with 2.1.0

ail message is for the intended >> recipient only and may contain confidential and/or privileged material. If >> you received this email in error and are not the intended recipient, or the >> person responsible to deliver it to the intended recipient, please contact >> the sen

Re: Proposal: freeze Thrift starting with 2.1.0

sible to deliver it to the intended recipient, please contact > the sender at the email above and delete this email and any attachments and > destroy any copies thereof. Any review, retransmission, dissemination, > copying or other use of, or taking any action in reliance upon, this > in

Re: Proposal: freeze Thrift starting with 2.1.0

taking any action in reliance upon, this information by persons or entities other than the intended recipient is strictly prohibited.   From: Peter Lin Reply-To: Date: Wednesday, March 12, 2014 at 8:44 AM To: "user@cassandra.apache.org" Subject: Re: Proposal: freeze Thrift starting

Re: Proposal: freeze Thrift starting with 2.1.0

r other use of, or taking any action in reliance upon, this information by persons or entities other than the intended recipient is strictly prohibited. From: Peter Lin Reply-To: Date: Wednesday, March 12, 2014 at 8:44 AM To: "user@cassandra.apache.org" Subject: Re: Proposal: f

Re: Proposal: freeze Thrift starting with 2.1.0

yes, I was looking at intravert last nite. For the kinds of reports my customers ask us to do, joins and subqueries are important. Having tried to do a simple join in PIG, the level of pain is high. I'm a masochist, so I don't mind breaking a simple join into multiple MR tasks, though I do find m

Re: Proposal: freeze Thrift starting with 2.1.0

"I would love to see Cassandra get to the point where users can define complex queries with subqueries, like, group by and joins" --> Did you have a look at Intravert ? I think it does union & intersection on server side for you. Not sure about join though.. On Wed, Mar 12, 2014 at 12:44 PM, Pete

Re: Proposal: freeze Thrift starting with 2.1.0

Hi Ed, I agree Solr is deeply integrated into DSE. I've looked at Solandra in the past and studied the code. My understanding is DSE uses Cassandra for storage and the user has both API available. I do think it can be integrated further to make moderate to complex queries easier and probably fast

Re: Proposal: freeze Thrift starting with 2.1.0

Peter, Solr is deeply integrated into DSE. Seemingly this can not efficiently be done client side (CQL/Thrift whatever) but the Solandra approach was to embed Solr in Cassandra. I think that is actually the future client dev, allowing users to embedded custom server side logic into there own API.

Re: Proposal: freeze Thrift starting with 2.1.0

If were to run a fork it would do one thing: "Cassandra is a highly scalable, eventually consistent, distributed, structured key-value store. Cassandra brings together the distributed systems technologies from Dynamoand

Re: Proposal: freeze Thrift starting with 2.1.0

I'll give you a concrete example. One of the things we often need to do is do a keyword search on unstructured text. What we did in our tooling is we combined solr with cassandra, but we put an Object API infront of it. The API is inspired by JPA, but designed specifically to fit our needs. the u

Re: Proposal: freeze Thrift starting with 2.1.0

sorry for the confusion. I'm not trying to add relational features like constraints, etc. what I want to do is make writing reports easier than the ugly mess that is today. Anyone that's used the various reporting tools for hadoop knows how ugly and painful it is. Without features like exist, or,

Re: Proposal: freeze Thrift starting with 2.1.0

I should add that I'm not trying to ignite a flame war. Just trying to understand your intentions. On Tue, Mar 11, 2014 at 6:50 PM, Steven A Robenalt wrote: > Okay, I'm officially lost on this thread. If you plan on forking Cassandra > to preserve and continue to enhance the Thrift interface, yo

Re: Proposal: freeze Thrift starting with 2.1.0

Okay, I'm officially lost on this thread. If you plan on forking Cassandra to preserve and continue to enhance the Thrift interface, you would also want to add a bunch of relational features to CQL as part of that same fork? On Tue, Mar 11, 2014 at 6:20 PM, Edward Capriolo wrote: > "one of the t

Re: Proposal: freeze Thrift starting with 2.1.0

I have no problems maintain my own fork :) or joining others forking cassandra. I'd be happy to work with you or anyone else to add features to thrift. That's the great thing about open source. Each person can scratch a technical itch and do what they love. I see lots of potential for Cassandra an

Re: Proposal: freeze Thrift starting with 2.1.0

"one of the things I'd like to see happen is for Cassandra to support queries with disjunction, exist, subqueries, joins and like. In theory CQL could support these features in the future. Cassandra would need a new query compiler and query planner. I don't see how the current design could do these

Re: Proposal: freeze Thrift starting with 2.1.0

Peter, My advice. Do not bother. I have become very active recently in attempting to add features to thrift. I had 4 open tickets I was actively working on. (I even found two bugs in the Cassandra in the process). People were aware of this and still called this vote. Several commit people have vo

Re: Proposal: freeze Thrift starting with 2.1.0

My bias opinion, just because some member of cassandra develop want to abandon Thrift, I see benefits of continuing to improve it. The great thing about open source is that as long as some people want to keep working on it and improve it, it can happen. I plan to do my best to keep Thrift going, s

Re: Proposal: freeze Thrift starting with 2.1.0

On Tue, Mar 11, 2014 at 2:41 PM, Shao-Chuan Wang < shaochuan.w...@bloomreach.com> wrote: > > So, does anyone know how to do "describing the splits" and "describing the > local rings" using native protocol? > For a ring description, you would do something like "select peer, tokens from system.peer

Re: Proposal: freeze Thrift starting with 2.1.0

Hi, I just received this email from Jonathan regarding this deprecation of thrift in 2.1 in dev emailing list. In fact, we migrated from thrift client to native one several months ago; however, in the Cassandra.hadoop, there are still a lot of dependencies on thrift interface, for example describ