Also can you show the attributes of the flowfile before and after route on attribute processor? The provenance/lineage should make that easy to grab and see.
Thanks On Mon, Aug 28, 2017 at 11:25 AM, mayank rathi <[email protected]> wrote: > Hello Laurens, > > eventName is an attribute of flow file or is part of content ( data) ? If > it's content then please use RouteOnContent processor > > On Mon, Aug 28, 2017 at 10:54 AM, Laurens Vets <[email protected]> wrote: >> >> Hi Mark, >> >> Can it be that there's something wrong with the below expression? >> >> Basically, I'm processing JSON objects which all have an eventName field. >> I've put in a RouteOnAttribute with the following expression: >> >> ${eventName:startsWith('Get'):or( >> ${eventName:startsWith('List')} >> ):or( >> ${eventName:startsWith('Describe')} >> )} >> >> But I still see events starting with Get, Describe & List in the field >> eventName. Do I need to use "*" after those words? >> >> >>> Certainly, you can: >>> >>> ${field:startsWith('alpha'):or( >>> ${field:startsWith('beta')} >>> ):or( >>> ${field:startsWith('gamma')} >>> )} >>> >>> Or, alternatively, you could use a regex: >>> >>> ${field:matches( '(alpha|beta|gamma).*' )} >>> >>> Thanks >>> -Mark >>> >>>> On Aug 24, 2017, at 11:06 AM, Laurens Vets <[email protected]> wrote: >>>> >>>> Hi list, >>>> >>>> Is it possible to have multiple 'or' statements in the query language? >>>> What I want to do is route on a JSON attribute if it doesn't start with >>>> 'alpha', 'beta' or 'gamma'. >>>> >>>> Is it possible to add a 3rd condition to the following somehow: >>>> >>>> ${field:startsWith('alpha'):or( >>>> ${field:startsWith('beta')} >>>> )} > > > > > -- > NOTICE: This email message is for the sole use of the intended recipient(s) > and may contain confidential and privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy all > copies of the original message.
