You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/03/27 17:59:27 UTC
[jira] [Comment Edited] (DERBY-590) How to integrate Derby with
Lucene API?
[ https://issues.apache.org/jira/browse/DERBY-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949581#comment-13949581 ]
Rick Hillegas edited comment on DERBY-590 at 3/27/14 4:59 PM:
--------------------------------------------------------------
Hi Mike,
The modular separation you want is largely observed by the Lucene plugin right now. The exceptions are:
o org.apache.derby.iapi.sql.dictionary.OptionalTool is referenced because the plugin implements this interface. Now that we have agreement on a source code tree for optional tools, this interface could probably be moved over there and perhaps eventually exposed in the public api.
o org.apache.derby.iapi.util.IdUtil is referenced because the plugin needs the identifier normalization logic from IdUtil in order to convert string arguments into SQL identifiers and avoid SQL injection attacks.
o org.apache.derby.iapi.error.StandardException and org.apache.derby.shared.common.reference.SQLState are referenced so that the plugin can construct localized SQLExceptions with SQLStates.
o org.apache.derby.iapi.sql.conn.ConnectionUtil and org.apache.derby.iapi.sql.conn.LanguageConnectionContext are referenced in order to retrieve the database Locale.
o org.apache.derby.impl.jdbc.EmbedConnection is referenced in order to retrieve the location of the database directory. This is the only instance of the plugin reaching into the impl classes. I will see whether this can be improved.
Thanks,
-Rick
was (Author: rhillegas):
Hi Mike,
The modular separation you want is largely observed by the Lucene plugin right now. The exceptions are:
o org.apache.derby.iapi.sql.dictionary.OptionalTool is referenced because the plugin implements this interface.
o org.apache.derby.iapi.util.IdUtil is referenced because the plugin needs the identifier normalization logic from IdUtil in order to convert string arguments into SQL identifiers and avoid SQL injection attacks.
o org.apache.derby.iapi.error.StandardException and org.apache.derby.shared.common.reference.SQLState are referenced so that the plugin can construct localized SQLExceptions with SQLStates.
o org.apache.derby.iapi.sql.conn.ConnectionUtil and org.apache.derby.iapi.sql.conn.LanguageConnectionContext are referenced in order to retrieve the database Locale.
o org.apache.derby.impl.jdbc.EmbedConnection is referenced in order to retrieve the location of the database directory. This is the only instance of the plugin reaching into the impl classes. I will see whether this can be improved.
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, derby-590-05-aa-accessDeclaredMembers.diff, derby-590-06-aa-suppressAccessChecks.diff, derby-590-07-aa-accessClassInPackage.sun.misc.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)