You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Shawn Heisey (Jira)" <ji...@apache.org> on 2022/10/07 17:00:00 UTC

[jira] [Comment Edited] (SOLR-16444) Solr Exception occurred while document update: "Exception writing document id 462011469 to the index; possible analysis error"

    [ https://issues.apache.org/jira/browse/SOLR-16444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614164#comment-17614164 ] 

Shawn Heisey edited comment on SOLR-16444 at 10/7/22 4:59 PM:
--------------------------------------------------------------

{quote}Caused by: java.lang.IllegalStateException: Managed stopwords not initialized correctly!
{quote}
This problem should have been discussed via our support avenues before opening an issue in Jira.  This is most likely not a bug.

This is the code snippet that creates the inner exception:
{code:java}
    if (stopWords == null) {
      throw new IllegalStateException("Managed stopwords not initialized correctly!");
    }{code}
So it looks like there are no stopwords configured for your stopword filter.  Note that most of the time, using a stopword filter is not recommended.  It can help performance, but can also greatly increase recall and reduce precision.  With modern system capacities, the tradeoff is rarely beneficial.


was (Author: elyograg):
{quote}Caused by: java.lang.IllegalStateException: Managed stopwords not initialized correctly!{quote}
This problem should have been discussed via our support avenues before opening an issue in Jira.  This is most likely not a bug.

This is the code snippet that creates the inner exception:
{code:java}
    if (stopWords == null) {
      throw new IllegalStateException("Managed stopwords not initialized correctly!");
    }{code}
So it looks like there are no stopwords configured for your stopword filter.  Note that most of the time, using a stopword filter is not recommended.  It can help performance, but can also greatly reduce recall and precision.  With modern system capacities, the tradeoff is rarely beneficial.

> Solr Exception occurred while document update: "Exception writing document id 462011469 to the index; possible analysis error"
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-16444
>                 URL: https://issues.apache.org/jira/browse/SOLR-16444
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: clients - java
>    Affects Versions: 8.10.1
>         Environment: PROD
>            Reporter: Aman Joshi
>            Priority: Major
>         Attachments: Solr_8.10.1_Exception.txt
>
>
> Intermittently, for some of the stored data, the Solr throws the below error while updating. Unable to find any root cause for this:
> "
> org.apache.solr.common.SolrException: Exception writing document id 462011469 to the index; possible analysis error.
> "
>  
> The complete exception has been attached to the thread.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org