[
https://issues.apache.org/jira/browse/CASSANDRA-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941941#comment-13941941
]
Sylvain Lebresne commented on CASSANDRA-6870:
---------------------------------------------
bq. I would suggest to differentiate a UDF which works like a mathamatical
function,from a UDTF. Trying to make them one uber-interface would probably
make said interface hard to implement.
Right, so we already have the code to handle "mathematical" functions. We just
haven't yet exposed a way for user to define their own function, but the code
for that is pretty generic. And while I would agree a interface for all type of
functions won't work, I'm pretty there is many common part still, they can
pretty sure have some common parts (extend some common interface), even if they
are slightly separate interface to account for their differences.
> Transform operation
> -------------------
>
> Key: CASSANDRA-6870
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6870
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Priority: Minor
>
> Compare and swap uses paxos to only update a value only if some criteria is
> met. If I understand correctly we should be able to use this feature to
> provide a wider variety of server side operations.
> For example inside a paxos transaction performing a slice and then using a
> function to manipulate the slice. You could accomplish features like append
> and increment this way without user needing to know the current value.
> I took a stab at doing this. I **think** I did it correctly. Comments welcome.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
