consistency level ALL?

I was wondering if there are users in this list using consistency level ALL and their reasons for doing so? For example, would the errors for deleting a financial transaction due to an error be reason enough to use consistency level of ALL? Are there other strategies people would use to avoid

Re: Returning an UDT from a user defined function (UDF)

;, fieldA); transformedValue.setString("field_b", "value b"); return transformedValue; '; On Thu, Apr 7, 2016 at 7:40 PM Henry M <henrymanm...@gmail.com> wrote: > I was wondering if it is possible to create an UDT and return it within a > user defined functio

Re: Mapping a continuous range to a discrete value

I had to do something similar (in my case it was an IN query)... I ended up writing hack in java to create a custom Expression and injecting into the RowFilter of a dummy secondary index (not advisable and very short term but it keeps my application code clean). I am keeping my eyes open for the

Returning an UDT from a user defined function (UDF)

I was wondering if it is possible to create an UDT and return it within a user defined function. I looked at this documentation http://docs.datastax.com/en/cql/3.3/cql/cql_using/useCreateUDF.html but the examples are only for basic types. This is my pseudo code I came up with... the part I think

Re: Large number of tombstones without delete or update

What is the reason for the tombstone for a brand new insert? Do the fields get written as a whole (both nulls and non-nulls? I understand the rationale for tombstones for deletes and updates but it does not make sense for an insert (I am trying to make sense of it). I understand Cassandra writes

Re: nulls in prepared statement & tombstones?

Thank you. It's probably not specific to prepared statements then and just a more general statement. That makes sense. On Tue, Mar 8, 2016 at 10:06 AM Steve Robenalt wrote: > Hi Henry, > > I would suspect that the tombstones are necessary to overwrite any > previous