Hello,
Does anybody have advice on why CDCR would say its Forwarding updates (with no
errors) even though the solr servers its replicating to aren't updating?
We have just under 50 million documents, that are spread across 4 servers. Each
server has a node each.
One side is updating happily so
Hi Mark,
It looks like you're using the "path" wildcard as it's intended, but
some bug is causing the behavior you're seeing. It should be working
as you expected, but evidently it's not.
One potential workaround might be to leave out the "path" property
entirely in your "custom-example" permiss
Thank you, I've created https://issues.apache.org/jira/browse/SOLR-15018
now.
Regards,
Andreas
Erick Erickson wrote on 24.11.20 13:29:
Sure, raise a JIRA. Thanks for the update...
On Nov 24, 2020, at 4:12 AM, Andreas Hubold
wrote:
Hi,
I was able to work around the issue. I'm now using a
Parameters, no. You could use a PatternReplaceCharFilterFactory. NOTE:
*FilterFactory are _not_ what you want in this case, they are applied to
individual tokens after parsing
*CharFiterFactory are invoked on the entire input to the field, although I
can’t say for certain that even that’s early
Dear Team,
We are in the process of migrating from Solr 5 to Solr 8, during testing
identified that "Not null" queries on plong & pint field types are not
giving any results, it is working fine with solr 5.4 version.
could you please let me know if you have suggestions on this issue?
Thanks
Deep
Ages ago at Netflix, I fixed this with a few hundred synonyms. If you are
working with
a fixed vocabulary (movie titles, product names), that can work just fine.
babysitter, baby-sitter, baby sitter
fullmetal, full-metal, full metal
manhunter, man-hunter, man hunter
spiderman, spider-man, spider
