[
https://issues.apache.org/jira/browse/DERBY-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962810#comment-13962810
]
Knut Anders Hatlen commented on DERBY-590:
------------------------------------------
We might want to change LuceneSupport.sqlException(StandardException) to call
PublicAPI.wrapStandardException() instead of invoking the SQLException
constructor directly. The advantages are that the PublicAPI wrapper method will
use the correct subclass of SQLException, if appropriate, and it will also wrap
the exception in a way that's recognized by error handlers higher up, which
reduces the amount of additional wrapping.
For example, an exception currently reported like this
{noformat}
ij> call LuceneSupport.createIndex('T', 'titles', 'title', null);
ERROR 38000: The exception 'java.sql.SQLException: The schema, table or column
does not exist or the column is not a string type.' was thrown while evaluating
an expression.
ERROR 42XBA: The schema, table or column does not exist or the column is not a
string type.
{noformat}
will instead be reported like this
{noformat}
ij> call LuceneSupport.createIndex('T', 'titles', 'title', null);
ERROR 42XBA: The schema, table or column does not exist or the column is not a
string type.
{noformat}
> 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,
> derby-590-08-aa-omitLuceneFlag.diff,
> derby-590-09-aa-localeSensitiveAnalysis.diff,
> derby-590-10-aa-fixLocaleTest.diff, derby-590-11-aa-moveCode.diff,
> derby-590-12-aa-newJar.diff, derby-590-13-aa-indexViews.diff,
> derby-590-14-aa-coarseGrainedAuthorization.diff,
> derby-590-15-aa-requireHardUpgrade.diff,
> derby-590-16-aa-adjustUpgradeTest.diff,
> derby-590-17-aa-closeInputStreamOnPropertiesFile.diff,
> derby-590-18-aa-cleanupAPI.diff, derby-590-19-aa-cleanupAPI2.diff,
> derby-590-20-aa-customQueryParser.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)
