[VOTE] Release Mojo's Cassandra Maven Plugin 1.2.0-1
Hi, I'd like to release version 1.2.0-1 of Mojo's Cassandra Maven Plugin to sync up with the 1.2.0 release of Apache Cassandra. (a 1.2.1-1 will follow shortly after this release, but it should be possible to use the xpath://project/build/plugins/plugin/dependencies/dependency override of cassandra-server to use C* releases from the 1.2.x stream now that the link errors have been resolved, so that is less urgent) We solved 1 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121&version=18467 Staging Repository: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-013/ Site: http://mojo.codehaus.org/cassandra-maven-plugin/index.html SCM Tag: https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-1.2.0-1@17921 [ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse says it looks fine too. [ ] 0 Mehhh! like I care, I don't have any opinions either, I'd follow somebody else if only I could decide who [ ] -1 No! wait up there I have issues (in general like, ya know, and being a trouble-maker is only one of them) The vote is open for 72h and will succeed by lazy consensus. Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Cheers -Stephen P.S. In the interest of ensuring (more is) better testing, and as is now tradition for Mojo's Cassandra Maven Plugin, this vote is also open to any subscribers of the dev and u...@cassandra.apache.org mailing lists that want to test or use this plugin.
Question about Streaming
Hello, I am working on some modifications of Cassandra in an academic setting (research code, not for a class), and have a question regarding bulk streaming of data across the network (e.g. between nodes). Assume that I have some known set of key/column family combos that are known good/current on a node A, and known stale on a node B (forget about hinted handoff, etc. assume that this mechanism isn't being used). I can obviously bring these up to date on B by using anti-entropy repair, but this checks all the data and is CPU/time intensive. I have written code that brings this data up to date using the same mechanism as read repair (e.g. an item at a time), and this works fine, but is inefficient. What I am interested in doing is something in between. I want to bulk stream a series of updates between nodes like anti-entropy does, but I want the data that is sent to only be part of the specific itemized set that I am interested in. Is this something that is possible to do with the current code that exists, assuming that I already have code that keeps track of this set of stale data? Advice is much appreciated. Sincerely, Bill Katsak Rutgers University
Re: Question about Streaming
On Mon, Feb 4, 2013 at 2:11 PM, William Katsak wrote: > Hello, > > I am working on some modifications of Cassandra in an academic setting > (research code, not for a class), and have a question regarding bulk > streaming of data across the network (e.g. between nodes). > > Assume that I have some known set of key/column family combos that are known > good/current on a node A, and known stale on a node B (forget about hinted > handoff, etc. assume that this mechanism isn't being used). I can obviously > bring these up to date on B by using anti-entropy repair, but this checks > all the data and is CPU/time intensive. I have written code that brings this > data up to date using the same mechanism as read repair (e.g. an item at a > time), and this works fine, but is inefficient. > > What I am interested in doing is something in between. I want to bulk stream > a series of updates between nodes like anti-entropy does, but I want the > data that is sent to only be part of the specific itemized set that I am > interested in. If all you want is a ks/cf-specific version of 'nodetool rebuild' then that is a good place to start. -Brandon
