Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 31 Oct 2012 12:03:11 +0000 (UTC)
From: "Oliver Christ (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <100671354.49954.1351684992313.JavaMail.jiratomcat@arcas>
In-Reply-To: <808905414.49944.1351684513782.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (LUCENE-4516) Suggesters: allow to associate a
 user-specified key (int) with a string
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/LUCENE-4516?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Christ updated LUCENE-4516:
----------------------------------

    Priority: Minor  (was: Major)
   =20
> Suggesters: allow to associate a user-specified key (int) with a string
> -----------------------------------------------------------------------
>
>                 Key: LUCENE-4516
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4516
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: core/FSTs
>            Reporter: Oliver Christ
>            Priority: Minor
>
> As a user, I'd like to associate a =E2=80=9Cforeign key=E2=80=9D with a s=
tring (rather: final node) in the suggester index (in addition to the rank)=
. For example, I=E2=80=99d like to add =E2=80=9CLucene in Action=E2=80=9D w=
ith key 1933988177 (the ISBN) and some rank to a WFST or AnalyzingSuggester=
. A completion would return the completed string and the key associated wit=
h each entry (i.e. final nodes get a =E2=80=9Ckey=E2=80=9D field (int), whi=
ch is returned in the LookupResult). That foreign key could also be used fo=
r fast de-duping (no more string/byte array comparisons).
> There may be workarounds for the =E2=80=9Cforeign key=E2=80=9D use case =
=E2=80=93it seems that lots of data structures would be affected by storing=
 a user-provided key with final nodes, which therefore may not be a viable =
path. It may be possible to encode the foreign key in the transducer=E2=80=
=99s output instead.
> *Discussion on java-user@lucene:*
> Mike McCandless:=20
> This is maybe the same idea as
> LUCENE-4491 ?  Could you simply stuff your ISBN onto the end of the sugge=
stion (ie enroll Lucene in
> Action|1933988177)?
> Dawid Weiss:
> Just remember that if your suffixes are unique then you'll be expanding t=
he automaton quite a bit (unique suffix paths).
> D.
> Mike:
> That's a good point... encoding into the FST's output may be better.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

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