You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/06/09 20:27:02 UTC

[jira] [Resolved] (DERBY-6596) LUCENESUPPORT routines should check for NULL arguments

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

Rick Hillegas resolved DERBY-6596.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.11.0.0

> LUCENESUPPORT routines should check for NULL arguments
> ------------------------------------------------------
>
>                 Key: DERBY-6596
>                 URL: https://issues.apache.org/jira/browse/DERBY-6596
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 10.11.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Rick Hillegas
>            Priority: Minor
>             Fix For: 10.11.0.0
>
>         Attachments: derby-6596-01-aa-checkNotNull.diff
>
>
> When the LUCENESUPPORT routines are called with argument value NULL where a NULL is not allowed, they fail with NullPointerExceptions. Example:
> ij> call lucenesupport.createindex('app', 't', null, null);
> ERROR 38000: The exception 'java.lang.NullPointerException' was thrown while evaluating an expression.
> ERROR XJ001: Java exception: ': java.lang.NullPointerException'.
> Here, the third argument (the column name) cannot be NULL. It would be nicer if it raised an error that said that the argument couldn't be NULL, since a NullPointerException looks more like an internal error.



--
This message was sent by Atlassian JIRA
(v6.2#6252)