It was likely just a decision by the developer of the processor, but in the current implementation you can parse the schema once when the processor is started which will be a lot more efficient then parsing every time the processor executes. If we do support flow file attributes then it could probably be made to cache parsed schemas.
On Tue, Sep 3, 2019 at 7:26 AM <[email protected]> wrote: > > We are using Apache NiFi 1.9.2 for one of our flows and had a question below. > > Why does the ValidateXML processor Schema File property supports only > Variable registry in Expression Language scope? > We are trying to devise a solution for our flow so that based on the incoming > file name and filetype ,appropriate XSD (camt 53,camt 52 etc) will be > selected for validation and updated in the flowfile attribute. > This attribute will then be used in the ValidateXML processor as Schema file > name so that it becomes easily configurable for future for other files as > well and we do not have to hardcode > > Thanks. > Chinmay > This e-mail and any files transmitted with it are for the sole use of the > intended recipient(s) and may contain confidential and privileged > information. If you are not the intended recipient(s), please reply to the > sender and destroy all copies of the original message. Any unauthorized > review, use, disclosure, dissemination, forwarding, printing or copying of > this email, and/or any action taken in reliance on the contents of this > e-mail is strictly prohibited and may be unlawful. Where permitted by > applicable law, this e-mail and other e-mail communications sent to and from > Cognizant e-mail addresses may be monitored. This e-mail and any files > transmitted with it are for the sole use of the intended recipient(s) and may > contain confidential and privileged information. If you are not the intended > recipient(s), please reply to the sender and destroy all copies of the > original message. Any unauthorized review, use, disclosure, dissemination, > forwarding, printing or copying of this email, and/or any action taken in > reliance on the contents of this e-mail is strictly prohibited and may be > unlawful. Where permitted by applicable law, this e-mail and other e-mail > communications sent to and from Cognizant e-mail addresses may be monitored.
