For the japanese/english/french/german/dutch/russian/spanish/portuguese
with lots of searchable metadata dictionary that I am developping for
Android, I'm using a multi-field index that uses human input (a single
string) and i have to
USE 1 : guess/associate each term/range to one (or more) re
Hi,
It's great to see support for payloads in the suggesters - this is really
helpful, and pretty much addresses LUCENE-4516. Are there any plans to also
support them for WFSTs? We have some cases where we don't need the Analyzer's
capabilities (we look up the completion us
On Fri, Mar 1, 2013 at 11:16 AM, Oliver Christ wrote:
>
> I've seen some changes in trunk regarding the data format of Lucene's
> FST-based suggesters, and wonder whether the automata created by trunk
> builds/next Lucene version are/will be binary-compatible to the o
Hi,
I've seen some changes in trunk regarding the data format of Lucene's
FST-based suggesters, and wonder whether the automata created by trunk
builds/next Lucene version are/will be binary-compatible to the ones
created with the current release, or whether any magic versioning
candless.com]
Sent: Wednesday, January 16, 2013 5:38 PM
To: java-user@lucene.apache.org
Subject: Re: Suggesters: circumfix suggestions
Netflix also does this, eg type transla (you need an account).
I think it'd be good to somehow support this (Lucene's suggesters don't
today).
The
> Eg, you'd index only "boston", "red", "sox", "rumor" into the FST, and
> then have a separate search index with "boston red sox rumor" indexed
> as a document. If the user types "red so", then you run suggest on
> "red" and on "so", and then run a hmm MultiPhraseQuery for
> (red|redmond|reddit)
Netflix also does this, eg type transla (you need an account).
I think it'd be good to somehow support this (Lucene's suggesters don't today).
The first two approaches should conceptually work, but both will bloat
the FST (I'd be curious to know how much!).
Maybe anoth
Hi,
Has anyone tried to implement circumfix suggesters, where the suggestion
is a circumfix of the lookup string?
E.g. "sox rumor" suggests "boston red sox rumors" (try it on
google.com).
I think there are several of ways to implement this:
* Given
Thanks!
Mike McCandless
http://blog.mikemccandless.com
On Wed, Oct 31, 2012 at 8:16 AM, Oliver Christ wrote:
> Hi,
>
> I've added
>
> LUCENE-4516 - Suggesters: allow to associate a user-specified key (int)
> with a string
>
> LUCENE-4517 - Suggesters: allow to
Hi,
I've added
LUCENE-4516 - Suggesters: allow to associate a user-specified key (int)
with a string
LUCENE-4517 - Suggesters: allow to pass a user-defined predicate/filter
to the completion searcher
LUCENE-4518 - Suggesters: highlighting (explicit markup of user-typed
portions vs. gene
On Tue, Oct 30, 2012 at 3:52 PM, Dawid Weiss wrote:
>> https://issues.apache.org/jira/browse/LUCENE-4491 ? Could you simply
>> stuff your ISBN onto the end of the suggestion (ie enroll Lucene in
>> Action|1933988177)?
>
> Just remember that if your suffixes are unique then you'll be
> expanding
> https://issues.apache.org/jira/browse/LUCENE-4491 ? Could you simply
> stuff your ISBN onto the end of the suggestion (ie enroll Lucene in
> Action|1933988177)?
Just remember that if your suffixes are unique then you'll be
expanding the automaton quite a bit (unique suffix paths).
D.
Highlighting of the completed portions (i.e. explicit markup
> of user-provided vs. auto-completed portions of a completion).
Hmm could you do this in the app level? Ie, hilite the common prefix yourself?
> What's your take on the above? What would be the best way to achieve
> this?
able
path. It may be possible to encode the foreign key in the transducer's
output instead.
* Adding a filter/predicate to the AnalyzingSuggester is simple,
as TopNSearcher<> already uses acceptResult() to test whether some
completion should be added - that can be overridden in a
14 matches
Mail list logo
