Re: SSTable Ancestors information in Cassandra 3.0.x

[Jeff Jirsa]

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
using a transaction log, which tracks the source/results on a per
compaction basis, and cassandra uses those logs/journals rather than
inspecting the ancestors.

- Jeff



On Thu, Mar 23, 2017 at 4:35 PM, Rajath Subramanyam 
wrote:

> 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 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
> > incomplete in the upgrade case , so CASSANDRA-13313 may be interesting to
> > people who are very very very very very very very sensitive to data
> > consistency)
> >
> >
> > On Thu, Mar 23, 2017 at 2:00 PM, Rajath Subramanyam 
> > wrote:
> >
> > > 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 test1-b83746000fef11e7bdfc8bb2d6662df7]$
> > > sstablemetadata
> > > ks3-test1-ka-2-Statistics.db | grep "Ancestors"
> > > Ancestors: [1]
> > > [centos@chen-datos test1-b83746000fef11e7bdfc8bb2d6662df7]$
> > >
> > > However, the same tool in Cassandra 3.0.x no longer gives us that
> > > information. Here is a sample output of the sstablemetadata grepping
> for
> > > Ancestors information in C* 3.0 (the output is empty since it is no
> > longer
> > > available):
> > > [centos@rj-cassandra-1 elsevier1-ab7389f0fafb11e6ac23e7ccf62f494b]$
> > > sstablemetadata mc-5-big-Statistics.db | grep "Ancestors"
> > > [centos@rj-cassandra-1 elsevier1-ab7389f0fafb11e6ac23e7ccf62f494b]$
> > >
> > > My question, how can I get this information in C* 3.0.x ?
> > >
> > > Thank you !
> > >
> > > Regards,
> > > Rajath
> > >
> > > 
> > > Rajath Subramanyam
> > >
> >
>

Re: SSTable Ancestors information in Cassandra 3.0.x

[Rajath Subramanyam]

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 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
> incomplete in the upgrade case , so CASSANDRA-13313 may be interesting to
> people who are very very very very very very very sensitive to data
> consistency)
>
>
> On Thu, Mar 23, 2017 at 2:00 PM, Rajath Subramanyam 
> wrote:
>
> > 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 test1-b83746000fef11e7bdfc8bb2d6662df7]$
> > sstablemetadata
> > ks3-test1-ka-2-Statistics.db | grep "Ancestors"
> > Ancestors: [1]
> > [centos@chen-datos test1-b83746000fef11e7bdfc8bb2d6662df7]$
> >
> > However, the same tool in Cassandra 3.0.x no longer gives us that
> > information. Here is a sample output of the sstablemetadata grepping for
> > Ancestors information in C* 3.0 (the output is empty since it is no
> longer
> > available):
> > [centos@rj-cassandra-1 elsevier1-ab7389f0fafb11e6ac23e7ccf62f494b]$
> > sstablemetadata mc-5-big-Statistics.db | grep "Ancestors"
> > [centos@rj-cassandra-1 elsevier1-ab7389f0fafb11e6ac23e7ccf62f494b]$
> >
> > My question, how can I get this information in C* 3.0.x ?
> >
> > Thank you !
> >
> > Regards,
> > Rajath
> >
> > 
> > Rajath Subramanyam
> >
>

Re: DataStax Client List

[Patrick McFadin]

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,
> >
> > 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 leads can also be further customized as per
> requirements.
> >
> > We can provide contact lists from any country/industry/title.
> >
> > If your target criteria are different kindly get back to us with your
> > requirement with geography and job titles to provide you with counts and
> > more information.
> >
> > Let me know your thoughts!
> >
> > Thanks,
> >
> >
> > Theresa
> > Senior Information Analyst
> >
> >
> > If you wish not to receive marketing emails, please reply back
> “Opt
> > Out” In headlines
> >
>

Re: SSTable Ancestors information in Cassandra 3.0.x

[Jeff Jirsa]

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
incomplete in the upgrade case , so CASSANDRA-13313 may be interesting to
people who are very very very very very very very sensitive to data
consistency)


On Thu, Mar 23, 2017 at 2:00 PM, Rajath Subramanyam 
wrote:

