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
> >
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 Sci
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
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 :
> re
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 = [{
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-
+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:
>
