Re: Moving Cassandra's Debian repository from dist to bintray.com/apache
Hi Andrew, I'm happy to help. -Jake On Tue, Jan 6, 2015 at 2:19 PM, Andrew Bayer wrote: > Hi Cassandra team - > > So as you're probably aware, the Cassandra Debian packages currently on > dist need to be moved off there. The Infra team has been working on a > solution for that - we've got an organization for ASF on bintray.com, > which > can store and serve Debian repositories. We'd like to work with you all on > moving the existing packages over to bintray, and figuring out what needs > to be done to get a working process for you to post new Debian packages > going forward. Could someone from Cassandra (or some set of someones) be > available to work with us on this? Thanks! > > A. >
Re: Moving Cassandra's Debian repository from dist to bintray.com/apache
Great! So to start, can you give us a sense of what your needs for the repo are? What are you putting in it? Are you splitting it up by distro at all or just putting new versions of Cassandra in each time? A. On Wed, Jan 7, 2015 at 7:15 AM, Jake Luciani wrote: > Hi Andrew, > > I'm happy to help. > > -Jake > > On Tue, Jan 6, 2015 at 2:19 PM, Andrew Bayer wrote: > >> Hi Cassandra team - >> >> So as you're probably aware, the Cassandra Debian packages currently on >> dist need to be moved off there. The Infra team has been working on a >> solution for that - we've got an organization for ASF on bintray.com, >> which >> can store and serve Debian repositories. We'd like to work with you all on >> moving the existing packages over to bintray, and figuring out what needs >> to be done to get a working process for you to post new Debian packages >> going forward. Could someone from Cassandra (or some set of someones) be >> available to work with us on this? Thanks! >> >> A. >> > >
Re: Moving Cassandra's Debian repository from dist to bintray.com/apache
We have a distr per minor version. You can see them here (we only currently use the last 3 major releases 21x, 20x and 12x) you can see them here https://dist.apache.org/repos/dist/release/cassandra/debian/dists/ The release managers have a local repo with our reprepro settings. We deploy the artifact and export locally then copy the whole thing over to the apache dist server. Here is the relevant section of the release script https://github.com/tjake/cassandra-release/blob/master/finish_release.sh#L161 As our wiki shows, users add the maintainer keys and the specific dist they want https://wiki.apache.org/cassandra/DebianPackaging Ideally, we can redirect the existing location to the new one but I'm not sure if that's possible. How can we replicate this setup with bintray? -Jake On Wed, Jan 7, 2015 at 12:41 PM, Andrew Bayer wrote: > Great! So to start, can you give us a sense of what your needs for the > repo are? What are you putting in it? Are you splitting it up by distro at > all or just putting new versions of Cassandra in each time? > > A. > > On Wed, Jan 7, 2015 at 7:15 AM, Jake Luciani wrote: > >> Hi Andrew, >> >> I'm happy to help. >> >> -Jake >> >> On Tue, Jan 6, 2015 at 2:19 PM, Andrew Bayer wrote: >> >>> Hi Cassandra team - >>> >>> So as you're probably aware, the Cassandra Debian packages currently on >>> dist need to be moved off there. The Infra team has been working on a >>> solution for that - we've got an organization for ASF on bintray.com, >>> which >>> can store and serve Debian repositories. We'd like to work with you all >>> on >>> moving the existing packages over to bintray, and figuring out what needs >>> to be done to get a working process for you to post new Debian packages >>> going forward. Could someone from Cassandra (or some set of someones) be >>> available to work with us on this? Thanks! >>> >>> A. >>> >> >> >
Re: Moving Cassandra's Debian repository from dist to bintray.com/apache
See https://bintray.com/docs/api/#_debian_upload for how to upload/sign artifacts with the Bintray API. Your release managers will need to get accounts on Bintray and then open INFRA tickets to get added to the Cassandra team in the Apache org there, at which point you'll have full admin rights over the cassandra repo there. If you want to start playing with it, go ahead and create an account and let me know the username so I can invite/add you. reprepro isn't relevant here - the Bintray Debian repos don't support the full range of reprepro's functionality by a long shot, but for what you're doing, I don't think you need anything that's not available through the Bintray API. Alternatively, if that turns out to not work for you, you can use a generic repo that allows you to just upload files/directories, so you could keep doing what you're doing now but upload to Bintray rather than dist. Others on the Infra team will know for sure, but I'm pretty confident that a redirect from dist to bintray is feasible. A. On Wed, Jan 7, 2015 at 10:17 AM, Jake Luciani wrote: > We have a distr per minor version. You can see them here (we only > currently use the last 3 major releases 21x, 20x and 12x) you can see them > here https://dist.apache.org/repos/dist/release/cassandra/debian/dists/ > > The release managers have a local repo with our reprepro settings. We > deploy the artifact and export locally then copy the whole thing over to > the apache dist server. > Here is the relevant section of the release script > https://github.com/tjake/cassandra-release/blob/master/finish_release.sh#L161 > > As our wiki shows, users add the maintainer keys and the specific dist > they want > https://wiki.apache.org/cassandra/DebianPackaging > > Ideally, we can redirect the existing location to the new one but I'm not > sure if that's possible. > > How can we replicate this setup with bintray? > > -Jake > > > On Wed, Jan 7, 2015 at 12:41 PM, Andrew Bayer > wrote: > >> Great! So to start, can you give us a sense of what your needs for the >> repo are? What are you putting in it? Are you splitting it up by distro at >> all or just putting new versions of Cassandra in each time? >> >> A. >> >> On Wed, Jan 7, 2015 at 7:15 AM, Jake Luciani wrote: >> >>> Hi Andrew, >>> >>> I'm happy to help. >>> >>> -Jake >>> >>> On Tue, Jan 6, 2015 at 2:19 PM, Andrew Bayer wrote: >>> Hi Cassandra team - So as you're probably aware, the Cassandra Debian packages currently on dist need to be moved off there. The Infra team has been working on a solution for that - we've got an organization for ASF on bintray.com, which can store and serve Debian repositories. We'd like to work with you all on moving the existing packages over to bintray, and figuring out what needs to be done to get a working process for you to post new Debian packages going forward. Could someone from Cassandra (or some set of someones) be available to work with us on this? Thanks! A. >>> >>> >> >
Is it possible to delete columns or row using CQLSSTableWriter?
CQLSSTableWriter only accepts an INSERT or UPDATE statement. I'm wondering whether make it accept DELETE statement. I need to update my cassandra table with a lot of data everyday. * I may need to delete a row (given the partition key) * I may need to delete some columns. For example, there are 20 rows for a primary key before loading, the new load may have 10 rows only. Because CQLSSTableWriter will write into a blank table, will DELETE put a tombstone in the table so that the row in the server will be deleted after bulk loading? Thanks.
How to bulkload into a specific data center?
I set up two virtual data centers, one for analytics and one for REST service. The analytics data center sits top on Hadoop cluster. I want to bulk load my ETL results into the analytics data center so that the REST service won't have the heavy load. I'm using CQLTableInputFormat in my Spark Application, and I gave the nodes in analytics data center as Intialial address. However, I found my jobs were connecting to the REST service data center. How can I specify the data center?