> 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 test1-b83746000fef11e7bdfc8bb2d6662df7]$
> sstablemetadata
> ks3-test1-ka-2-Statistics.db | grep "Ancestors"
> Ancestors: [1]
> [centos@chen-datos test1-b83746000fef11e7bdfc8bb2d6662df7]$
>
> However, the same tool in Cassandra 3.0.x no longer gives us that
> information. Here is a sample output of the sstablemetadata grepping for
> Ancestors information in C* 3.0 (the output is empty since it is no longer
> available):
> [centos@rj-cassandra-1 elsevier1-ab7389f0fafb11e6ac23e7ccf62f494b]$
> sstablemetadata mc-5-big-Statistics.db | grep "Ancestors"
> [centos@rj-cassandra-1 elsevier1-ab7389f0fafb11e6ac23e7ccf62f494b]$
>
> My question, how can I get this information in C* 3.0.x ?
>
> Thank you !
>
> Regards,
> Rajath
>
> 
> Rajath Subramanyam
>

SSTable Ancestors information in Cassandra 3.0.x

[Rajath Subramanyam]

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 test1-b83746000fef11e7bdfc8bb2d6662df7]$ sstablemetadata
ks3-test1-ka-2-Statistics.db | grep "Ancestors"
Ancestors: [1]
[centos@chen-datos test1-b83746000fef11e7bdfc8bb2d6662df7]$

However, the same tool in Cassandra 3.0.x no longer gives us that
information. Here is a sample output of the sstablemetadata grepping for
Ancestors information in C* 3.0 (the output is empty since it is no longer
available):
[centos@rj-cassandra-1 elsevier1-ab7389f0fafb11e6ac23e7ccf62f494b]$
sstablemetadata mc-5-big-Statistics.db | grep "Ancestors"
[centos@rj-cassandra-1 elsevier1-ab7389f0fafb11e6ac23e7ccf62f494b]$

My question, how can I get this information in C* 3.0.x ?

Thank you !

Regards,
Rajath


Rajath Subramanyam

Re: Spam Moderation

[daemeon reiydelle]

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 number of recruiters who contact me based on my (more
intelligent at times) postings to this list, there IS a wider audience
listening to this than we think. Therefore I thought it interesting and
insightful to hear the responses.

I agree it is off topic, but IMO do not consider it spam.


*...*



*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872*

On Thu, Mar 23, 2017 at 11:51 AM, Eric Evans 
wrote:

> 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 seen as a valid
> > message about the development of Apache Cassandra?
>
> TL;DR That would be me.
>
> My policy in moderating this list has always been to ignore the
> obvious spam, and default to letting everything else through.  IMO, to
> apply judgment beyond that is a very slippery slope.  Transparency and
> openness are more important to me than protecting everyone from the
> occasional false-positive spam and/or possibly off-topic message.
>
> I also bang through the messages in the queue pretty quickly and make
> the Obvious Spam -or- not judgement almost reflexively.  In this case,
> I guess the lack of HTML, images, or attachments, along with the
> presence of words like "Datastax", and "client" triggered a snap Not
> Spam reaction and I sent it through.
>
> But at least some of the reaction here seems to extend beyond a simple
> matter of a spam message on the list (that has happened before); Some
> here seem to be reacting out of concern to the very existence of the
> email, which makes me think it's precisely the sort of thing that
> shouldn't be kept hidden.
>
>
> --
> Eric Evans
> john.eric.ev...@gmail.com
>

Re: Spam Moderation

[Eric Evans]

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 seen as a valid
> message about the development of Apache Cassandra?

TL;DR That would be me.

My policy in moderating this list has always been to ignore the
obvious spam, and default to letting everything else through.  IMO, to
apply judgment beyond that is a very slippery slope.  Transparency and
openness are more important to me than protecting everyone from the
occasional false-positive spam and/or possibly off-topic message.

I also bang through the messages in the queue pretty quickly and make
the Obvious Spam -or- not judgement almost reflexively.  In this case,
I guess the lack of HTML, images, or attachments, along with the
presence of words like "Datastax", and "client" triggered a snap Not
Spam reaction and I sent it through.

But at least some of the reaction here seems to extend beyond a simple
matter of a spam message on the list (that has happened before); Some
here seem to be reacting out of concern to the very existence of the
email, which makes me think it's precisely the sort of thing that
shouldn't be kept hidden.


-- 
Eric Evans
john.eric.ev...@gmail.com

Re: Spam Moderation

