It is called the "Lucene/Solr Connector" component.
Karl
On Tue, Jul 13, 2021 at 10:11 AM wrote:
> Ok, there is no "Solr connector" component in JIRA, can you add it please
> ?
>
> -Message d'origine-
> De : Karl Wright
> Envoyé : mardi 13 juillet 2021 16:04
> À : dev
> Objet : Re:
Ok, there is no "Solr connector" component in JIRA, can you add it please ?
-Message d'origine-
De : Karl Wright
Envoyé : mardi 13 juillet 2021 16:04
À : dev
Objet : Re: Solr output connector - behavior on some exceptions
Null values causing exceptions in the output connector should
Null values causing exceptions in the output connector should be addressed
independently in the output connector. But basically as long as that is
done I am fine with your proposal.
Karl
On Tue, Jul 13, 2021 at 9:59 AM wrote:
> I ended up in that part of the code while debugging after we had
I ended up in that part of the code while debugging after we had a crawling job
stopped because of an exception concerning a document having a null value for a
specific metadata and another one with a value that triggered a request parsing
issue on Solr side.
Julien
-Message
If the "solr is down" exceptions are indeed caught upstream, I'm
tentatively in agreement that this fallback logic can be changed. But I
would like to understand what specifically you are seeing this happen for.
What cases are you hoping to improve?
Karl
On Tue, Jul 13, 2021 at 9:39 AM wrote:
Here is the code snippet that I mentionned in the section 1) of the previous
mail :
// Otherwise, no idea what the trouble is, so presume that retries might fix
it.
String message3 = "IO exception during "+context+": "+e.getMessage();
Logging.ingest.warn(message3,e);
throw new
Hi,
I would like to change the behavior of the Solr output connector concerning
two exception handling cases :
1. In the current < handleIOException > method of the HttpPoster class,
the < unknown > case looks like this :
As the comment says, we don't know the type of IOException, so
