lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <mar...@rectangular.com>
Subject Re: Having a default constructor in Analyzers
Date Mon, 08 Feb 2010 00:47:28 GMT
DM Smith:

> Imagine that each index maintains a manifest of the toolchain for the index,
> which includes the version of each part of the chain. Since the index is
> created all at once, this probably is the same as the version of lucene.
> When the user searches the index the manifest is consulted to recreate the
> toolchain.

---->8 snip 8<----

> IIRC: This is something that Marvin has implemented in Lucy.

Yes.  QueryParser's constructor takes a Schema argument.  Furthermore, Schema
definitions are fully externalized and stored as JSON with the index itself.
So you can do stuff like this:

  IndexReader reader = IndexReader.open("/path/to/index");
  QueryParser qparser = new QueryParser(reader.getSchema());

We haven't got Version for our Analyzers yet, but it's planned.  I'm following
this discussion with interest to see how the deployment of Version plays out
with the user base.

However, Lucy's approach won't work for Lucene because Lucene allows you to
have fields with the same name and completely different semantics.

Marvin Humphrey



---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message