Queries about global index feature

2015-01-16 Thread Ajaya Agrawal
Hi guys,

I have a few questions about the global index feature that's coming in
cassandra 3.0 . I’ve had a discussion about this with carlyeks and
belliottsmith and I have gone through the discussion in
https://issues.apache.org/jira/browse/CASSANDRA-6477. I have some followup
questions regarding this feature. Please provide your insights.


   -

   Is the index going to be a separate table behind the scenes? As a user
   what are the possibilities w.r.t. data in the main table and the index that
   I have to account for? E.g. I gather that data may be in the index but not
   main table. This is especially interesting to understand in the presence of
   failures.
   -

   Related to the above point: What about the cases where the consistency
   level is set to quorum or all?
   -

   Can global index be based on multiple columns? For e.g. in primary key I
   can have a partition key column and a clustering column. Can I do the same
   in global secondary index? If yes, then is it going to behave the same way
   as the composite primary key?
   -

   Can I create a GSI after creating a table and having some data in it?


Cheers,

Ajaya


Re: [VOTE] Release Apache Cassandra 2.0.12 (Second attempt)

2015-01-16 Thread Aleksey Yeschenko
Sorry for ruining it again, but we just found another regression in the 
unreleased 2.0.12.

https://issues.apache.org/jira/browse/CASSANDRA-8346 has a typo in calculating 
# of required LWT participants, essentially forcing ALL instead of QUORUM.

Anthony Cozzie found and fixed the issue in 
https://issues.apache.org/jira/browse/CASSANDRA-8640 (already committed).

We must re-roll.

-- 
AY

On January 15, 2015 at 5:17:45 PM, Aleksey Yeschenko (alek...@apache.org) wrote:

+1

-- 
AY

On January 15, 2015 at 5:14:30 PM, Jake Luciani (j...@apache.org) wrote:

I propose the following artifacts for release as 2.0.12.

sha1: 90780b550f39bc318567ac53f8e8e7d797697f16
Git: 
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.12-tentative
Artifacts: 
https://repository.apache.org/content/repositories/orgapachecassandra-1042/org/apache/cassandra/apache-cassandra/2.0.12/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1042/

The artifacts as well as the debian package are also available here:
http://people.apache.org/~jake

The vote will be open for 72 hours (longer if needed).

[1]: http://goo.gl/7JmQWg (CHANGES.txt)
[2]: http://goo.gl/bqxiFR (NEWS.txt)


Re: Moving Cassandra's Debian repository from dist to bintray.com/apache

2015-01-16 Thread Jake Luciani
Ok well I'm able to post artifacts however this still requires posting
my private key to bintray to have it signed.

I don't see how this is a viable solution since this requires us to
post our private keys to this service.
You mentioned there is a way to simply post our existing directories,
maybe that's what we should do...

On Thu, Jan 15, 2015 at 8:00 PM, Andrew Bayer  wrote:
> And an update!
>
> "Signing via API with transient key/pass just went live. You need to call
> the metadata calculation API for a (deb) repo, passing the subject to sign
> with, and api key and an optional passphrase, as described here."
>
> Lemme know how it works!
>
> A.
>
> On Thu, Jan 15, 2015 at 7:00 AM, Andrew Bayer 
> wrote:
>>
>> Sorry for not emailing - JFrog is investigating the work involved in
>> getting users able to sign organization Debian repository metadata. I'll
>> ping them for an update.
>>
>> A.
>>
>>
>> On Thursday, January 15, 2015, Jake Luciani  wrote:
>>>
>>> Any update?
>>>
>>> On Fri, Jan 9, 2015 at 12:53 PM, Andrew Bayer 
>>> wrote:
>>> > I'm investigating this now - will update when I have more information.
>>> >
>>> > A.
>>> >
>>> > On Fri, Jan 9, 2015 at 7:54 AM, Jake Luciani  wrote:
>>> >
>>> >> The docs seems to indicate signing happens at the organization level
>>> >>
>>> >>
>>> >>
>>> >> https://bintray.com/docs/usermanual/interacting/interacting_gpgsigningforbintrayorganizations.html
>>> >>
>>> >> Am I able to sign artifacts with my user GPG?  I'm not sure if
>>> >> everyone is comfortable uploading their private gpg key to bintray.
>>> >>
>>> >> On Wed, Jan 7, 2015 at 1:40 PM, Andrew Bayer 
>>> >> wrote:
>>> >> > 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
>>> >>

[VOTE] Release Apache Cassandra 2.0.12 (Third attempt)

2015-01-16 Thread Jake Luciani
Let's try again. I propose the following artifacts for release as 2.0.12.

sha1: ce207cba413381986324f2c8edad9e090e5be5b1
Git: 
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.12-tentative
Artifacts: 
https://repository.apache.org/content/repositories/orgapachecassandra-1043/org/apache/cassandra/apache-cassandra/2.0.12/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1043/

The artifacts as well as the debian package are also available here:
http://people.apache.org/~jake

The vote will be open for 72 hours (longer if needed).

[1]: http://goo.gl/7JmQWg (CHANGES.txt)
[2]: http://goo.gl/bqxiFR (NEWS.txt)


Re: [VOTE] Release Apache Cassandra 2.0.12 (Third attempt)

2015-01-16 Thread Jonathan Ellis
+1

On Fri, Jan 16, 2015 at 9:38 PM, Jake Luciani  wrote:
> Let's try again. I propose the following artifacts for release as 2.0.12.
>
> sha1: ce207cba413381986324f2c8edad9e090e5be5b1
> Git: 
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.12-tentative
> Artifacts: 
> https://repository.apache.org/content/repositories/orgapachecassandra-1043/org/apache/cassandra/apache-cassandra/2.0.12/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1043/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/7JmQWg (CHANGES.txt)
> [2]: http://goo.gl/bqxiFR (NEWS.txt)



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder, http://www.datastax.com
@spyced