[Michael Shuler]

No replies, please.

This was resolved privately and was a simple mistake.

-- 
Kind regards,
Michael

RE: DataStax Client List

[Bob Dourandish]

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 [mailto:daeme...@gmail.com] 
Sent: Thursday, March 23, 2017 1:46 PM
To: dev@cassandra.apache.org
Subject: 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 looking to charge?

FYI, my goal is to get connected with the resources that provide CIO/CTO level 
headhunting to these CIO/CTO's. Thoughts?


*...*



*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872*

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,
> >
> > 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 leads can also be further customized as per
> requirements.
> >
> > We can provide contact lists from any country/industry/title.
> >
> > If your target criteria are different kindly get back to us with 
> > your requirement with geography and job titles to provide you with 
> > counts and more information.
> >
> > Let me know your thoughts!
> >
> > Thanks,
> >
> >
> > Theresa
> > Senior Information Analyst
> >
> >
> > If you wish not to receive marketing emails, please reply 
> > back
> “Opt
> > Out” In headlines
> >
>

Re: thread architecture of Cassandra

[杨苏立 Yang Su Li]

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,
>
>
>
> You forgot to attach the document.
>
>
>
> *Thanks,*
>
> *Christopher Licata*
>
> Senior Software Engineer
>
> Game Changers
>
> Card Rewards
>
> 718.916.8940 <(718)%20916-8940>
>
>
>
> *From: *杨苏立 Yang Su Li 
> *Reply-To: *"dev@cassandra.apache.org" 
> *Date: *Wednesday, March 22, 2017 at 4:16 PM
> *To: *"dev@cassandra.apache.org" 
> *Cc: *Jing Liu 
> *Subject: *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 (attached). I am wondering if the developers of
> Cassandra could take a look at it and let me know if anything is incorrect
> or inaccurate, or if I have missed anything.
>
> Thanks a lot for your help!
>
>
>
> On Wed, Mar 22, 2017 at 3:10 PM, 杨苏立 Yang Su Li 
> wrote:
>
> 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 (attached). I am wondering if the developers of
> Cassandra could take a look at it and let me know if anything is incorrect
> or inaccurate, or if I have missed anything.
>
> Thanks a lot for your help!
>
> Suli
>
>
>
> --
>
> Suli Yang
>
> Department of Physics
> University of Wisconsin Madison
>
> 4257 Chamberlin Hall
> Madison WI 53703
>
>
>
>
> --
>
> Suli Yang
>
> Department of Physics
> University of Wisconsin Madison
>
> 4257 Chamberlin Hall
> Madison WI 53703
>
> --
>
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The information
> transmitted herewith is intended only for use by the individual or entity
> to which it is addressed. If the reader of this message is not the intended
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon this information is strictly prohibited. If you
> have received this communication in error, please contact the sender and
> delete the material from your computer.
>



-- 
Suli Yang

Department of Physics
University of Wisconsin Madison

4257 Chamberlin Hall
Madison WI 53703

Re: DataStax Client List

[Jeff Jirsa]

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 beyond
this one warning.

- Jeff


On Thu, Mar 23, 2017 at 10:46 AM, daemeon reiydelle 
wrote:

>
>
>
> *Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872*
>
> 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:
> >
> > >
> >
>

Re: DataStax Client List

[daemeon reiydelle]

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 looking to charge?

FYI, my goal is to get connected with the resources that provide CIO/CTO
level headhunting to these CIO/CTO's. Thoughts?


*...*



*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872*

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,
> >
> > 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 leads can also be further customized as per
> requirements.
> >
> > We can provide contact lists from any country/industry/title.
> >
> > If your target criteria are different kindly get back to us with your
> > requirement with geography and job titles to provide you with counts and
> > more information.
> >
> > Let me know your thoughts!
> >
> > Thanks,
> >
> >
> > Theresa
> > Senior Information Analyst
> >
> >
> > If you wish not to receive marketing emails, please reply back
> “Opt
> > Out” In headlines
> >
>

Re: Spam Moderation

[Edward Capriolo]

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 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,
> > Michael
> >
>
>
>
> --
> *Most people have more than the average number of legs*
>

While the dev list is not clearly the place, and ithe email is spam looking
it is interesting to know that someone is marketing such a list. I have
spoken at different events an those entities likely have my email so I am
curious about the list.

