You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Input and Output provided by Pipeline-to-Pipeline can be configured with a codec, but the configuration is ignored; the in-memory event is passed directly from the output to the input.
We should error helpfully if someone attempts to use codecs with these inputs/outputs.
The text was updated successfully, but these errors were encountered:
Yes, i try to use codec in pipeline input.
pipeline to read udp and drop when it's a healcheck message and send to another pipelie with codec cef.
Don't woek because codec in input pipeline seems to be not read.
@adelbot the pipeline input and output do not use codecs by design, since serialising and deserialising the events through a codec would add significant overhead and noticeably impact performance. The bug reported here is that they don't complain when a codec is specified.
The Input and Output provided by Pipeline-to-Pipeline can be configured with a codec, but the configuration is ignored; the in-memory event is passed directly from the output to the input.
We should error helpfully if someone attempts to use codecs with these inputs/outputs.
The text was updated successfully, but these errors were encountered: