[VOTE PASSED] Release Apache Cassandra 1.2.15

[Sylvain Lebresne]

With 4 binding +1, 1 other +1 and no -1's the vote passed. I'll get the
artifacts published.


On Wed, Feb 5, 2014 at 3:17 PM, Gary Dusbabek  wrote:

> +1
>
>
> On Wed, Feb 5, 2014 at 2:23 AM, Sylvain Lebresne  >wrote:
>
> > We just released 1.2.14 but unfortunately it shipped with a relatively
> > serious
> > regression: https://issues.apache.org/jira/browse/CASSANDRA-6648. That
> > regression has been fixed, but we need to get that fix to users, so I
> > propose
> > the following artifacts for release as 1.2.15. As there has been little
> > changes
> > since 1.2.14 (outside the fix for #6648) and since it would be best to
> get
> > this
> > fix to users sooner than later, we'll stick to an expedited 24h vote.
> >
> > sha1: 178e086f1aaa2744dfc8046c9abb0c62e8a65895
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.15-tentative
> > Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1004/org/apache/cassandra/apache-cassandra/1.2.15/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1004/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~slebresne/
> >
> > The vote will be open for 24 hours (longer if needed).
> >
> > [1]: http://goo.gl/AuCbcg (CHANGES.txt)
> > [2]: http://goo.gl/Fnaj65 (NEWS.txt)
> >
>

Re: "[applied]" column in ModificationStatement?

[Brian O'Neill]

Thanks Jonathan.  
It feels a little weird, but that will work.

Not a big deal, but maybe we could include a wasApplied() method on the
ResultSet in the future that would insulate clients from the ResultSet
schema/column name.

-brian


---
Brian O'Neill
Chief Technology Officer

Health Market Science
The Science of Better Results
2700 Horizon Drive • King of Prussia, PA • 19406
M: 215.588.6024 • @boneill42   •
healthmarketscience.com

This information transmitted in this email message is for the intended
recipient only and may contain confidential and/or privileged material. If
you received this email in error and are not the intended recipient, or
the person responsible to deliver it to the intended recipient, please
contact the sender at the email above and delete this email and any
attachments and destroy any copies thereof. Any review, retransmission,
dissemination, copying or other use of, or taking any action in reliance
upon, this information by persons or entities other than the intended
recipient is strictly prohibited.
 






On 2/6/14, 2:58 PM, "Jonathan Ellis"  wrote:

>In Cassandra, it's ModificationStatement.CAS_RESULT_COLUMN.text
>
>On Thu, Feb 6, 2014 at 10:22 AM, Brian O'Neill 
>wrote:
>> Silly questionŠ
>>
>> Using the CQL driver for conditional updates, I¹m looking into the
>>ResultSet
>> that comes back:
>> for (ColumnDefinitions.Definition definition :
>> results.getColumnDefinitions().asList()) {
>> for (Row row : results.all()) {
>> LOG.debug("UPDATE APPLIED = [{}]=[{}]",
>> definition.getName(), row.getBool(definition.getName()));
>> }
>> }
>>
>> I noticed that the ResultSet of a conditional update contains a column
>> ³[applied]², with a boolean indicating whether or not the update was
>> applied.
>>
>> I assume this column name comes from:
>> 
>>src/java/org/apache/cassandra/cql3/statements/ModificationStatement.java:
>>50
>>private static final ColumnIdentifier CAS_RESULT_COLUMN = new
>> ColumnIdentifier("[applied]", false);
>>
>> Does it make sense to expose this column name as a String constant
>> somewhere?
>> Either in the CQL java-driver, or Cassandra itself?
>>
>> -brian
>>
>> ---
>> Brian O'Neill
>> Chief Technology Officer
>>
>>
>> Health Market Science
>> The Science of Better Results
>> 2700 Horizon Drive € King of Prussia, PA € 19406
>> M: 215.588.6024 € @boneill42    €
>> healthmarketscience.com
>>
>>
>> This information transmitted in this email message is for the intended
>> recipient only and may contain confidential and/or privileged material.
>>If
>> you received this email in error and are not the intended recipient, or
>>the
>> person responsible to deliver it to the intended recipient, please
>>contact
>> the sender at the email above and delete this email and any attachments
>>and
>> destroy any copies thereof. Any review, retransmission, dissemination,
>> copying or other use of, or taking any action in reliance upon, this
>> information by persons or entities other than the intended recipient is
>> strictly prohibited.
>>
>>
>>
>
>
>
>-- 
>Jonathan Ellis
>Project Chair, Apache Cassandra
>co-founder, http://www.datastax.com
>@spyced

Error reporting

[graham sanderson]

I’ve seen a few JIRA issues here and there, but haven’t heard much about any 
goal towards more context in error reporting. For almost all of the errors we 
see in production, it would be useful to include KS/CF in the error (and from 
the code that information is available in most cases). We have a bunch of 
different apps using Cassandra in different ways, and so knowing where the 
errors are occurring (which isn’t obvious from the logs) would help us a lot, 
because a) it is currently hard to distinguish between a possible application 
problem or Cassandra problem, and b) currently we have other authoritative data 
sources upstream for many things, and could simply blow away problematic 
keyspaces/tables

smime.p7s
Description: S/MIME cryptographic signature

Re: "[applied]" column in ModificationStatement?

