lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Updated] (LUCENE-3830) MappingCharFilter could be improved by switching to an FST.
Date Mon, 30 Apr 2012 17:03:48 GMT


Michael McCandless updated LUCENE-3830:

    Attachment: LUCENE-3830.patch

Patch; I think it's basically working.

I disallow empty string match to be added (this was accepted, but I think ignored, before),
so I had to fix a couple places that were doing that.

I also added another random test that separately (slowly) computes the output & corrected
offsets and then compares ... it's passing.

I still need to do a perf test.. does anyone have a "typical" set of mappings + content I
could use?  Else I'll try to come up with something...
> MappingCharFilter could be improved by switching to an FST.
> -----------------------------------------------------------
>                 Key: LUCENE-3830
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Dawid Weiss
>            Assignee: Michael McCandless
>            Priority: Minor
>              Labels: gsoc2012, lucene-gsoc-12
>             Fix For: 4.0
>         Attachments: LUCENE-3830.patch
> MappingCharFilter stores an overly complex tree-like structure for matching input patterns.
The input is a union of fixed strings mapped to a set of fixed strings; an fst matcher would
be ideal here and provide both memory and speed improvement I bet.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message