Hi Chris, thank you for your quick response I tried the flow with 1.13.2 and 1.13.1, and 1.14.0 just before the first RC and it still had the problem, so I am not sure if this is related to the session handling you pointed out, that has been fixed in 1.13.2
Le mer. 21 juil. 2021 à 16:22, Chris Sampson <[email protected]> a écrit : > 1.13.1 was known to have problems with session handling - see the Release > Note "lowlights" for 1.13.1 [1] > > It is recommended to upgrade to version 1.13.2 (or the latest 1.14.0). If > you can't upgrade then 1.13.0 would be better than 1.13.1. > > > [1] > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.13.1 > > --- > *Chris Sampson* > IT Consultant > [email protected] > <https://www.naimuri.com/> > > > On Wed, 21 Jul 2021 at 15:14, Matthieu Ré <[email protected]> wrote: > >> Hi all, >> >> Currently using NiFi 1.11.4, we face a blocking issue trying to switch to >> NiFi 1.13.1+ due to the VolatileContentRepository : some processors we use >> (and probably others that we didn't try) were not able to process >> flowfiles, such as MargeRecord, QueryRecord or SplitJson (logs are in the >> Jira >> ticket NiFi-8760 <https://issues.apache.org/jira/browse/NIFI-8760>). >> >> I wanted to know if any of you guys are able to reproduce the issue, and >> if this is not a misconfiguration from our side. The nifi.properties and >> flow.xml.gz used are available in the ticket. If I am not missing anything, >> we could identify that the issue could come from this commit >> <https://github.com/apache/nifi/commit/528fce2407d092d4ced1a58fcc14d0bc6e660b89> >> since >> it appeared with the 1.13.1 and the flow is working fine with 1.13.0. >> >> Open to contribute as much as I can if you confirm that this is not due >> to a misconfiguration.. >> >> Thanks ! >> Matthieu >> > -- Matthieu RÉ Data Scientist - Machine Learning Engineer - Dassault Systèmes ENSIIE, M2 AIC (Université Paris-Saclay) Tel: 0631609755 Email: [email protected]