[Jonathan Ellis]

In Cassandra, it's ModificationStatement.CAS_RESULT_COLUMN.text

On Thu, Feb 6, 2014 at 10:22 AM, Brian O'Neill  wrote:
> Silly questionŠ
>
> Using the CQL driver for conditional updates, I¹m looking into the ResultSet
> that comes back:
> for (ColumnDefinitions.Definition definition :
> results.getColumnDefinitions().asList()) {
> for (Row row : results.all()) {
> LOG.debug("UPDATE APPLIED = [{}]=[{}]",
> definition.getName(), row.getBool(definition.getName()));
> }
> }
>
> I noticed that the ResultSet of a conditional update contains a column
> ³[applied]², with a boolean indicating whether or not the update was
> applied.
>
> I assume this column name comes from:
> src/java/org/apache/cassandra/cql3/statements/ModificationStatement.java:50
>private static final ColumnIdentifier CAS_RESULT_COLUMN = new
> ColumnIdentifier("[applied]", false);
>
> Does it make sense to expose this column name as a String constant
> somewhere?
> Either in the CQL java-driver, or Cassandra itself?
>
> -brian
>
> ---
> Brian O'Neill
> Chief Technology Officer
>
>
> Health Market Science
> The Science of Better Results
> 2700 Horizon Drive € King of Prussia, PA € 19406
> M: 215.588.6024 € @boneill42    €
> healthmarketscience.com
>
>
> This information transmitted in this email message is for the intended
> recipient only and may contain confidential and/or privileged material. If
> you received this email in error and are not the intended recipient, or the
> person responsible to deliver it to the intended recipient, please contact
> the sender at the email above and delete this email and any attachments and
> destroy any copies thereof. Any review, retransmission, dissemination,
> copying or other use of, or taking any action in reliance upon, this
> information by persons or entities other than the intended recipient is
> strictly prohibited.
>
>
>



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

"[applied]" column in ModificationStatement?

[Brian O'Neill]

Silly questionŠ

Using the CQL driver for conditional updates, I¹m looking into the ResultSet
that comes back:
for (ColumnDefinitions.Definition definition :
results.getColumnDefinitions().asList()) {
for (Row row : results.all()) {
LOG.debug("UPDATE APPLIED = [{}]=[{}]",
definition.getName(), row.getBool(definition.getName()));
}
}

I noticed that the ResultSet of a conditional update contains a column
³[applied]², with a boolean indicating whether or not the update was
applied.

I assume this column name comes from:
src/java/org/apache/cassandra/cql3/statements/ModificationStatement.java:50
   private static final ColumnIdentifier CAS_RESULT_COLUMN = new
ColumnIdentifier("[applied]", false);

Does it make sense to expose this column name as a String constant
somewhere? 
Either in the CQL java-driver, or Cassandra itself?

-brian

---
Brian O'Neill
Chief Technology Officer


Health Market Science
The Science of Better Results
2700 Horizon Drive € King of Prussia, PA € 19406
M: 215.588.6024 € @boneill42    €
healthmarketscience.com


This information transmitted in this email message is for the intended
recipient only and may contain confidential and/or privileged material. If
you received this email in error and are not the intended recipient, or the
person responsible to deliver it to the intended recipient, please contact
the sender at the email above and delete this email and any attachments and
destroy any copies thereof. Any review, retransmission, dissemination,
copying or other use of, or taking any action in reliance upon, this
information by persons or entities other than the intended recipient is
strictly prohibited.
 

[VOTE PASSED] Release Apache Cassandra 2.0.5 (Strike 3)

[Sylvain Lebresne]

With 4 binding +1's, 1 other +1 and no -1's, the vote passes. I'll get the
artifact published.


On Thu, Feb 6, 2014 at 2:06 PM, Brandon Williams  wrote:

> +1
> On Feb 5, 2014 3:50 AM, "Sylvain Lebresne"  wrote:
>
> > As said while closing the previous vote, we needed to re-roll for
> > CASSANDRA-6648, so I propose the following artifacts for release as
> 2.0.5.
> > I also propose an expedited 24h vote.
> >
> > sha1: 29670eb6692f239a3e9b0db05f2d5a1b5d4eb8b0
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.5-tentative
> > Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1005/org/apache/cassandra/apache-cassandra/2.0.5/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1005/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~slebresne/
> >
> > The vote will be open for 24 hours (longer if needed).
> >
> > [1]: http://goo.gl/B6rgA6 (CHANGES.txt)
> > [2]: http://goo.gl/5qaw5i (NEWS.txt)
> >
>

Re: [VOTE] Release Apache Cassandra 2.0.5 (Strike 3)

[Brandon Williams]

+1
On Feb 5, 2014 3:50 AM, "Sylvain Lebresne"  wrote:

> As said while closing the previous vote, we needed to re-roll for
> CASSANDRA-6648, so I propose the following artifacts for release as 2.0.5.
> I also propose an expedited 24h vote.
>
> sha1: 29670eb6692f239a3e9b0db05f2d5a1b5d4eb8b0
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.5-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1005/org/apache/cassandra/apache-cassandra/2.0.5/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1005/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 24 hours (longer if needed).
>
> [1]: http://goo.gl/B6rgA6 (CHANGES.txt)
> [2]: http://goo.gl/5qaw5i (NEWS.txt)
>