[DERBY-6596] LUCENESUPPORT routines should check for NULL arguments

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.11.1.1
• Fix Version/s: 10.11.1.1
• Component/s: Tools
• Assignee: Richard N. Hillegas
• Reporter: Knut Anders Hatlen
• Created: 03/Jun/14 14:48
• Updated: 10/Jun/14 08:12
• Resolved: 09/Jun/14 18:26

Description

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.

Issue Links

• relates to: DERBY-590 How to integrate Derby with Lucene API?