and what if your analyzer needs a third-party library (or two)? i mean this isn't unique to analyzers, if something changes/bug is fixed in the guts of some query/scorer that affects scoring in the slightest then thats a potential issue too, right?
for a big index burying a result deep is effectively the same as the stopword example... On Thu, May 21, 2009 at 5:27 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > On Thu, May 21, 2009 at 5:19 PM, Earwin Burrfoot <ear...@gmail.com> wrote: > >> Why not store an "actsAs" in the index, just for the changes that > >> affect what's in the index? Ie the index records the > >> version that created it, and by default TokenStreams emulate their > >> behavior as of that version? > > > > Because you don't always have access to index at the time you create > > your TokenStreams? > > Such places would have to pass in their own actsAs when they ask the > Analyzer for the tokenStream? > > Ie, the benefit of this approach vs the single global default is it'd > be per-instance. > > Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > -- Robert Muir rcm...@gmail.com
