"In case you decide to use an entire new index for the
autosuggestion, you
can potentially manage that on your own"
This refers to the fact that is possible to define an index just for
autocompletion.
You can model the document as you prefer in this additional index, defining
the field types tha
Alessandro, thanks for your reply.
What do you mean by "In case you decide to use an entire new index for the
autosuggestion, you
can potentially manage that on your own".
Is this duplicate issue a problem with the DocumentDictionaryFactory?
--
Sent from: http://lucene.472066.n3.nabble.com/S
Hi Ruby,
I partecipated at the discussion at the time,
It's definitely still open.
It's on my long TO DO list, I hope I will be able to contribute a solution
sooner or later.
In case you decide to use an entire new index for the autosuggestion, you
can potentially manage that on your own.
But out
Yes, Id is an unique field in my schema.
I found following Jira issue:
https://issues.apache.org/jira/browse/LUCENE-6336
It looks related to me. It does not mention that it was fixed. Is it fixed
in Solr 6.1? I'm using Solr 6.1
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068
yes, id is an unique field.
I found following issue in Jira:
https://issues.apache.org/jira/browse/LUCENE-6336
It says affected versions are 4.10.3, 5.0. I'm using Solr 6.1 and seeing
this issue.
You can recreate it by indexing those documents I shared and querying.
--
Sent from: http://lucen
Is "id" the actual in your schema? If you indexed the same
document twice, the second one should overwrite the first one so
getting two docs back with the same ID is strange.
Best,
Erick
On Tue, Nov 7, 2017 at 10:43 AM, ruby wrote:
> I'm trying to enable phrase suggestion in my application by u
