Absolutely!
Thanks man.
[]'s
Rafael
On Thu, Jul 2, 2015 at 12:42 PM, Alessandro Benedetti <
benedetti.ale...@gmail.com> wrote:
> That is what I was saying :)
> Hope it helps
>
> 2015-07-02 16:32 GMT+01:00 Rafael :
>
> > Just double checking:
> >
> > In my ruby backend I ask for (using the given
That is what I was saying :)
Hope it helps
2015-07-02 16:32 GMT+01:00 Rafael :
> Just double checking:
>
> In my ruby backend I ask for (using the given example) all suggested terms
> that starts with "J." , then I (probably) add all the terms to a Set, and
> then return the Set to the view. Righ
Just double checking:
In my ruby backend I ask for (using the given example) all suggested terms
that starts with "J." , then I (probably) add all the terms to a Set, and
then return the Set to the view. Right ?
[]'s
Rafael
On Thu, Jul 2, 2015 at 12:12 PM, Alessandro Benedetti <
benedetti.ale...
No, I was referring to the fact that a Suggester as a unit of information
manages simple terms which are identified simply by themselves.
What you need to do is tu sums some Ruby Datastructure that prevent the
duplicates to be inserted, and then offer the Suggestions from there.
Cheers
2015-07-0
Thanks, Alessandro!
Well, I'm using Ruby and the r-solr as a client library. I didn't get what
you said about term id. Do I have to create this field ? Or is it a "hidden
field" utilized by solr under the hood ?
[]'s
Rafael
On Thu, Jul 2, 2015 at 6:41 AM, Alessandro Benedetti <
benedetti.ale...@
Hi Rafael,
Your problem is clear and it has actually been explored few times in the
past.
I agree with you in a first instance.
A Suggester basic unit of information is a term. Not a document.
This means that actually it does not make a lot of sense to return
duplicates terms ( because they are co
