Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Stream Selection anomoly

I have a Stream Selector stage with the following condition:

${record:value('/create-user_response/data[0]/request_results/this_does_not_exist') == 'failure'}

The field at the end of the path DOES NOT EXIST, yet the pipeline doesn't error out completely and actually passes the record to a continuing processor stage instead of an error stage that its supposed to send to.

Any insight would be greatly appreciated.

Thanks.

Stream Selection anomoly

I have a Stream Selector stage with the following condition:

${record:value('/create-user_response/data[0]/request_results/this_does_not_exist') == 'failure'}

The field at the end of the path DOES NOT EXIST, yet the pipeline doesn't error out completely and actually passes the record to a continuing processor stage instead of an error stage that its supposed to send to.

Any insight would be greatly appreciated.

Thanks.

Per Jeff's update request...

For some reason now the behavior has changed and the Selector is sending to the proper stream (don't know why it changed as before is was definitely sending it to the default) However, I'm still not sure why it allowed the records to be sent to Stream 1 when the field in the the condition does not exists.

Screen shot (redacted a bit for privacy sake):

C:\fakepath\2019-08-12_11-40-16.jpg

Stream Selection anomoly

I have a Stream Selector stage with the following condition:

${record:value('/create-user_response/data[0]/request_results/this_does_not_exist') == 'failure'}

The field at the end of the path DOES NOT EXIST, yet the pipeline doesn't error out completely and actually passes the record to a continuing processor stage instead of an error stage that its supposed to send to.

Any insight would be greatly appreciated.

Thanks.

Per Jeff's update request...

For some reason now the behavior has changed and the Selector is sending to the proper stream (don't know why it changed as before is was definitely sending it to the default) However, I'm still not sure why it allowed the records to be sent to Stream 1 when the field in the the condition does not exists.

Screen shot (redacted a bit for privacy sake):

C:\fakepath\2019-08-12_11-40-16.jpgC:\fakepath\2019-08-12_11-40-16.jpg

Stream Selection anomoly

I have a Stream Selector stage with the following condition:

${record:value('/create-user_response/data[0]/request_results/this_does_not_exist') == 'failure'}

The field at the end of the path DOES NOT EXIST, yet the pipeline doesn't error out completely and actually passes the record to a continuing processor stage instead of an error stage that its supposed to send to.

Any insight would be greatly appreciated.

Thanks.

Per Jeff's update request...

For some reason now the behavior has changed and the Selector is sending to the proper stream (don't know why it changed as before is was definitely sending it to the default) However, I'm still not sure why it allowed the records to be sent to Stream 1 when the field in the the condition does not exists.

Screen shot (redacted a bit for privacy sake):

C:\fakepath\2019-08-12_11-40-16.jpg