Oh yes, I also use Spring Cache which works fine and I don't have to store
products in Lucene making index smaller and faster.
On Fri, 23 Sept 2022, 19:26 Stephane Passignat,
wrote:
> Hi
>
> I would don't store the original value. That's "just" an index. But store
> the value of your db identifi
Well, my bad is that I used wrong word. I'm not storing but just goving
keywords to analyzer. That was my mistake in writing. So far I don't index
exotic letters, but just normalized.
Additionally I put in index something like "Prod_3443" which is a product
ID for situation when specific product is
You don't need a server-side cache as the searchAfter value has all
the information, it is just your "current position".
For example if you are sorting by ID and you return IDs 1,2,3,4,5, the
searchAfter value is basically 5.
So when you query the next time with that searchAfter=5, it skips over
an
