Arroyo use NATS bug

[like0121]

Observed behavior

2026/03/15 12:41:11.282135 [WRN] Invalid JetStream request '$G > $JS.API.CONSUMER.CREATE.nats-arroyo.nats-arroyo-source_logs_0-IErrn0U0tX': json: unknown field "rate_limit"

When arroyo start it's pipeline,send a "rate_limit",nats can't handle this parameter "rate_limit"

Expected behavior

want to use arroyo connect nats normal

Server and client version

Arroyo. v0.15.0

NATS v2.12.5

Host environment

No response

Steps to reproduce

No response

[MauriceVanVeen]

Arroyo is sending a rate_limit field that doesn't exist. However, a rate_limit_bps field on the consumer config does exist. This is a bug that should be fixed in Arroyo.

[wallyqs]

which client is arroyo using?

[MauriceVanVeen]

which client is arroyo using?

Seems Rust, in which case this client PR seems relevant: nats-io/nats.rs#1536

However, the Arroyo docs think the consumer rate limiting is about messages per second:

consumer.rate_limit | Maximum number of messages per second that will be delivered to consumer (-1 for no limit) | No | 1000
https://doc.arroyo.dev/connectors/nats/

So, Arroyo would need an update regardless, since it is bits per second, not messages per second.