Bilal,

And I will be more than happy to help fix this. This is plaguing myself as
well. Please let me know what your ticket number is, and I will help in
whatever way is needed to get this fixed.

/Adam

On Wed, Feb 8, 2023 at 10:13 AM Dan S <dsti...@gmail.com> wrote:

> Bilal,
>  Please create a bug ticket for this.
>
> On Wed, Feb 8, 2023 at 4:51 AM Bilal Bektaş <bilal.bek...@obase.com
> .invalid>
> wrote:
>
> > Hi Dev Team,
> >
> > NiFi environment was upgraded from 1.15.1 to 1.19.1. The following
> > situation has occurred with the ValidateXml processor:
> >
> > ValidateXml processor works correctly on 1.15.1 and
> > validatexml.invalid.error attribute gives an detail information about the
> > error.
> >
> > ValidateXml processor works on 1.19.1 but validatexml.invalid.error
> > attribute does not give an detail information about the error.
> > validatexml.invalid.error attriubute only contains “Validation failed”
> text.
> >
> > Similar problem was talked in cloudera community and Eduu said that:
> >
> > Hi @ChuckE<
> > https://community.cloudera.com/t5/user/viewprofilepage/user-id/98065>
> > using NiFi 1.15.2 seems to add the error detail in the
> > "validatexml.invalid.error" attribute.
> > For example --> "cvc-minLength-valid: Value '' with length = '0' is not
> > facet-valid with respect to minLength '1' for type 'HotelCode"
> >
> > This seems to be an issue starting from NiFi 1.16.3, maybe a bug?
> > You can use NiFi 1.15.2 or custom code as @SAMSAL<
> > https://community.cloudera.com/t5/user/viewprofilepage/user-id/80381>
> > suggested.
> >
> >
> > Ref:
> >
> https://community.cloudera.com/t5/Support-Questions/How-to-get-the-reason-for-invalid-XML/m-p/348767/highlight/true#M235443
> >
> > Is it possible to add to this feature in new NiFi version like NiFi
> 1.15.1?
> >
> >
> > Thank you in advance,
> >
> > --Bilal
> >
> > obase
> > TEL: +90216 527 30 00
> > FAX: +90216 527 31 11
> > [http://www.obase.com/images/signature/home.png]<http://www.obase.com> [
> > http://www.obase.com/images/signature/facebook.png] <
> > https://www.facebook.com/obasesocial>  [
> > http://www.obase.com/images/signature/twitter.png] <
> > https://twitter.com/obasesocial>  [
> > http://www.obase.com/images/signature/linkedin.png] <
> > https://tr.linkedin.com/in/obase>
> > [http://www.obase.com/images/signature/obaselogo.png]<
> http://www.obase.com
> > >
> >
> > Bu elektronik posta ve onunla iletilen bütün dosyalar sadece göndericisi
> > tarafindan almasi amaclanan yetkili gercek ya da tüzel kisinin kullanimi
> > icindir. Eger söz konusu yetkili alici degilseniz bu elektronik postanin
> > icerigini aciklamaniz, kopyalamaniz, yönlendirmeniz ve kullanmaniz
> > kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz
> gerekmektedir.
> > OBASE bu mesajin icerdigi bilgilerin doğruluğu veya eksiksiz oldugu
> > konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne
> > sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve
> > saklanmasindan sorumlu degildir. Bu mesajdaki görüsler yalnizca gönderen
> > kisiye aittir ve OBASE görüslerini yansitmayabilir.
> >
> > Bu e-posta bilinen bütün bilgisayar virüslerine karsi taranmistir.
> >
> > This e-mail and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they are
> > addressed. If you are not the intended recipient you are hereby notified
> > that any dissemination, forwarding, copying or use of any of the
> > information is strictly prohibited, and the e-mail should immediately be
> > deleted. OBASE makes no warranty as to the accuracy or completeness of
> any
> > information contained in this message and hereby excludes any liability
> of
> > any kind for the information contained therein or for the information
> > transmission, recepxion, storage or use of such in any way whatsoever.
> The
> > opinions expressed in this message belong to sender alone and may not
> > necessarily reflect the opinions of OBASE.
> >
> > This e-mail has been scanned for all known computer viruses.
> >
>

Reply via email to