This is an interesting bug. I’m wondering if we can completely skip the
initialization of UpdateRequestProcessorFactories in PULL replicas...
On Wed, Aug 5, 2020 at 8:40 AM Erick Erickson
wrote:
> Offhand, this looks like a bug, please raise a JIRA.
>
> You said: " We also have
HI
I am getting the following exception if passing a long String in q
parameter .
Great advice Erick, kindly appreciated.
I removed PorterStemFilter as you suggested and it worked as one would
expect it to. Very useful to learn about avoiding KeywordTokenizerFactory,
the limitation of the WhitespaceTokenizer and the testing approach.
Best,
Phil
On Wed, Aug 5, 2020 at 8:37 PM
What is the Solr field type definition for this field? And what sort of
spatial data do you add here -- just points or what?
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Mon, Aug 3, 2020 at 10:09 PM sanjay dutt
wrote:
> Hello Solr community,
>
Hi All,
We have tried the system variable recommend here
https://www.eclipse.org/jetty/documentation/current/high-load.html
The errors stopped now, and system is running stable.
Is there any disadvantage using the following?
sysctl -w net.ipv4.tcp_tw_recycle=1
Somewhere I read tw_reuse also
Thanks Erik.When you mentioned we can't control sorting by _docid_ . So if not
client Does that mean solr internally makes such type of queries which includes
sort on internal Lucene Id? And for what purpose?
Sent from Yahoo Mail on Android
On Wed, Aug 5, 2020 at 6:27 PM, Erick Erickson
Offhand, this looks like a bug, please raise a JIRA.
You said: " We also have DocBasedVersionConstraintsProcessorFactory in our
UpdateProcessorChain for optimistic Concurrency.”
Optimistic concurrency is automatically enofrced on the _version_ field. The
intent of this processor factory is to
This seems to have been introduced in
https://issues.apache.org/jira/browse/SOLR-13972 in 8.4
That test seems to be inverted for sure.
Jason?
Jan
> 5. aug. 2020 kl. 13:15 skrev Mark Todd1 :
>
>
> I've configured SolrCloud (8.5) with both SSL and Authentication which is
> working correctly.
A sort on anything can cause an OOM… That said, _all_ fields defined in your
Solr schema should have docValues set to true if you sort, group, use function
queries or facet on them. What’s happening is the docValues structure is being
synthesized at runtime on the heap. In recent Solr releases
Lucene has never really supported this migration path. There’s a whole long
discussion of why, but basically you can’t upgrade an index with 100% fidelity
because the original information isn’t there. Here’s the most succinct
definition I’ve seen (from Robert Muir):
"I think the key issue here
First of all, lots of attachments are stripped by the mail server so a number
of your attachments didn’t come through, although your field definitions did so
we can’t see your results.
KeywordTokenizerFactory is something I’d avoid at this point. It doesn’t break
up the input at all, so input
Hello,
I've had a break-through with my partial string search problem, I don't
understand why though.
I found yet another example,
https://medium.com/aubergine-solutions/partial-string-search-in-apache-solr-4b9200e8e6bb
and this one uses a different tokenizer, whitespaceTokenizerFactory
Hi All,
We are presently using solr 5.3.0 and planning to migrate to version 8.4.1 .I
tried using index upgrader for the same .
I am able to upgrade 5.3.0->6.6.6 and 6.6.6 to 7.7.3.But when I try upgrading
7.7.3 index to 8.4.1,I keep getting following error :
This index was initially
I've configured SolrCloud (8.5) with both SSL and Authentication which is
working correctly. However, I get the following warning in the logs
Solr authentication is enabled, but SSL is off. Consider enabling SSL to
protect user credentials and data with encryption
Looking at the source
Hello,
I'm new to Solr and to this user group. Any help with this problem would be
greatly appreciated.
I'm trying to get partial keyword search results working. This seems like a
fairly common problem, I've found numerous google results offering
solutions
for instance
Hi all,
We are using SOLR 8.6.0 and we put the "read-only" parameter on a SOLRCLOUD
collection with 3 replicas. Here is the error message we have following a
problem on one of the SOLR nodes:
Error while trying to
recover:org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException
:
Hello, everyone. I hope you are all well and safe.
I am trying to enable authentication to our Solr 8.3.1 servers. I followed
the instructions on this page:
https://lucene.apache.org/solr/guide/8_3/basic-authentication-plugin.html
and used the "Global (JVM) Basic Auth Credentials" with the
Hi All,
We have a hybrid cluster with a mix of TLOG and PUll replica. We also have
DocBasedVersionConstraintsProcessorFactory in our UpdateProcessorChain for
optimistic Concurrency.
Our TLOG replicas are our index nodes. When we start them they startup fine
with
Here is some of the work I did to remedy this effort before I knew about this
email:
https://github.com/apache/lucene-solr/pull/1712
https://issues.apache.org/jira/browse/SOLR-14702page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=17169865
It makes me sick to read
Hi,
Which file system would be better for Solr, ext4 or XFS?
Regards,
Anshuman
20 matches
Mail list logo
