[
https://issues.apache.org/jira/browse/DERBY-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025498#comment-14025498
]
ASF subversion and git services commented on DERBY-6596:
--------------------------------------------------------
Commit 1601465 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1601465 ]
DERBY-6596: Forbid null args to lucene support routines;
derby-6596-01-aa-checkNotNull.diff.
> 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)
