[
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-19-aa-cleanupAPI2.diff
Attaching derby-590-19-aa-cleanupAPI2.diff. This patch adds another parameter
to the query table function used by the plugin.
Lucene has a concept of a window's worth of results. The Lucene classes allow
you to process a series of windows of results by configuring two parameters:
1) The window size.
2) The score of the last document in the previous window.
Right now the plugin allows you to set 2). I think the plugin would be more
useful if you could set 1) as well. This would also make it easier to explain
how the plugin API maps onto Lucene concepts.
Technically, neither of these parameters are needed. That is because the user
can specify OFFSET and FETCH NEXT clauses to produce the same effect. However,
I think that supporting both of these parameters will make some families of
queries perform better.
This patch adds a windowSize parameter to the query table function.
Touches the following files:
-------------
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/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,
> 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)
