[
https://issues.apache.org/jira/browse/DERBY-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799278#comment-13799278
]
Andrew McIntyre commented on DERBY-590:
---------------------------------------
Attached patch sent to mailing list. ij script that can be used to demonstrate
the patch's features is here:
http://people.apache.org/~fuzzylogic/lucene_titles.sql
although this contains what might be considered copyrighted data, so this will
be removed and I'll try to replace it with a more appropriate dataset and
include it directly in the patch when I can find one that works well. As I
said, very rough, I basically just got it working. :-) Some things don't work
(the rankCutoff parameter in the query function doesn't do anything), it needs
formatting, comments, javadoc, tests, etc. etc.
Regarding Rick's comment on the dev list about further integration via the
parser, it seems like it would be pretty straightforward to go from the
procedure call in this patch to wiring the index creation into the sql grammar
by using the MySQL-ish: CREATE FULLTEXT INDEX INDEX_NAME ON SCHEMA.TABLE
(COLUMN)
> How to integrate Derby with Lucene API?
> ---------------------------------------
>
> Key: DERBY-590
> URL: https://issues.apache.org/jira/browse/DERBY-590
> Project: Derby
> Issue Type: Improvement
> Components: Documentation, SQL
> Reporter: Abhijeet Mahesh
> Labels: derby_triage10_11
> Attachments: lucene_demo.diff
>
>
> In order to use derby with lucene API what should be the steps to be taken?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
