[
https://issues.apache.org/jira/browse/DERBY-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947296#comment-13947296
]
Rick Hillegas commented on DERBY-590:
-------------------------------------
I would support moving the Lucene plugin (and maybe other optional tools) into
a new derbyOptionalTools.jar. I continue to think that derbytools.jar is the
wrong place for this tool and some of the other optional tools. That is because
some of the optional tools (including the Lucene plugin) rely on engine
classes. derbytools.jar is supposed to hold tools which run fine on a client
machine without the engine jar.
Or maybe I misunderstand you. Are you suggesting that we crack open the Lucene
jars and put all their contents together with the plugin into a single
Lucene-specific jar? I think there will be problems with that approach.
Are you suggesting that we allocate a separate jar file to each optional tool?
Yes, please, I would like more discussion about the transactional behavior of
the Lucene plugin. Having another set of eyes on this would be very helpful. In
particular, I want to reduce the chance that users will experience deadlocks
between Lucene's locks and Derby's locks.
Thanks,
-Rick
> 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)
