Re: Solr output connector - behavior on some exceptions

2021-07-13 Thread Karl Wright
her one with a > > value that triggered a request parsing issue on Solr side. > > > > Julien > > > > -----Message d'origine- > > De : Karl Wright > > Envoyé : mardi 13 juillet 2021 15:48 > > À : dev > > Objet : Re: Solr output connector - behavior on

RE: Solr output connector - behavior on some exceptions

2021-07-13 Thread julien.massiera
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

Re: Solr output connector - behavior on some exceptions

2021-07-13 Thread Karl Wright
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

RE: Solr output connector - behavior on some exceptions

2021-07-13 Thread julien.massiera
- 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

Re: Solr output connector - behavior on some exceptions

2021-07-13 Thread Karl Wright
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:

RE: Solr output connector - behavior on some exceptions

2021-07-13 Thread julien.massiera
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