Issue 121457 - Update Apache Lucene to version 3.6.x
Summary: Update Apache Lucene to version 3.6.x
Status: REOPENED
Alias: None
Product: Build Tools
Classification: Code
Component: external prerequisites (show other issues)
Version: 4.0.0-dev
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-10 18:47 UTC by Pedro Giffuni
Modified: 2014-03-12 10:13 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Pedro Giffuni 2012-12-10 18:47:57 UTC 
Lucene was recently updated to version 2.9.4.

We can bump Lucene up to version 3.6.x without trouble (tested on FreeBSD).
After some feedback from Steve Rowe from Apache Lucene, this would let us use new features in modern Lucene:

-  In HelpIndexerTool.java, for Japanese, we use CJKAnalyzer.  In Lucene version 3.6, a new Japanese morphological analyzer was added (the kuromoji module) - this would definitely do a better job of searching Japanese content.

- We use NIOFSDirectory, both when searching and indexing, but this is slow on Windows.  Here's a blog post about a better alternative (MMapDirectory) when using Lucene 3.1+ with 64-bit JVMs: <http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html> - it mentions the NIOFSDirectory issue too.  FSDirectory.open() knows about these issues and tries to pick the best option for you.

Implementing this the help system would be much faster.
Comment 1 Pedro Giffuni 2013-02-13 21:23:10 UTC 
This also requires adapting the long_path patch to apply for the upstream version.
Comment 2 Pedro Giffuni 2013-05-06 19:12:34 UTC 
There seems to be little interest in this.
Comment 3 Rob Weir 2013-05-07 19:06:48 UTC 
The issue is still valid, even if progress is slow.  I don't think it should be marked WONTFIX.

If you disagree, then please follow the process described in the wiki, and raise the issue on the dev mailing list:

http://wiki.openoffice.org/wiki/Issue_lifecycle

Thanks!

-Rob
Comment 4 jsc 2014-03-12 10:13:47 UTC 
we should directly analyze an update to the latest version 4.7