beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-2469) Handling Kinesis shards splits and merges
Date Mon, 11 Dec 2017 17:40:00 GMT


ASF GitHub Bot commented on BEAM-2469:

pawel-kaczmarczyk opened a new pull request #4243: [BEAM-2469] Handling Kinesis shards splits
and merges
   Follow this checklist to help us incorporate your contribution quickly and easily:
    - [X] Make sure there is a [JIRA issue](
filed for the change (usually before you start working on it).  Trivial changes like typos
do not require a JIRA issue.  Your pull request should address just this issue, without pulling
in other changes.
    - [X] Each commit in the pull request should have a meaningful subject line and body.
    - [X] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`,
where you replace `BEAM-XXX` with the appropriate JIRA issue.
    - [X] Write a pull request description that is detailed enough to understand what the
pull request does, how, and why.
    - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
    - [ ] If this contribution is large, please file an Apache [Individual Contributor License
   This pull requests tries to address stream resharding operations described in detail [here](

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Handling Kinesis shards splits and merges
> -----------------------------------------
>                 Key: BEAM-2469
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-extensions
>            Reporter: Paweł Kaczmarczyk
>            Assignee: Paweł Kaczmarczyk
> Kinesis stream consists of [shards|]
that allow for capacity scaling. In order to increase/decrease the capacity shards have to
be split/merged together. Such operations are currently not handled properly and will end
with errors.

This message was sent by Atlassian JIRA

View raw message