Re: DataStax Client List

This has to be the most entertaining dev list in all of the ASFs On Thu, Mar 23, 2017 at 9:52 AM, Edward Capriolo wrote: > Well that is quite unsettling. > > On Thu, Mar 23, 2017 at 10:33 AM, Theresa Taylor < > theresa.tay...@onlinedatatech.biz> wrote: > > > Hi, > > > >

SSTable Ancestors information in Cassandra 3.0.x

Hello Cassandra-Users and Cassandra-dev, One of the handy features in sstablemetadata that was part of Cassandra 2.1.15 was that it displayed Ancestor information of an SSTable. Here is a sample output of the sstablemetadata tool with the ancestors information in C* 2.1.15: [centos@chen-datos

Re: SSTable Ancestors information in Cassandra 3.0.x

That information was removed, because it was really meant to be used for a handful of internal tasks, most of which were no longer used. The remaining use was cleaning up compaction leftovers, and the compaction leftover code was rewritten in 3.0 / CASSANDRA-7066 (note, though, that it's somewhat

Re: SSTable Ancestors information in Cassandra 3.0.x

Thanks, Jeff. Did all the internal tasks and the compaction tasks move to a timestamp-based approach? Regards, Rajath Rajath Subramanyam On Thu, Mar 23, 2017 at 2:12 PM, Jeff Jirsa wrote: > That information was removed, because it was really meant

Re: SSTable Ancestors information in Cassandra 3.0.x

The ancestors were used primarily to clean up leftovers in the case that cassandra was killed right as compaction finished, where the source/origin/ancestors were still on the disk at the same time as the compaction result. It's not timestamp based, though - that compaction process has moved to

Re: DataStax Client List

The original email and this reply are totally inappropriate. At best, this is a wholly invalid use of the list to peddle fake contact lists. At worst, it's inappropriately disseminating a list that's likely covered under NDA. I'll be unsubscribing any user who continues to humor this poster

Re: thread architecture of Cassandra

Hi, Sorry the original email is missing attachement. You can find attachment in the following URL: http://pages.cs.wisc.edu/~suli/cassandra.pdf Thanks a lot for you help! Suli On Thu, Mar 23, 2017 at 10:43 AM, Licata, Christopher < christopher.lic...@capitalone.com> wrote: > Hey Suli, > > >

RE: DataStax Client List

Daemeon: Please have this conversation DIRECTLY with the spammer, instead of replying to the entire list. I don't need to waste any more time on this, nor do I care to know the details of your transaction with these people. Bob -Original Message- From: daemeon reiydelle

Re: Spam Moderation

No replies, please. This was resolved privately and was a simple mistake. -- Kind regards, Michael

Re: DataStax Client List

Hi Theresa, While some may be fussing at this, I am not concerned. I AM interested in something of the sort, which would be a list of contacts who are CTO, CIO, etc. using big data. Just Hadoop (Datastax) is fine, or those using other big data providers would be of interest. What are you

Re: DataStax Client List

Well that is quite unsettling. On Thu, Mar 23, 2017 at 10:33 AM, Theresa Taylor < theresa.tay...@onlinedatatech.biz> wrote: > Hi, > > Would you be interested in acquiring a list of DataStax users' information > in an Excel sheet for unlimited marketing usage? > > List includes – First and Last

Re: Spam Moderation

On Thu, Mar 23, 2017 at 12:42 PM, Daryl Hawken wrote: > +1. > > On Thu, Mar 23, 2017 at 12:10 PM, Michael Shuler > wrote: > > > I won't reply to the obvious spam to hilight it any further, so new > > message.. > > > > Could the mailing list

Re: Spam Moderation

+1. On Thu, Mar 23, 2017 at 12:10 PM, Michael Shuler wrote: > I won't reply to the obvious spam to hilight it any further, so new > message.. > > Could the mailing list moderator that approved the "client list" message > identify themselves and possibly explain how that

Re: thread architecture of Cassandra

Hi, I am a graduate student working on scheduling on storage systems, and we are interested in how different threads in Cassandra interact with each other and how it might affect scheduling. I have written down my understanding on how Cassandra works based on its current thread architecture

DataStax Client List

Hi, Would you be interested in acquiring a list of DataStax users' information in an Excel sheet for unlimited marketing usage? List includes – First and Last name, Phone number, Email Address, Company Name, Job Title, Address, City, State, Zip, SIC code/Industry, Revenue and Company Size. The

Re: splitting CQL parser & spec into separate repo

On Wed, Mar 22, 2017 at 10:01 AM, Edward Capriolo wrote: > I believe you could accomplish a similar goal by making a multi-module > project https://maven.apache.org/guides/mini/guide-multiple-modules.html. > Probably not as easy thanks to ant, but I think that is a better

Re: splitting CQL parser & spec into separate repo

On Thu, Mar 23, 2017 at 10:56 AM, Eric Evans wrote: > On Wed, Mar 22, 2017 at 10:01 AM, Edward Capriolo > wrote: > > I believe you could accomplish a similar goal by making a multi-module > > project

Spam Moderation

I won't reply to the obvious spam to hilight it any further, so new message.. Could the mailing list moderator that approved the "client list" message identify themselves and possibly explain how that was seen as a valid message about the development of Apache Cassandra? -- Kind regards,

Re: DataStax Client List

YES!  > On Mar 23, 2017, at 10:33 AM, Theresa Taylor > wrote: > > Hi, > > Would you be interested in acquiring a list of DataStax users' information > in an Excel sheet for unlimited marketing usage? > > List includes – First and Last name, Phone

Re: Spam Moderation

In spite of what was intended to be an out of channel email (thank you gmail for deciding to change the email address, grr ;{) I both recognize that these resources exist, think that they are not appropriate for this channel, but think they ARE appropriate "in some other channel". Given the

Re: Spam Moderation

On Thu, Mar 23, 2017 at 11:10 AM, Michael Shuler wrote: > I won't reply to the obvious spam to hilight it any further, so new > message.. > > Could the mailing list moderator that approved the "client list" message > identify themselves and possibly explain how that was