db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-590) How to integrate Derby with Lucene API?
Date Sun, 06 Apr 2014 15:22:15 GMT

     [ 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-18-aa-cleanupAPI.diff

Attaching derby-590-18-aa-cleanupAPI.diff. This patch cleans up the plugin api by renaming
a column and a parameter. The patch also forbids name conflicts between user-supplied and
system-supplied column names.

While preparing to write a functional spec for the plugin, I tripped across some parts of
the api which need some tweaking so that users can understand the tool. This patch is the
first set of tweaks.

The existing plugin uses the term "rank" as a synonym for Lucene's concept of a "score". I
think it will be easier to explain the plugin if we stick to Lucene's terms. So this patch
renames the following:

o The "rank" column returned by LuceneQueryVTI has been renamed to "score".

o The "rankCutoff" argument to LuceneQueryVTI has been renamed to "scoreCeiling".

While I was in there, I changed the type of scoreCeiling from double to real so that it corresponds
with the type of score. I also added some logic to prevent users from creating a LuceneQueryVTI
which returns a data set with two columns named "documentID" or two columns named "score".


Touches the following files:

-------------

M       java/engine/org/apache/derby/loc/messages.xml
M       java/shared/org/apache/derby/shared/common/reference/SQLState.java

New error message.

-------------

M       java/optional/org/apache/derby/optional/lucene/LuceneQueryVTI.java
M       java/optional/org/apache/derby/optional/lucene/LuceneSupport.java

Rename columns and forbid name conflicts.

-------------

M       java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneCoarseAuthorizationTest.java
M       java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneSupportPermsTest.java

Adjust existing tests and add new test case for name conflicts.


> 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, 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)

Mime
View raw message