Thanks stack for helping committing this.
Out of curiosity - this lucene tool ( buildtableIndex) seems totally
tangential to hbase , albeit an useful tool for sure. Can this be in a
separate contrib to lessen the dependencies on the core hbase tree ?
Thoughts ?
On 1/11/10 2:30 PM, stack (JIRA) wrote:
[
https://issues.apache.org/jira/browse/HBASE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-2107.
--------------------------
Resolution: Fixed
Fix Version/s: 0.21.0
Committed.
Upgrading Lucene 2.2 to Lucene 3.0.0
-------------------------------------
Key: HBASE-2107
URL: https://issues.apache.org/jira/browse/HBASE-2107
Project: Hadoop HBase
Issue Type: Improvement
Reporter: Kay Kay
Fix For: 0.21.0
Attachments: HBASE-2107.patch, HBASE-2107.patch, HBASE-2107.patch
HBase has an utility to export columns as Lucene indices.
(o.a.h.hbase.mapreduce.BuildTableIndex ) .
This patch increases the version in libraries.properties and addresses some
deprecations towards moving it.
Rationale for upgradation:
====================
A lot has been happening in the Lucene since 2.2, with improved performance and
focus on NRT (Near Real Time search) happening recently. Hence - we need to
keep up with the same and make the utility publish indices for the new version.
Caveats:
=======
Index created by Lucene 3.0 is *not backward-compatible* with Lucene 2.2 code.
In other words - as part of this upgradation - indices need to be created all
over again and the library interacting with the index ( readers / searchers )
need to be upgraded to the new version as well.
