This change aims to allow test-machine users to supply their own consumer group configuration parameters when creating a test-machine that uses the rest-proxy. The allowed parameters are described in the API Docs.
One feature this is intended to support is to get the test-machine to read from the beginning of some topic that exists in another environment. This will allow users to retrieve data from e.g. production or staging environments, and run it through a test version of the application running on a developer machine without requiring access to the broker itself which can then be locked down for security purposes. Once this rest-proxy feature is merged, we'll get the ability to request data from a specific timestamp too.
When using this feature to read from the beginning, you'll likely want to also configure the fetch.min.bytes and consumer.fetch.timeout.ms properties to keep the response sizes reasonably small.
This change aims to allow test-machine users to supply their own consumer group configuration parameters when creating a test-machine that uses the rest-proxy. The allowed parameters are described in the API Docs.
One feature this is intended to support is to get the test-machine to read from the beginning of some topic that exists in another environment. This will allow users to retrieve data from e.g. production or staging environments, and run it through a test version of the application running on a developer machine without requiring access to the broker itself which can then be locked down for security purposes. Once this rest-proxy feature is merged, we'll get the ability to request data from a specific timestamp too.
When using this feature to read from the beginning, you'll likely want to also configure the
fetch.min.bytesandconsumer.fetch.timeout.msproperties to keep the response sizes reasonably small.Example use would look something like this....