I think the situation is much like the "Free bsd backdoor emails"
http://marc.info/?l=openbsd-tech=129236621626462=2 . IE even if you
believe  99.999% the info untrue do you pass the info along?

Re: DataStax Client List

[Edward Capriolo]

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 name, Phone number, Email Address, Company
> Name, Job Title, Address, City, State, Zip, SIC code/Industry, Revenue and
> Company Size. The leads can also be further customized as per requirements.
>
> We can provide contact lists from any country/industry/title.
>
> If your target criteria are different kindly get back to us with your
> requirement with geography and job titles to provide you with counts and
> more information.
>
> Let me know your thoughts!
>
> Thanks,
>
>
> Theresa
> Senior Information Analyst
>
>
> If you wish not to receive marketing emails, please reply back “Opt
> Out” In headlines
>

Re: Spam Moderation

[Daryl Hawken]

+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 was seen as a valid
> message about the development of Apache Cassandra?
>
> --
> Kind regards,
> Michael
>



-- 
*Most people have more than the average number of legs*

Spam Moderation

[Michael Shuler]

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,
Michael

Re: DataStax Client List

[Mark Greene]

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 number, Email Address, Company
> Name, Job Title, Address, City, State, Zip, SIC code/Industry, Revenue and
> Company Size. The leads can also be further customized as per requirements.
> 
> We can provide contact lists from any country/industry/title.
> 
> If your target criteria are different kindly get back to us with your
> requirement with geography and job titles to provide you with counts and
> more information.
> 
> Let me know your thoughts!
> 
> Thanks,
> 
> 
> Theresa
> Senior Information Analyst
> 
> 
>If you wish not to receive marketing emails, please reply back “Opt
> Out” In headlines

Re: thread architecture of Cassandra

[杨苏立 Yang Su Li]

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 (attached). I am wondering if the developers of
Cassandra could take a look at it and let me know if anything is incorrect
or inaccurate, or if I have missed anything.

Thanks a lot for your help!

On Wed, Mar 22, 2017 at 3:10 PM, 杨苏立 Yang Su Li  wrote:

> 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 (attached). I am wondering if the developers of
> Cassandra could take a look at it and let me know if anything is incorrect
> or inaccurate, or if I have missed anything.
>
> Thanks a lot for your help!
>
> Suli
>
>
> --
> Suli Yang
>
> Department of Physics
> University of Wisconsin Madison
>
> 4257 Chamberlin Hall
> Madison WI 53703
>
>


-- 
Suli Yang

Department of Physics
University of Wisconsin Madison

4257 Chamberlin Hall
Madison WI 53703

DataStax Client List

[Theresa Taylor]

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 leads can also be further customized as per requirements.

We can provide contact lists from any country/industry/title.

If your target criteria are different kindly get back to us with your
requirement with geography and job titles to provide you with counts and
more information.

Let me know your thoughts!

Thanks,


Theresa
Senior Information Analyst


If you wish not to receive marketing emails, please reply back “Opt
Out” In headlines

Re: splitting CQL parser & spec into separate repo

[Edward Capriolo]

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 https://maven.apache.org/guides/mini/guide-multiple-modules.html
> .
> > Probably not as easy thanks to ant, but I think that is a better route.
> One
> > there actually are N dependent projects in the wild you can make the case
> > for overhead which is both technical and in ASF based.
>
> This was my first thought: If we were using Maven, we'd probably
> already have created this as a module[*].
>
>
> [*]: Maybe a surprise to some given how strongly I pushed back against
> it in the Early Days, but we would be so much better off at this point
> with Maven.
>
>
> --
> Eric Evans
> john.eric.ev...@gmail.com
>

Well the ant maven bit is a separate issue: It still could be done with
ant, it could be done in a way that the port is very easy.
http://ant.apache.org/easyant/history/trunk/ref/anttasks/SubModuletask.html

Re: splitting CQL parser & spec into separate repo

[Eric Evans]

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 route. One
> there actually are N dependent projects in the wild you can make the case
> for overhead which is both technical and in ASF based.

This was my first thought: If we were using Maven, we'd probably
already have created this as a module[*].


[*]: Maybe a surprise to some given how strongly I pushed back against
it in the Early Days, but we would be so much better off at this point
with Maven.


-- 
Eric Evans
john.eric.ev...@gmail.com