On 22 Jul 2019, at 11:32 am, Richard Walker wrote:
> I'm trying out the advice in the user guide
> (
> https://lucene.apache.org/solr/guide/8_1/highlighting.html#schema-options-and-performance-considerations
> )
> for using the unified highlighter.
>
> ...
> * "set storeOffsetsWithPositions to
Good to hear.
Joel Bernstein
http://joelsolr.blogspot.com/
On Sun, Jul 21, 2019 at 5:21 PM Ahmed Adel wrote:
> Yeah, it turned out to be related to the data. The “fetch” method works
> fine as you described, it’s just the data distribution that caused name
> field not to be fetched in a number
I'm trying out the advice in the user guide
(
https://lucene.apache.org/solr/guide/8_1/highlighting.html#schema-options-and-performance-considerations
)
for using the unified highlighter.
I saw the note:
"This is definitely the fastest option for highlighting
wildcard queries on large text field
Yeah, it turned out to be related to the data. The “fetch” method works
fine as you described, it’s just the data distribution that caused name
field not to be fetched in a number of responses. I tested it with two
other collections and it worked as expected as well. Thank you for your
help getting
Thanks for your reply Alex and Yogendra.
@Yogendra: I have tried with grouping but it did not work. I will recheck
again if I am missing somethin.
@Alex : Recommendations are some of the products that comes from Solr.
Here is the scenario:
1) We get 100 products from Solr on product listing pag
So, if the recommendations are dynamic and come from outside Solr, why
do you need Solr to do anything at this stage? Sounds like the
original result list is where Solr responsibility ends.
You are not exposing Solr directly to the UI (you should not), so
whatever your middleware is, can be coded
