@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Using User Defined Functions in UPDATE queries
On Fri, Mar 11, 2016 at 5:09 PM, Kim Liu
mailto:k...@edgewaternetworks.com>> wrote:
Just for sake of clarification, then, what is the use-ca
Just for sake of clarification, then, what is the use-case for having UDFs in
an UPDATE?
If they cannot read data from the data store, then all of the parameters to the
UDF must be supplied by the client, correct?
If the client has all the parameters, the client could perform the equivalent
of
It does sounds like the use of UDF in UPDATE is in an ambiguous state at the
moment, then. The document grammar says they can’t be used, but the document
examples say they can, and the server will execute them, but it can’t execute
them in a useful way (i.e. no row supplied data.)
So essential
Um, I’m not entirely sure how I misread it, since this was copy-pasted from the
document:
UPDATE atable SET col = some_function(?) …;
So the document examples certainly seem to support the use of UDF in UPDATE. I
suppose the document may be more erroneous in its writing than I in its
misread
n an UPDATE
would seem to make the most sense only if the row data could be accessed, since
it could be used to bypass the need for a SELECT by a client to read the values
and perform the operation on them before doing the UPDATE.
Thank you,
Kim Liu
Kim Liu
Sr. Software Engineer
k..
