lucene-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <>
Subject Re: Factor out a standalone, shared analysis package for Nutch/Solr/Lucene?
Date Mon, 01 Mar 2010 18:38:53 GMT
Also, there still seems to be a misconception on what's being proposed

The proposal is to synchronize the development of Solr and Lucene.
Ie, a single dev list, single set of committers, synchronized

Everything else remains the same.  EG the release artifacts, user's
lists, web sites, branding, all remain separate.

How the source code is modularized is an orthogonal question.  We've
discussed breaking out things of Lucene's core, like query parser,
queries, analyzers into their own modules (and shipping their own
artifacts), which I still think makes great sense.  But it's
independent of synchronizing our development.


On Mon, Mar 1, 2010 at 1:03 PM, Michael McCandless
<> wrote:
> On Mon, Mar 1, 2010 at 12:58 PM, Marvin Humphrey <> wrote:
>> On Mon, Mar 01, 2010 at 12:44:02PM -0500, Michael McCandless wrote:
>>> But it goes beyond analyzers: I'd like to see other modules, now in
>>> Solr, eventually moved to Lucene, because they really are "core"
>>> functionality (eg facets, function (and other?) queries, spatial,
>>> maybe improvements to spellchecker/highlighter).
>> I disagree.  Those don't belong in core, and though they are all
>> great features, adding them to core constitutes "bloat", IMO.
>> The Query class belongs in core.  All those other modules should be
>> distributed as plugins, which could be used by Solr, Katta, Lucene,
>> whatever.
>> Note that this is orthogonal to whether Solr and Lucene merge or
>> diverge.
> I agree with this (sorry I wasn't clear).
> By "core functionality" I mean it should be a separate module (plugin)
> that direct Lucene users can use, not "whenever you install core
> Lucene you get these functions".
> Ie, users shouldn't have to install Solr to use facets with Lucene.
> Mike

View raw message