[
https://issues.apache.org/jira/browse/DERBY-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947260#comment-13947260
]
Mike Matrigali commented on DERBY-590:
--------------------------------------
I see that the optional tool for lucene is being added to derby.jar. I
continue to believe that optional tools
should be optional to the jar classpath as well as the runtime loading of the
optional tool. Support specific
to lucene should to into a separate jar, either an derbyoptionallucene.jar (or
whatever would be a good name) or I would be ok for now to lump it into
derbytools.jar.
I would like to see a sustainable model where developers can make an unbounded
number of optional
tools avaliable for derby, but each one should not add to the weight of the
core derby.jar.
Also I would prefer that these tools be in a different project than the derby
server and the interfaces in
derby be enhanced so that is possible.
While I think the code being donated for the lucene integration looks
interesting, I think we need to be
clear about its functionality. I have not reviewed the code as I believed it
was going to exist as an OPTIONAL tool, not integrated into the product. Some
high level descriptions indicate that its indexes
are not transactional, which does not mesh well with default current derby
behavior.
I continue to hope that we can come up with a project or separate "demo" set of
jars for features like this
so that users can benefit from a shared development environment. But also so
that we can continue
to promote the stable core of the derby server with clear and clean interfaces
to allow the less supported
functions to work (user provided new functions, user provided optional tools,
...)
> 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, 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)
