Secondary plugin input got affected by primary's buffer chunk.

[yang-wei]

Is your feature request related to a problem? Please describe.

Secondary plugin input got affected by primary's buffer chunk.

As described in awslabs/aws-fluent-plugin-kinesis#167 , when primary plugin is not working the input of secondary input has to depends on the primary plugin.

If secondary plugin get triggered I am expecting the input is same as what the primary plugin is handling.

Like I am expecting:

{"test":"this is a test message", "message_id":"1234"}

instead of

36cbd167849700a041b3bd691b014937íƒì{"test":"this is a test message", "message_id":"1234"}Ÿ

Where 36cbd167849700a041b3bd691b014937íƒì is added by plugin

side note

Also currently there is no clear documentation regarding which secondary plugin could be supported by which primary plugin =(
Though I do get something like this

Use different plugin for secondary. Check the plug
in works with primary like secondary_file primary="Fluent::KinesisStreamsOutput" secondary="Flue
nt::Plugin::ExecOutput"

[github-actions]

This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days

[github-actions]

This issue was automatically closed because of stale in 30 days