[
https://issues.apache.org/jira/browse/DERBY-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-590:
--------------------------------
Attachment: derby-590-20-aa-customQueryParser.diff
Attaching derby-590-20-aa-customQueryParser.diff. This patch adds another
parameter to the table function which performs the Lucene search. The new
argument is the name of a static, public method which creates a query parser.
Lucene lets you extend its query language or even replace its query language
with your own, custom language.
The table function relies on two classes for which Lucene supplies multiple
implementations:
1) Analyzer - This is the locale-specific logic which turns a block of text
into a series of indexable terms.
2) QueryParser - This is the application-specific logic for interpreting the
query string.
As of derby-590-09-aa-localeSensitiveAnalysis.diff, the user can supply their
own locale-specific Analyzer. As of this patch, the user can also supply their
own custom QueryParser for interpreting query strings.
Touches the following files:
-------------
M java/optional/org/apache/derby/optional/api/LuceneUtils.java
M java/optional/org/apache/derby/optional/lucene/LuceneQueryVTI.java
M java/optional/org/apache/derby/optional/lucene/LuceneSupport.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneCoarseAuthorizationTest.java
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/build.xml
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneSupportPermsTest.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneSupportTest.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneCollationTest.java
> 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: derby-590-01-ag-publicAccessToLuceneRoutines.diff,
> derby-590-01-ah-publicAccessToLuceneRoutines.diff,
> derby-590-01-am-publicAccessToLuceneRoutines.diff,
> derby-590-02-aa-cleanupFindbugsErrors.diff,
> derby-590-03-aa-removeTestingDiagnostic.diff,
> derby-590-04-aa-removeIDFromListIndexes.diff,
> derby-590-05-aa-accessDeclaredMembers.diff,
> derby-590-06-aa-suppressAccessChecks.diff,
> derby-590-07-aa-accessClassInPackage.sun.misc.diff,
> derby-590-08-aa-omitLuceneFlag.diff,
> derby-590-09-aa-localeSensitiveAnalysis.diff,
> derby-590-10-aa-fixLocaleTest.diff, derby-590-11-aa-moveCode.diff,
> derby-590-12-aa-newJar.diff, derby-590-13-aa-indexViews.diff,
> derby-590-14-aa-coarseGrainedAuthorization.diff,
> derby-590-15-aa-requireHardUpgrade.diff,
> derby-590-16-aa-adjustUpgradeTest.diff,
> derby-590-17-aa-closeInputStreamOnPropertiesFile.diff,
> derby-590-18-aa-cleanupAPI.diff, derby-590-19-aa-cleanupAPI2.diff,
> derby-590-20-aa-customQueryParser.diff, lucene_demo.diff, lucene_demo_2.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.2#6252)
