Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
Low
Description
In order to use derby with lucene API what should be the steps to be taken?
Attachments
Attachments
Issue Links
- blocks
-
DERBY-6564 Document the experimental, optional LuceneSupport tool.
- Closed
- breaks
-
DERBY-6528 many nightly test failures following checkin of lucene work.
- Closed
- is blocked by
-
DERBY-472 Full Text Indexing / Full Text Search
- Closed
- is related to
-
DERBY-6731 Lucene VTI returns NULL for key if it is a BLOB
- Open
-
DERBY-6536 Errors in LuceneSupportTest on Windows platforms
- Closed
-
DERBY-6538 Error in LuceneSupportPermsTest.test_006_changeAnalyzer on windows
- Closed
-
DERBY-6539 Wrong rank value in LuceneSupportTest and LuceneSupportPermsTest
- Closed
-
DERBY-6544 Non-english locale flunks LuceneSupportTest
- Closed
-
DERBY-6597 LUCENESUPPORT.LISTINDEXES() fails with FileNotFoundException
- Closed
-
DERBY-6600 Make the Lucene plugin use the database class path to resolve ANALYZERMAKERs and QUERYPARSERMAKERs
- Closed
-
DERBY-6602 LuceneQueryVTI handles NULL key values inconsistently
- Closed
-
DERBY-6730 Cannot create a Lucene index if a key column's name is case-sensitive
- Closed
-
DERBY-6385 Make it possible to plug alternative parsers into Derby.
- Open
-
DERBY-6603 Make LuceneSupport.createOrRecreateIndex() write the index properties file once per indexing run
- Closed
-
DERBY-6596 LUCENESUPPORT routines should check for NULL arguments
- Closed
-
DERBY-6658 Update list of tested Lucene versions
- Closed
- relates to
-
LUCENE-5471 Classloader issues when running Lucene under a java SecurityManager
- Open