olr output connector behavior on some exceptions
> -
>
> Key: CONNECTORS-1671
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1671
> Project: ManifoldCF
> Is
Assignee: Karl Wright
Resolution: Fixed
r1893132
> Solr output connector behavior on some exceptions
> -
>
> Key: CONNECTORS-1671
> URL: https://issues.apache.org/jira/browse/
about integrating this patch ? Let me
know if my explanations are not clear, I'm at your disposal
> Solr output connector behavior on some exceptions
> -
>
> Key: CONNECTORS-1671
> URL: https://issues.
be interpreted * as meaning that the document
or action is illegal and should not be repeated. */{code}
I have just updated the Javadoc to add "or request parsing exceptions" because
this is what happens.
{code:java}
{code}
> Solr output connector behavior on so
. That is the broad class of
exceptions that includes everything that you really don't want to ignore, e.g.
OutOfMemoryException. Can you be more specific about what you want to catch
here? I am not comfortable with this.
> Solr output connector behavior on some excepti
for you ?
> Solr output connector behavior on some exceptions
> -
>
> Key: CONNECTORS-1671
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1671
> Project: ManifoldCF
>
let 2021 16:04
> À : dev
> Objet : Re: Solr output connector - behavior on some exceptions
>
> 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 proposa
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 connec
oyé : mardi 13 juillet 2021 15:48
> À : dev
> Objet : Re: Solr output connector - behavior on some exceptions
>
> 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
-
De : Karl Wright
Envoyé : mardi 13 juillet 2021 15:48
À : dev
Objet : Re: Solr output connector - behavior on some exceptions
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
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:
3,e);
throw new ServiceInterruption(message3,
e,
currentTime + interruptionRetryTime,
-1L,
3,
false);
De : julien.massi...@francelabs.com
Envoyé : mardi 13 juillet 2021 15:39
À : dev@manifoldcf.apache.org
Objet : Solr output connector - behavior on so
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
13 matches
Mail list logo
