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-6600) Make the Lucene plugin use the database class path to resolve ANALYZERMAKERs and QUERYPARSERMAKERs
Date Thu, 05 Jun 2014 20:50:02 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rick Hillegas updated DERBY-6600:

    Attachment: derby-6600-01-aa-useDBclasspath.diff

Attaching derby-6600-01-aa-useDBclasspath.diff. This patch makes the Lucene plugin use the
database classoader in order to resolve references to custom Analyzers and QueryParsers. I
am running tests now.

Touches the following files:


M       java/engine/org/apache/derby/impl/services/reflect/JarLoader.java

Add the optional tools api package to the packages whose contents can be resolved by the database


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

Use the database class loader to resolve Analyzer and QueryParser classes.


M       java/testing/org/apache/derbyTesting/functionTests/tests/lang/myLuceneClasses.jar
M       java/testing/org/apache/derbyTesting/functionTests/tests/lang/luceneSupport.policy
M       java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneSupportPermsTest.java
M       java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneSuite.java
A       java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneJarLoadingTest.java

Add a regression test for using an Analyzer and a QueryParser in a jar file in the database.

> Make the Lucene plugin use the database class path to resolve ANALYZERMAKERs and QUERYPARSERMAKERs
> --------------------------------------------------------------------------------------------------
>                 Key: DERBY-6600
>                 URL: https://issues.apache.org/jira/browse/DERBY-6600
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-6600-01-aa-useDBclasspath.diff
> You get a ClassNotFoundException if you try to use an Analyzer or a QueryParser stored
in a jar file in the database. This is probably easy to fix: the class resolution needs to
use the database class loader.

This message was sent by Atlassian JIRA

View raw message