Hi,
Any of the above :)
If you don't care about minimizing network hops during indexing/search, you can
use a LB like HAProxy, NginX or some hardware product in front of your nodes
for simplified logic in your application.
However, the best practice these days is to provide your application w
Hi Colvin,
Thank for your answer and your link, I will see if I can solve my problem.
I use a old solr, I know :'(.
This old version is used since several years and I have a huge set of data
(around 200M of textfile to index).
Re-indexing my set of data will take too much time for me (several we
Hi Rahul,
This sounds very interesting!
I enjoyed the discussion at CoC and would be very
interested to hear more about the technical details.
I am also curious to know more what you mean by "in-place"
and what the expectation is around downtime.
Either way I am sure this would be a great addit
If you want to improve the collapsing performance, you might use a numeric
supplier id to collapse on instead of a string.
You've denormalized things, which is typically the right trade-off. As you
have observed, the down-side is that you have to reindex lots of stuff when
a related entity changes
Great point! I must focus on zoekt! I might change in some years. I will
see.
Regards!
Le jeu. 20 mars 2025 à 20:02, Andrew Witt a
écrit :
> Since you say, "I already started with Zoekt", I'm guessing you are facing
> some problem large enough to cause you to abandon your work so far.
>
> I say
