...

• partitions
  List of partitions to fetch data from. Multiple partitions can be provided as a comma-separated list. e.g. --partitions 0,1,2
• offsets
  List of offsets to start reading from. If specified, the list must have the same number of elements as the partitions list in the same sequence. If not specified, starts reading from earliest unless --from-latest is specified. Only works with --partitions option.

Proposed Changes

Describe the new thing you want to do in appropriate detail. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences. Use judgement based on the scope of the changeAs mentioned earlier, two new flags are introduced. When they are specified, consumer will be assigned only specified partitions and seek to provided offsets (If specified). User can specify start offsets to ensure the results are precisely comparable.

Compatibility, Deprecation, and Migration Plan

• What impact (if any) will there be on existing users?
• If we are changing behavior how will we phase out the older behavior?
• If we need special migration tools, describe them here.
• When will we remove the existing behavior?

Test Plan

Describe in few sentences how the KIP will be tested. We are mostly interested in system tests (since unit-tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?

Rejected Alternatives

• This change is backward compatible since both parameters are optional

Test Plan

The change can be easily tested by specifying new parameters and checking metrics. 

Rejected Alternatives

NAIf there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.