lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3140) Backport FSTs to 3.x
Date Wed, 25 May 2011 16:05:48 GMT


Michael McCandless commented on LUCENE-3140:

bq. should we name the thing o.a.l.u.fst in trunk too?

Good idea... I'll do that w/ this issue.

bq. if FST is going to go into 3.x i think we should do a check to ensure all classes are

OK will do... there were a few missing (I'll fix trunk too).

bq. I think we should consider cutting Builder over to the new CharsRef?

I agree but I think we should do this separately?  I'll open an issue...

bq. we need to discuss things like autosuggest file formats, etc? At least so we are all on
the same page wrt any backwards policy...

Yes... maybe the same policy as the index?  So if you create auto-suggest FST in 3.x, 4.x's
suggest module will be able to read it / use it?

The FST itself is already versioned (uses CodecUtil to read/write the header) so we should
be all set to impl whatever policy we work out.

> Backport FSTs to 3.x
> --------------------
>                 Key: LUCENE-3140
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 3.2
>         Attachments: LUCENE-3140.patch

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message