You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by "Nery, Francisco" <fr...@contractors.roche.com> on 2023/05/03 08:55:30 UTC
Re: [Sender Not Verified] Re: Issue upgrading Nifi(1.7.0) & Minifi(0.5.0) to 1.20.0
Hello Matt,
Our custom nars have already been recompiled and rebuilt with the version
1.20.0. Any other ideas? Or any other info you need? We have not tried with
the latest 1.21.0 version although I don't think the problem would be
solved.
Regards,
Francisco.
On Sat, Apr 29, 2023 at 4:38 PM Matt Burgess <ma...@apache.org> wrote:
> Ignasi,
>
> A lot has changed between MiNiFi 0.5.0 and MiNiFi 1.20.0, including
> changes to NARs, how they are loaded, etc. For custom NARs I would try to
> rebuild them using the same version of NiFi and MiNiFi dependencies. The
> latest Apache NiFi release is now 1.21.0 so I would change the NiFi and
> MiNiFi dependencies in your custom NARs to 1.21.0. You may find that there
> are compilation errors or some issue that wasn't there before, these would
> be things introduced between NiFi 1.7.0 and NiFi 1.21.0. I can't think of
> any offhand but wanted to mention it in case your NARs no longer
> compile/build.
>
> Regards,
> Matt
>
>
> On Fri, Apr 28, 2023 at 5:31 AM Garriga, Ignasi
> <ig...@roche.com.invalid> wrote:
>
>> Hi all,
>>
>> We're trying to upgrade versions of Apache Nifi 1.7.0 with Minifi 0.5.0
>> to the latest embedded version 1.20.0.
>> We have some custom nars that when we add to the project there are
>> problems with the Classloader and bundle not found:
>>
>> ERROR [main] o.a.n.n.StandardExtensionDiscoveringManager Could not
>> instantiate class of type org.apache.nifi.processors.standard.JoltTransformJSON
>> using ClassLoader for bundle default:unknown:unversioned because the bundle
>> could not be found
>>
>>
>> In the following pictures I share with you the docker-compose that we use
>> to create an image and all libraries that we use to compile. It can help to
>> identify something or give a clue to find the solution.
>>
>> pm-data-pipeline:
>> image: apache/nifi-minifi:1.20.0
>> restart: always
>> hostname: pm-data-pipeline
>> container_name: pm-data-pipeline
>> environment:
>> - NIFI_WEB_HTTPS_PORT=9443
>> ports:
>> - "8080:8080"
>> - "9443:9443"
>> volumes:
>> - ../../../assets/templates/nMonFlow.yml:/opt/minifi/minifi-1.20.0/conf/config.yml
>> - ../../../assets/nifi-invoke-igw-nar-1.6.0.nar:/opt/minifi/minifi-1.20.0/lib/nifi-invoke-igw-nar-1.6.0.nar
>> - ../../../assets/pm-data-pipeline-ssl-context-service-nar-1.0.0.nar:/opt/minifi/minifi-1.20.0/lib/pm-data-pipeline-ssl-context-service-nar-1.0.0.nar
>> - ../../../assets/nifi-amqp-nar-1.20.0.nar:/opt/minifi/minifi-1.20.0/lib/nifi-amqp-nar-1.20.0.nar
>>
>>
>> [image: image.png]
>>
>>
>> Thank you in advance for your support and don't hesitate to contact us if
>> you need more information .
>>
>> Regards,
>>
>>
>> --
>> *--*
>>
>> *Ignasi Garriga Sala* Coagulation Software Developer
>>
>> Roche Diagnostics SL
>> Patient Care POC
>> Av. de la Generalitat, 171-173
>> E-08174 Sant Cugat del Vallès
>>
>> M +34 619 048 267
>> *ignasi.garriga@roche.com* <ignasi.garriga@roche.com;>
>>
>> roche.es <https://diagnostics.roche.es> | AularioRoche
>> <https://aulario.roche.es> | RocheDialog
>> <https://dialogportal.roche.com/dialog/es/es/e-services> | Twitter
>> <https://twitter.com/roche_es> | YouTube <https://www.youtube.com/roche>
>> | Facebook <https://www.facebook.com/RocheCareers> | LinkedIn
>> <https://es.linkedin.com/company/roche-diagnostics-espa%C3%B1a>
>>
>> *Confidencialidad* - Este mensaje ha sido dirigido sólo al destinatario
>> o a los destinatarios mencionados y puede contener información confidencial
>> y/o de uso restringido a profesionales de la salud, en cuyo caso su
>> remisión a terceros que no sean profesionales de la salud no está
>> permitida. Si usted tiene dudas respecto a quién puede remitir este mensaje
>> y/o la información que contiene, por favor, consulte con su remitente. Si
>> usted no debería haber recibido este correo o piensa que el destinatario es
>> incorrecto, por favor contacte con el remitente y borre este mensaje. El
>> uso no autorizado de la información contenida en este mensaje está
>> prohibido.
>>
>> *Protección de datos* - Roche Diagnostics, S.L.U. (con domicilio en
>> Avda. de la Generalitat, 171-173, 08174 Sant Cugat del Vallès, Barcelona)
>> es el responsable del tratamiento de sus datos de contacto corporativos con
>> el fin de poder mantener relaciones con usted o con la empresa, entidad y
>> organización para la cual usted trabaja o colabora. Para obtener más
>> información sobre cómo tratamos sus datos y cómo ejercer sus derechos,
>> consulte nuestra política de privacidad
>> <https://go.roche.com/politicadeprivacidad>.
>>
>>
Re: [Sender Not Verified] Re: Issue upgrading Nifi(1.7.0) & Minifi(0.5.0) to 1.20.0
Posted by "Comas, Joan" <jo...@roche.com.INVALID>.
Dear Matt,
I am taking over the Architecture role from Ignasi.
Would it be possible for you to check Francisco's latest comments and come
back with some feedback?
We would really appreciate it,
Thanks a lot and kind regards
On Wed, May 3, 2023 at 10:55 AM Nery, Francisco <
francisco.nery@contractors.roche.com> wrote:
> Hello Matt,
>
> Our custom nars have already been recompiled and rebuilt with the version
> 1.20.0. Any other ideas? Or any other info you need? We have not tried with
> the latest 1.21.0 version although I don't think the problem would be
> solved.
>
> Regards,
> Francisco.
>
> On Sat, Apr 29, 2023 at 4:38 PM Matt Burgess <ma...@apache.org> wrote:
>
>> Ignasi,
>>
>> A lot has changed between MiNiFi 0.5.0 and MiNiFi 1.20.0, including
>> changes to NARs, how they are loaded, etc. For custom NARs I would try to
>> rebuild them using the same version of NiFi and MiNiFi dependencies. The
>> latest Apache NiFi release is now 1.21.0 so I would change the NiFi and
>> MiNiFi dependencies in your custom NARs to 1.21.0. You may find that there
>> are compilation errors or some issue that wasn't there before, these would
>> be things introduced between NiFi 1.7.0 and NiFi 1.21.0. I can't think of
>> any offhand but wanted to mention it in case your NARs no longer
>> compile/build.
>>
>> Regards,
>> Matt
>>
>>
>> On Fri, Apr 28, 2023 at 5:31 AM Garriga, Ignasi
>> <ig...@roche.com.invalid> wrote:
>>
>>> Hi all,
>>>
>>> We're trying to upgrade versions of Apache Nifi 1.7.0 with Minifi 0.5.0
>>> to the latest embedded version 1.20.0.
>>> We have some custom nars that when we add to the project there are
>>> problems with the Classloader and bundle not found:
>>>
>>> ERROR [main] o.a.n.n.StandardExtensionDiscoveringManager Could not
>>> instantiate class of type org.apache.nifi.processors.standard.JoltTransformJSON
>>> using ClassLoader for bundle default:unknown:unversioned because the bundle
>>> could not be found
>>>
>>>
>>> In the following pictures I share with you the docker-compose that we
>>> use to create an image and all libraries that we use to compile. It can
>>> help to identify something or give a clue to find the solution.
>>>
>>> pm-data-pipeline:
>>> image: apache/nifi-minifi:1.20.0
>>> restart: always
>>> hostname: pm-data-pipeline
>>> container_name: pm-data-pipeline
>>> environment:
>>> - NIFI_WEB_HTTPS_PORT=9443
>>> ports:
>>> - "8080:8080"
>>> - "9443:9443"
>>> volumes:
>>> - ../../../assets/templates/nMonFlow.yml:/opt/minifi/minifi-1.20.0/conf/config.yml
>>> - ../../../assets/nifi-invoke-igw-nar-1.6.0.nar:/opt/minifi/minifi-1.20.0/lib/nifi-invoke-igw-nar-1.6.0.nar
>>> - ../../../assets/pm-data-pipeline-ssl-context-service-nar-1.0.0.nar:/opt/minifi/minifi-1.20.0/lib/pm-data-pipeline-ssl-context-service-nar-1.0.0.nar
>>> - ../../../assets/nifi-amqp-nar-1.20.0.nar:/opt/minifi/minifi-1.20.0/lib/nifi-amqp-nar-1.20.0.nar
>>>
>>>
>>> [image: image.png]
>>>
>>>
>>> Thank you in advance for your support and don't hesitate to contact us
>>> if you need more information .
>>>
>>> Regards,
>>>
>>>
>>> --
>>> *--*
>>>
>>> *Ignasi Garriga Sala* Coagulation Software Developer
>>>
>>> Roche Diagnostics SL
>>> Patient Care POC
>>> Av. de la Generalitat, 171-173
>>> E-08174 Sant Cugat del Vallès
>>>
>>> M +34 619 048 267
>>> *ignasi.garriga@roche.com* <ignasi.garriga@roche.com;>
>>>
>>> roche.es <https://diagnostics.roche.es> | AularioRoche
>>> <https://aulario.roche.es> | RocheDialog
>>> <https://dialogportal.roche.com/dialog/es/es/e-services> | Twitter
>>> <https://twitter.com/roche_es> | YouTube <https://www.youtube.com/roche>
>>> | Facebook <https://www.facebook.com/RocheCareers> | LinkedIn
>>> <https://es.linkedin.com/company/roche-diagnostics-espa%C3%B1a>
>>>
>>> *Confidencialidad* - Este mensaje ha sido dirigido sólo al destinatario
>>> o a los destinatarios mencionados y puede contener información confidencial
>>> y/o de uso restringido a profesionales de la salud, en cuyo caso su
>>> remisión a terceros que no sean profesionales de la salud no está
>>> permitida. Si usted tiene dudas respecto a quién puede remitir este mensaje
>>> y/o la información que contiene, por favor, consulte con su remitente. Si
>>> usted no debería haber recibido este correo o piensa que el destinatario es
>>> incorrecto, por favor contacte con el remitente y borre este mensaje. El
>>> uso no autorizado de la información contenida en este mensaje está
>>> prohibido.
>>>
>>> *Protección de datos* - Roche Diagnostics, S.L.U. (con domicilio en
>>> Avda. de la Generalitat, 171-173, 08174 Sant Cugat del Vallès, Barcelona)
>>> es el responsable del tratamiento de sus datos de contacto corporativos con
>>> el fin de poder mantener relaciones con usted o con la empresa, entidad y
>>> organización para la cual usted trabaja o colabora. Para obtener más
>>> información sobre cómo tratamos sus datos y cómo ejercer sus derechos,
>>> consulte nuestra política de privacidad
>>> <https://go.roche.com/politicadeprivacidad>.
>>>
>>>
--
*Joan Comas*
Principal Software Engineer
Roche Diagnostics International AG
RIS Emerging Backend Core
Forrenstrasse 2
CH-6343 Rotkreuz
Switzerland
Tel.: +41 41 798 51 38
joan.comas@roche.com
Confidentiality Note: This message is intended only for the use of the
named recipient(s) and may contain confidential and/or proprietary
information. If you are not the intended recipient, please contact the
sender and delete this message. Any unauthorized use of the information
contained in this message is prohibited.