[DERBY-6731] Lucene VTI returns NULL for key if it is a BLOB

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.11.1.1
• Component/s: Tools
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Knut Anders Hatlen
• Created: 09/Sep/14 13:39
• Updated: 09/Sep/14 15:46

Description

ij> connect 'jdbc:derby:memory:db;create=true';
ij> call syscs_util.syscs_register_tool('luceneSupport', true);
0 rows inserted/updated/deleted
ij> create table t(b blob, c clob);
0 rows inserted/updated/deleted
ij> insert into t values (cast (x'cafe' as blob), 'hello');
1 row inserted/updated/deleted
ij> call lucenesupport.createindex('app', 't', 'c', null, 'b');
0 rows inserted/updated/deleted
ij> select * from table(t__c('hello', 10, null)) t;
B                                                                                                                               |DOCUMENTID |SCORE          
------------------------------------------------------------------------------------------------------------------------------------------------------------
NULL                                                                                                                            |0          |0.30685282     

1 row selected

I expected either that CREATEINDEX had failed with a message saying that a BLOB column could not be used as a key column, or that the Lucene VTI had returned a non-null value for column B.

Issue Links

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