[VOTE PASSED] Release Apache Cassandra 1.2.13 (Strike 3)
Including my own, I count 5 binding +1, one other +1 and no -1. The vote passes. I'll get the artifacts published asap. -- Sylvain On Wed, Dec 18, 2013 at 10:56 PM, Gary Dusbabek wrote: > +1 > > > On Wed, Dec 18, 2013 at 3:46 AM, Sylvain Lebresne >wrote: > > > Third time's the charm, I propose the following artifacts for release as > > 1.2.13. > > > > sha1: 1b4c9b45cbf32a72318c42c1ec6154dc1371e8e2 > > Git: > > > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.13-tentative > > Artifacts: > > > > > https://repository.apache.org/content/repositories/orgapachecassandra-066/org/apache/cassandra/apache-cassandra/1.2.13/ > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachecassandra-066/ > > > > The artifacts as well as the debian package are also available here: > > http://people.apache.org/~slebresne/ > > > > Since it is a re-roll, I propose an expediated vote so the vote will be > > open for 24 hours (but longer if needed). > > > > [1]: http://goo.gl/ELcvdB (CHANGES.txt) > > [2]: http://goo.gl/lVJqUQ (NEWS.txt) > > >
C* engine
Hello, Don't want to rise "holy war". Just let me share my crazy thoughts. I believe it could improve Cassandra speed and robustness. What people will say if I propose to have Cassandra engine written in C/C++, and this engine will give you ability to run extensions in Java, Groovy and bunch other languages like Perl/Python/Ruby? I just want to understand for myself does this solution will be useful or I'm looking in wrong direction? Thank you for understanding.
C* engine
Hello, Don't want to rise "holy war". Just let me share my crazy thoughts. I believe it could improve Cassandra speed and robustness. What people will say if I propose to have Cassandra engine written in C/C++, and this engine will give you ability to run extensions in Java, Groovy and bunch other languages like Perl/Python/Ruby? I just want to understand for myself does this solution will be useful or I'm looking in wrong direction? Thank you for reading.
Re[4]: C* engine
Definitely not weekend, I thought about a year of hard development. I went throw Cassandra code, and can see a lot of work. -- Original Message -- From: "Michael Kjellman" To: "dev@cassandra.apache.org" ; "Roman Vasilyev" Cc: "Brandon Williams" Sent: 12/19/2013 11:38:54 AM Subject: Re: Re[2]: C* engine You seem to think something like this is akin to a weekend project. I would recommend you actually read some of the Cassandra source code and better understand how it is architected. On Dec 19, 2013, at 11:30 AM, "Roman Vasilyev" wrote: I'm not talking to throw away currently working code. Just port it to C/C++, and have option to run Java based or "native" binary. -- Original Message -- From: "Brandon Williams" To: dev@cassandra.apache.org; "Roman Vasilyev" Sent: 12/19/2013 11:26:21 AM Subject: Re: C* engine Let's ask what we'll lose here. 4 years of work, tons of debugging, loads of instrumentation, for what gain? Almost nil. On Thu, Dec 19, 2013 at 1:22 PM, Roman Vasilyev wrote: Hello, Don't want to rise "holy war". Just let me share my crazy thoughts. I believe it could improve Cassandra speed and robustness. What people will say if I propose to have Cassandra engine written in C/C++, and this engine will give you ability to run extensions in Java, Groovy and bunch other languages like Perl/Python/Ruby? I just want to understand for myself does this solution will be useful or I'm looking in wrong direction? Thank you for reading. === Find out how eSigning generates significant financial benefit. Read the Barracuda SignNow ROI whitepaper at https://signnow.com/l/business/esignature_roi
Re: Re[2]: C* engine
You seem to think something like this is akin to a weekend project. I would recommend you actually read some of the Cassandra source code and better understand how it is architected. > On Dec 19, 2013, at 11:30 AM, "Roman Vasilyev" wrote: > > I'm not talking to throw away currently working code. Just port it to > C/C++, and have option to run Java based or "native" binary. > > -- Original Message -- > From: "Brandon Williams" > To: dev@cassandra.apache.org; "Roman Vasilyev" > Sent: 12/19/2013 11:26:21 AM > Subject: Re: C* engine > >> Let's ask what we'll lose here. >> >> 4 years of work, tons of debugging, loads of instrumentation, for what >> gain? Almost nil. >> >> >> On Thu, Dec 19, 2013 at 1:22 PM, Roman Vasilyev >> wrote: >>> Hello, >>> >>> Don't want to rise "holy war". Just let me share my crazy thoughts. >>> I believe it could improve Cassandra speed and robustness. >>> >>> What people will say if I propose to have Cassandra engine written in >>> C/C++, and this engine will give you ability to run extensions in >>> Java, Groovy and bunch other languages like Perl/Python/Ruby? >>> >>> I just want to understand for myself does this solution will be useful >>> or I'm looking in wrong direction? >>> >>> Thank you for reading. === Find out how eSigning generates significant financial benefit. Read the Barracuda SignNow ROI whitepaper at https://signnow.com/l/business/esignature_roi
Re: Re[4]: C* engine
I'm not sure I see a point in this as opposed to developing new features. On Thu, Dec 19, 2013 at 1:42 PM, Roman Vasilyev wrote: > Definitely not weekend, I thought about a year of hard development. I went > throw Cassandra code, and can see a lot of work. > > > -- Original Message -- > From: "Michael Kjellman" > To: "dev@cassandra.apache.org" ; "Roman > Vasilyev" > Cc: "Brandon Williams" > Sent: 12/19/2013 11:38:54 AM > Subject: Re: Re[2]: C* engine > > You seem to think something like this is akin to a weekend project. I >> would recommend you actually read some of the Cassandra source code and >> better understand how it is architected. >> >> On Dec 19, 2013, at 11:30 AM, "Roman Vasilyev" >>> wrote: >>> >>> I'm not talking to throw away currently working code. Just port it to >>> C/C++, and have option to run Java based or "native" binary. >>> >>> -- Original Message -- >>> From: "Brandon Williams" >>> To: dev@cassandra.apache.org; "Roman Vasilyev" >>> Sent: 12/19/2013 11:26:21 AM >>> Subject: Re: C* engine >>> >>> Let's ask what we'll lose here. 4 years of work, tons of debugging, loads of instrumentation, for what gain? Almost nil. On Thu, Dec 19, 2013 at 1:22 PM, Roman Vasilyev >>> > wrote: > Hello, > > Don't want to rise "holy war". Just let me share my crazy thoughts. > I believe it could improve Cassandra speed and robustness. > > What people will say if I propose to have Cassandra engine written in > C/C++, and this engine will give you ability to run extensions in > Java, Groovy and bunch other languages like Perl/Python/Ruby? > > I just want to understand for myself does this solution will be useful > or I'm looking in wrong direction? > > Thank you for reading. > >> === >> >> >> >> Find out how eSigning generates significant financial benefit. >> >> Read the Barracuda SignNow ROI whitepaper at https://signnow.com/l/ >> business/esignature_roi >> > >
Re: C* engine
The question just as easily be asked, why not rewrite it in Erlang ? Probably lots of advantages to be gained there, the ability to upgrade on the fly, native message passing, functional programming paradigm ? But as Brandon says, you would be throwing away so much work, would it be worth it ? Andy On 19 Dec 2013, at 19:22, Roman Vasilyev wrote: > Hello, > > Don't want to rise "holy war". Just let me share my crazy thoughts. > I believe it could improve Cassandra speed and robustness. > > What people will say if I propose to have Cassandra engine written in C/C++, > and this engine will give you ability to run extensions in Java, Groovy and > bunch other languages like Perl/Python/Ruby? > > I just want to understand for myself does this solution will be useful or I'm > looking in wrong direction? > > Thank you for reading. The University of Dundee is a Scottish Registered Charity, No. SC015096.
Re: C* engine
Roman, I would start with figuring out exactly how much performance you’re losing because of the language and whether there is lower hanging fruit. For the record, I *hate* java, but my experience in performance work has taught me that with some exceptions, it’s rarely the language where the performance sink is. Do you have any data that points to Java as being a performance problem? Cheers, -Oscar On Dec 19, 2013, at 11:46 AM, Roman Vasilyev wrote: > Never will say that Erlang will be faster and memory consumption will be > lower than native code. Rest of it totally agree with Brandon, in a few words > I'm talking about serious parallel project on improving Cassandra basics. > > -- Original Message -- > From: "Andy Cobley" > To: "" ; "Roman Vasilyev" > > Sent: 12/19/2013 11:40:55 AM > Subject: Re: C* engine > >> The question just as easily be asked, why not rewrite it in Erlang ? >> Probably lots of advantages to be gained there, the ability to upgrade on >> the fly, native message passing, functional programming paradigm ? >> >> But as Brandon says, you would be throwing away so much work, would it be >> worth it ? >> >> Andy >> >> >> On 19 Dec 2013, at 19:22, Roman Vasilyev wrote: >> >>> Hello, >>> >>> Don't want to rise "holy war". Just let me share my crazy thoughts. >>> I believe it could improve Cassandra speed and robustness. >>> >>> What people will say if I propose to have Cassandra engine written in >>> C/C++, and this engine will give you ability to run extensions in Java, >>> Groovy and bunch other languages like Perl/Python/Ruby? >>> >>> I just want to understand for myself does this solution will be useful or >>> I'm looking in wrong direction? >>> >>> Thank you for reading. >> >> >> The University of Dundee is a Scottish Registered Charity, No. SC015096. >> >> >
Re: C* engine
There is a _lot_ of room for performance improvements, both in terms of design decisions but even more so in terms of implementation specifics on there. I don’t think it makes sense (any kind of sense) to rewrite to C or any other language, given the amount of work and(perhaps most importantly) testing that was put on C* so far, but, choosing a different language is not what’s most important here in terms of extracting performance; improving existing codebase is the right thing to do, however, as I understand it, improving what’s already there in terms of stability and conformance and releasing new features is a higher priority item for the developers, for now. It will happen though. Mark Papadakis On Dec 19, 2013, at 9:22 PM, Roman Vasilyev wrote: > Hello, > > Don't want to rise "holy war". Just let me share my crazy thoughts. > I believe it could improve Cassandra speed and robustness. > > What people will say if I propose to have Cassandra engine written in C/C++, > and this engine will give you ability to run extensions in Java, Groovy and > bunch other languages like Perl/Python/Ruby? > > I just want to understand for myself does this solution will be useful or I'm > looking in wrong direction? > > Thank you for reading.
Re[2]: C* engine
I'm not talking to throw away currently working code. Just port it to C/C++, and have option to run Java based or "native" binary. -- Original Message -- From: "Brandon Williams" To: dev@cassandra.apache.org; "Roman Vasilyev" Sent: 12/19/2013 11:26:21 AM Subject: Re: C* engine Let's ask what we'll lose here. 4 years of work, tons of debugging, loads of instrumentation, for what gain? Almost nil. On Thu, Dec 19, 2013 at 1:22 PM, Roman Vasilyev wrote: Hello, Don't want to rise "holy war". Just let me share my crazy thoughts. I believe it could improve Cassandra speed and robustness. What people will say if I propose to have Cassandra engine written in C/C++, and this engine will give you ability to run extensions in Java, Groovy and bunch other languages like Perl/Python/Ruby? I just want to understand for myself does this solution will be useful or I'm looking in wrong direction? Thank you for reading.
Re[2]: C* engine
Never will say that Erlang will be faster and memory consumption will be lower than native code. Rest of it totally agree with Brandon, in a few words I'm talking about serious parallel project on improving Cassandra basics. -- Original Message -- From: "Andy Cobley" To: "" ; "Roman Vasilyev" Sent: 12/19/2013 11:40:55 AM Subject: Re: C* engine The question just as easily be asked, why not rewrite it in Erlang ? Probably lots of advantages to be gained there, the ability to upgrade on the fly, native message passing, functional programming paradigm ? But as Brandon says, you would be throwing away so much work, would it be worth it ? Andy On 19 Dec 2013, at 19:22, Roman Vasilyev wrote: Hello, Don't want to rise "holy war". Just let me share my crazy thoughts. I believe it could improve Cassandra speed and robustness. What people will say if I propose to have Cassandra engine written in C/C++, and this engine will give you ability to run extensions in Java, Groovy and bunch other languages like Perl/Python/Ruby? I just want to understand for myself does this solution will be useful or I'm looking in wrong direction? Thank you for reading. The University of Dundee is a Scottish Registered Charity, No. SC015096.
Re: C* engine
I can agree with you on Java, but the JVM is a different matter. It is wonderful. On Thu, Dec 19, 2013 at 1:50 PM, Oscar Bonilla <6f6...@gmail.com> wrote: > Roman, > > I would start with figuring out exactly how much performance you’re losing > because of the language and whether there is lower hanging fruit. For the > record, I *hate* java, but my experience in performance work has taught me > that with some exceptions, it’s rarely the language where the performance > sink is. > > Do you have any data that points to Java as being a performance problem? > > Cheers, > > -Oscar > > On Dec 19, 2013, at 11:46 AM, Roman Vasilyev > wrote: > > > Never will say that Erlang will be faster and memory consumption will be > lower than native code. Rest of it totally agree with Brandon, in a few > words I'm talking about serious parallel project on improving Cassandra > basics. > > > > -- Original Message -- > > From: "Andy Cobley" > > To: "" ; "Roman > Vasilyev" > > Sent: 12/19/2013 11:40:55 AM > > Subject: Re: C* engine > > > >> The question just as easily be asked, why not rewrite it in Erlang ? > Probably lots of advantages to be gained there, the ability to upgrade on > the fly, native message passing, functional programming paradigm ? > >> > >> But as Brandon says, you would be throwing away so much work, would it > be worth it ? > >> > >> Andy > >> > >> > >> On 19 Dec 2013, at 19:22, Roman Vasilyev wrote: > >> > >>> Hello, > >>> > >>> Don't want to rise "holy war". Just let me share my crazy thoughts. > >>> I believe it could improve Cassandra speed and robustness. > >>> > >>> What people will say if I propose to have Cassandra engine written in > C/C++, and this engine will give you ability to run extensions in Java, > Groovy and bunch other languages like Perl/Python/Ruby? > >>> > >>> I just want to understand for myself does this solution will be useful > or I'm looking in wrong direction? > >>> > >>> Thank you for reading. > >> > >> > >> The University of Dundee is a Scottish Registered Charity, No. SC015096. > >> > >> > > > >
Re: C* engine
Yeah, agreed. On Dec 19, 2013, at 11:54 AM, Brandon Williams wrote: > I can agree with you on Java, but the JVM is a different matter. It is > wonderful. > > > On Thu, Dec 19, 2013 at 1:50 PM, Oscar Bonilla <6f6...@gmail.com> wrote: > >> Roman, >> >> I would start with figuring out exactly how much performance you’re losing >> because of the language and whether there is lower hanging fruit. For the >> record, I *hate* java, but my experience in performance work has taught me >> that with some exceptions, it’s rarely the language where the performance >> sink is. >> >> Do you have any data that points to Java as being a performance problem? >> >> Cheers, >> >> -Oscar >> >> On Dec 19, 2013, at 11:46 AM, Roman Vasilyev >> wrote: >> >>> Never will say that Erlang will be faster and memory consumption will be >> lower than native code. Rest of it totally agree with Brandon, in a few >> words I'm talking about serious parallel project on improving Cassandra >> basics. >>> >>> -- Original Message -- >>> From: "Andy Cobley" >>> To: "" ; "Roman >> Vasilyev" >>> Sent: 12/19/2013 11:40:55 AM >>> Subject: Re: C* engine >>> The question just as easily be asked, why not rewrite it in Erlang ? >> Probably lots of advantages to be gained there, the ability to upgrade on >> the fly, native message passing, functional programming paradigm ? But as Brandon says, you would be throwing away so much work, would it >> be worth it ? Andy On 19 Dec 2013, at 19:22, Roman Vasilyev wrote: > Hello, > > Don't want to rise "holy war". Just let me share my crazy thoughts. > I believe it could improve Cassandra speed and robustness. > > What people will say if I propose to have Cassandra engine written in >> C/C++, and this engine will give you ability to run extensions in Java, >> Groovy and bunch other languages like Perl/Python/Ruby? > > I just want to understand for myself does this solution will be useful >> or I'm looking in wrong direction? > > Thank you for reading. The University of Dundee is a Scottish Registered Charity, No. SC015096. >>> >> >>
Re[2]: C* engine
One of the core problems what I can see is garbage collection, it blocks whole server just to clean memory, same stuff with periods of it. On high load you constantly have to control does the heap close to the limit specified on start. -- Original Message -- From: "Oscar Bonilla" <6f6...@gmail.com> To: "Roman Vasilyev" Cc: dev@cassandra.apache.org Sent: 12/19/2013 11:50:10 AM Subject: Re: C* engine Roman, I would start with figuring out exactly how much performance you’re losing because of the language and whether there is lower hanging fruit. For the record, I *hate* java, but my experience in performance work has taught me that with some exceptions, it’s rarely the language where the performance sink is. Do you have any data that points to Java as being a performance problem? Cheers, -Oscar On Dec 19, 2013, at 11:46 AM, Roman Vasilyev wrote: Never will say that Erlang will be faster and memory consumption will be lower than native code. Rest of it totally agree with Brandon, in a few words I'm talking about serious parallel project on improving Cassandra basics. -- Original Message -- From: "Andy Cobley" To: "" ; "Roman Vasilyev" Sent: 12/19/2013 11:40:55 AM Subject: Re: C* engine The question just as easily be asked, why not rewrite it in Erlang ? Probably lots of advantages to be gained there, the ability to upgrade on the fly, native message passing, functional programming paradigm ? But as Brandon says, you would be throwing away so much work, would it be worth it ? Andy On 19 Dec 2013, at 19:22, Roman Vasilyev wrote: Hello, Don't want to rise "holy war". Just let me share my crazy thoughts. I believe it could improve Cassandra speed and robustness. What people will say if I propose to have Cassandra engine written in C/C++, and this engine will give you ability to run extensions in Java, Groovy and bunch other languages like Perl/Python/Ruby? I just want to understand for myself does this solution will be useful or I'm looking in wrong direction? Thank you for reading. The University of Dundee is a Scottish Registered Charity, No. SC015096.
Re: Re[2]: C* engine
That's why we move things off-heap. On Thu, Dec 19, 2013 at 1:57 PM, Roman Vasilyev wrote: > One of the core problems what I can see is garbage collection, it blocks > whole server just to clean memory, same stuff with periods of it. On high > load you constantly have to control does the heap close to the limit > specified on start. > > > -- Original Message -- > From: "Oscar Bonilla" <6f6...@gmail.com> > To: "Roman Vasilyev" > Cc: dev@cassandra.apache.org > Sent: 12/19/2013 11:50:10 AM > Subject: Re: C* engine > > Roman, >> >> I would start with figuring out exactly how much performance you’re >> losing because of the language and whether there is lower hanging fruit. >> For the record, I *hate* java, but my experience in performance work has >> taught me that with some exceptions, it’s rarely the language where the >> performance sink is. >> >> Do you have any data that points to Java as being a performance problem? >> >> Cheers, >> >> -Oscar >> >> On Dec 19, 2013, at 11:46 AM, Roman Vasilyev >> wrote: >> >> Never will say that Erlang will be faster and memory consumption will >>> be lower than native code. Rest of it totally agree with Brandon, in a few >>> words I'm talking about serious parallel project on improving Cassandra >>> basics. >>> >>> -- Original Message -- >>> From: "Andy Cobley" >>> To: "" ; "Roman >>> Vasilyev" >>> Sent: 12/19/2013 11:40:55 AM >>> Subject: Re: C* engine >>> >>> The question just as easily be asked, why not rewrite it in Erlang ? Probably lots of advantages to be gained there, the ability to upgrade on the fly, native message passing, functional programming paradigm ? But as Brandon says, you would be throwing away so much work, would it be worth it ? Andy On 19 Dec 2013, at 19:22, Roman Vasilyev wrote: Hello, > > Don't want to rise "holy war". Just let me share my crazy thoughts. > I believe it could improve Cassandra speed and robustness. > > What people will say if I propose to have Cassandra engine written in > C/C++, and this engine will give you ability to run extensions in Java, > Groovy and bunch other languages like Perl/Python/Ruby? > > I just want to understand for myself does this solution will be > useful or I'm looking in wrong direction? > > Thank you for reading. > The University of Dundee is a Scottish Registered Charity, No. SC015096. >>> >> >
Re: C* engine
On Dec 19, 2013, at 11:40 AM, Andy Cobley wrote: > The question just as easily be asked, why not rewrite it in Erlang ? > Probably lots of advantages to be gained there, the ability to upgrade on the > fly, native message passing, functional programming paradigm ? You could switch from Java to Scala and gain on the functional programming paradigm in an incremental basis. Blair
Re: Best avenue for reporting security issues
http://www.apache.org/security/ email secur...@apache.org since there isn't a Cassandra specific security list. This will also help with getting things like CVEs assigned and making sure balls are not dropped. On Tue, Dec 17, 2013 at 3:30 PM, Ben Bromhead wrote: > Hi guys > > We’ve come across a bug with potential security implications and in the > spirit of responsible disclosure whats the best path for reporting it / > submitting patches without making the issue public until a fixed version of > Cassandra is released? > > As a follow up I would propose that the Cassandra project should have > secur...@cassandra.apache.org mailing address, where sensitive issues can be > reported to the core dev team without it being made public. > > Regards > > Ben Bromhead > Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359 >
Re: C* engine
Let's ask what we'll lose here. 4 years of work, tons of debugging, loads of instrumentation, for what gain? Almost nil. On Thu, Dec 19, 2013 at 1:22 PM, Roman Vasilyev wrote: > Hello, > > Don't want to rise "holy war". Just let me share my crazy thoughts. > I believe it could improve Cassandra speed and robustness. > > What people will say if I propose to have Cassandra engine written in > C/C++, and this engine will give you ability to run extensions in Java, > Groovy and bunch other languages like Perl/Python/Ruby? > > I just want to understand for myself does this solution will be useful or > I'm looking in wrong direction? > > Thank you for reading.
Re: C* engine
[ Roman Vasilyev ] > Don't want to rise "holy war". Just let me share my crazy thoughts. > I believe it could improve Cassandra speed and robustness. That's an awfully large reset button you want to press, presumably the benefits will justify the enormity of effort? What are we talking here, 10x improvement? 100x improvement? More? > What people will say if I propose to have Cassandra engine written > in C/C++, and this engine will give you ability to run extensions in > Java, Groovy and bunch other languages like Perl/Python/Ruby? No one can stop you from working on this; Good luck P.S. Please subscribe to the list (dev-subsrc...@cassandra.apache.org) -- Eric Evans eev...@sym-link.com
Re[2]: C* engine
This is what I expected as an answer, that effort just fully destroying any benefits. All what I can hear is just better not touch stuff which works and find improvements different way. Change (algorithms/caching/...) where I agree, and seems like bottleneck will be FS I/O or network delays. Just want to thank you for all answers on my question. -- Original Message -- From: "Eric Evans" To: dev@cassandra.apache.org; "Roman Vasilyev" Sent: 12/19/2013 1:47:03 PM Subject: Re: C* engine [ Roman Vasilyev ] Don't want to rise "holy war". Just let me share my crazy thoughts. I believe it could improve Cassandra speed and robustness. That's an awfully large reset button you want to press, presumably the benefits will justify the enormity of effort? What are we talking here, 10x improvement? 100x improvement? More? What people will say if I propose to have Cassandra engine written in C/C++, and this engine will give you ability to run extensions in Java, Groovy and bunch other languages like Perl/Python/Ruby? No one can stop you from working on this; Good luck P.S. Please subscribe to the list (dev-subsrc...@cassandra.apache.org) -- Eric Evans eev...@sym-link.com
Re: Could .gitignore be added? (was: can test/Test.iml be removed?)
I can't think of any. On Sat, Dec 14, 2013 at 11:14 AM, Michael Shuler wrote: > On 12/13/2013 11:28 PM, graham sanderson wrote: >> >> This seemed to get introduced (by mistake?) in ef33f9543 > > > Would there be any issues with adding a .gitignore to the repository? I > could work one up. > > -- > Kind regards, > Michael > > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Could .gitignore be added? (was: can test/Test.iml be removed?)
The first thing I did when I forked the Cassandra repo was add a .gitignore: --- cut here --- .classpath .idea/ .project build/ src/gen-java/ cassandra.iml *.pyc cscope.* *.swp *~ src/resources/org/apache/cassandra/config/ --- cut here --- On Dec 19, 2013, at 2:16 PM, Jonathan Ellis wrote: > I can't think of any. > > On Sat, Dec 14, 2013 at 11:14 AM, Michael Shuler > wrote: >> On 12/13/2013 11:28 PM, graham sanderson wrote: >>> >>> This seemed to get introduced (by mistake?) in ef33f9543 >> >> >> Would there be any issues with adding a .gitignore to the repository? I >> could work one up. >> >> -- >> Kind regards, >> Michael >> >> > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder, http://www.datastax.com > @spyced
Re: Could .gitignore be added?
How about this for a .gitignore? I mixed in Oscar's, CASSANDRA-4899, a few more general ones which are pretty common, along with a comment about ignoring db.RowMutation.bin modification, which I've done locally: --- cut here --- # C* build/ src/gen-java/ src/resources/org/apache/cassandra/config/ # gitignore doesn't help with modified files - you may wish to: # git update-index --assume-unchanged test/data/serialization/2.0/db.RowMutation.bin # to undo: # git update-index --no-assume-unchanged test/data/serialization/2.0/db.RowMutation.bin # Intellij .idea/ *.iml *.ipr *.iws # Eclipse .classpath .project .metadata .settings/ local.properties # Cscope cscope.* # General *.pyc *~ *.bak *.swp *.tmp .DS_Store --- cut here --- -- Kind regards, Michael On 12/19/2013 04:23 PM, Oscar Bonilla wrote: The first thing I did when I forked the Cassandra repo was add a .gitignore: --- cut here --- .classpath .idea/ .project build/ src/gen-java/ cassandra.iml *.pyc cscope.* *.swp *~ src/resources/org/apache/cassandra/config/ --- cut here --- On Dec 19, 2013, at 2:16 PM, Jonathan Ellis wrote: I can't think of any. On Sat, Dec 14, 2013 at 11:14 AM, Michael Shuler wrote: On 12/13/2013 11:28 PM, graham sanderson wrote: This seemed to get introduced (by mistake?) in ef33f9543 Would there be any issues with adding a .gitignore to the repository? I could work one up. -- Kind regards, Michael -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Could .gitignore be added?
Your missing netbeans includes. I also include the following for anything java related. .*.swo Thumbs.db # Maven and other build system/IDE artifacts bin build out/* target/* # Netbeans nb-configuration.xml nbactions.xml nbproject On 20 Dec 2013, at 10:42 am, Michael Shuler wrote: > How about this for a .gitignore? I mixed in Oscar's, CASSANDRA-4899, a few > more general ones which are pretty common, along with a comment about > ignoring db.RowMutation.bin modification, which I've done locally: > > --- cut here --- > # C* > build/ > src/gen-java/ > src/resources/org/apache/cassandra/config/ > > # gitignore doesn't help with modified files - you may wish to: > # git update-index --assume-unchanged > test/data/serialization/2.0/db.RowMutation.bin > # to undo: > # git update-index --no-assume-unchanged > test/data/serialization/2.0/db.RowMutation.bin > > # Intellij > .idea/ > *.iml > *.ipr > *.iws > > # Eclipse > .classpath > .project > .metadata > .settings/ > local.properties > > # Cscope > cscope.* > > # General > *.pyc > *~ > *.bak > *.swp > *.tmp > .DS_Store > --- cut here --- > > -- > Kind regards, > Michael > > On 12/19/2013 04:23 PM, Oscar Bonilla wrote: >> The first thing I did when I forked the Cassandra repo was add a .gitignore: >> >> --- cut here --- >> .classpath >> .idea/ >> .project >> build/ >> src/gen-java/ >> cassandra.iml >> *.pyc >> cscope.* >> *.swp >> *~ >> src/resources/org/apache/cassandra/config/ >> --- cut here --- >> >> >> On Dec 19, 2013, at 2:16 PM, Jonathan Ellis wrote: >> >>> I can't think of any. >>> >>> On Sat, Dec 14, 2013 at 11:14 AM, Michael Shuler >>> wrote: On 12/13/2013 11:28 PM, graham sanderson wrote: > > This seemed to get introduced (by mistake?) in ef33f9543 Would there be any issues with adding a .gitignore to the repository? I could work one up. -- Kind regards, Michael >>> >>> >>> >>> -- >>> Jonathan Ellis >>> Project Chair, Apache Cassandra >>> co-founder, http://www.datastax.com >>> @spyced >> smime.p7s Description: S/MIME cryptographic signature
Re: Could .gitignore be added?
On 12/19/2013 05:46 PM, Jacob Rhoden wrote: Your missing netbeans includes. I also include the following for anything java related. .*.swo Thumbs.db Added. # Maven and other build system/IDE artifacts bin build out/* target/* We can't exclude bin/, since it's under revision control and build/ is already excluded. # Netbeans nb-configuration.xml nbactions.xml nbproject Added with a couple other typical netbeans dirs. --- snip --- # C* build/ src/gen-java/ src/resources/org/apache/cassandra/config/ # gitignore doesn't help with modified files - you may wish to: # git update-index --assume-unchanged test/data/serialization/2.0/db.RowMutation.bin # to undo: # git update-index --no-assume-unchanged test/data/serialization/2.0/db.RowMutation.bin # IntelliJ .idea/ *.iml *.ipr *.iws # Eclipse .classpath .project .metadata .settings/ local.properties # Cscope cscope.* # NetBeans nbbuild/ nbdist/ nbproject/ nb-configuration.xml nbactions.xml # Maven, etc. out/ target/ # General *.pyc *~ *.bak *.sw[o,p] *.tmp .DS_Store Thumbs.db --- snip --- -- Kind regards, Michael
