db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6600) Make the Lucene plugin use the database class path to resolve ANALYZERMAKERs and QUERYPARSERMAKERs
Date Fri, 06 Jun 2014 12:22:02 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019795#comment-14019795
] 

ASF subversion and git services commented on DERBY-6600:
--------------------------------------------------------

Commit 1600866 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1600866 ]

DERBY-6600: Make Derby resolve custom Lucene Analyzers and QueryParsers by using the database
classpath.

> 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
(v6.2#6252)

Mime
View raw message