Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 14 Apr 2015 08:35:12 +0000 (UTC)
From: "Robert Stupp (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12757935.1416995260000.79340.1429000512680@Atlassian.JIRA>
In-Reply-To: <JIRA.12757935.1416995260000@Atlassian.JIRA>
References: <JIRA.12757935.1416995260000@Atlassian.JIRA>
 <JIRA.12757935.1416995260399@arcas>
Subject: [jira] [Updated] (CASSANDRA-8374) Better support of null for UDF
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Stupp updated CASSANDRA-8374:
------------------------------------
    Attachment: 8473-4.txt

* Rebased branch
* Fix cqlsh completion ({{NON DETERMINISTIC}} was at wrong place)

> Better support of null for UDF
> ------------------------------
>
>                 Key: CASSANDRA-8374
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8374
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Robert Stupp
>              Labels: client-impacting, cql3.3, docs-impacting, udf
>             Fix For: 3.0
>
>         Attachments: 8374-3.txt, 8374-3.txt, 8473-1.txt, 8473-2.txt, 8473-4.txt
>
>
> Currently, every function needs to deal with it's argument potentially being {{null}}. There is very many case where that's just annoying, users should be able to define a function like:
> {noformat}
> CREATE FUNCTION addTwo(val int) RETURNS int LANGUAGE JAVA AS 'return val + 2;'
> {noformat}
> without having this crashing as soon as a column it's applied to doesn't a value for some rows (I'll note that this definition apparently cannot be compiled currently, which should be looked into).  
> In fact, I think that by default methods shouldn't have to care about {{null}} values: if the value is {{null}}, we should not call the method at all and return {{null}}. There is still methods that may explicitely want to handle {{null}} (to return a default value for instance), so maybe we can add an {{ALLOW NULLS}} to the creation syntax.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)