lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wettin (JIRA)" <>
Subject [jira] Updated: (LUCENE-1380) Patch for ShingleFilter.enablePositions
Date Mon, 22 Sep 2008 15:16:44 GMT


Karl Wettin updated LUCENE-1380:

    Lucene Fields: [New, Patch Available]  (was: [Patch Available, New])
         Assignee:     (was: Karl Wettin)

I'm unassigning myself from this issue as there are so many votes and I consider it a hack
to add a change whos soul purpose is to change the behavior of a query parser and I don't
think such a thing should be committed. I think the focus should be on the query parser and
I understand that is a lot more work than modifying the shingle filter. If you really want
to do this change is this layer I suggest that you seperate out this feature to a new filter
that modify the position increment.

> Patch for ShingleFilter.enablePositions
> ---------------------------------------
>                 Key: LUCENE-1380
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/analyzers
>            Reporter: Mck SembWever
>            Priority: Trivial
>         Attachments: LUCENE-1380.patch, LUCENE-1380.patch
> Make it possible for *all* words and shingles to be placed at the same position, that
is for _all_ shingles (and unigrams if included) to be treated as synonyms of each other.
> Today the shingles generated are synonyms only to the first term in the shingle.
> For example the query "abcd efgh ijkl" results in:
>    ("abcd" "abcd efgh" "abcd efgh ijkl") ("efgh" efgh ijkl") ("ijkl")
> where "abcd efgh" and "abcd efgh ijkl" are synonyms of "abcd", and "efgh ijkl" is a synonym
of "efgh".
> There exists no way today to alter which token a particular shingle is a synonym for.
> This patch takes the first step in making it possible to make all shingles (and unigrams
if included) synonyms of each other.
> See for mailing list thread.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message