Skip to content
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.

Releases: uber-archive/cherami-thrift

v1.26.0

06 Oct 20:25
Compare
Choose a tag to compare

git log --pretty=format:"%an - %h - %s" v1.25.0-rc0..HEAD
Kiran RG - 45b0a9d - Merge pull request #27 from uber/cg-status-deleting
kiranrg - 72dfeec - fix thrift
kiranrg - 5dea82c - add metadata api DeleteConsumerGroupUUID
kiranrg - b38d8ca - add consumer-group status: deleting

Prepare for release v1.25.0-rc0

06 Sep 17:42
Compare
Choose a tag to compare
Pre-release
Merge pull request #26 from uber/options

Add options field to cg and destination

v1.24.0-rc0

11 Aug 03:46
Compare
Choose a tag to compare
v1.24.0-rc0 Pre-release
Pre-release
v1.24.0-rc0

Prepare for release v1.22.0

26 Jun 18:37
Compare
Choose a tag to compare
Merge pull request #24 from uber/delay

Introduce Delay field to CG APIs

Prepare for release v1.21.0

30 May 20:07
Compare
Choose a tag to compare
Merge pull request #22 from uber/active_zone_cherami

add activeZone to UpdateConsumerGroupRequest

v1.20.0

09 May 20:38
Compare
Choose a tag to compare
Merge pull request #22 from uber/active_zone_cherami

add activeZone to UpdateConsumerGroupRequest

v1.18.0

02 Apr 15:45
Compare
Choose a tag to compare
v1.18.0 Pre-release
Pre-release
Add APIs for graceful drain (#15)

* Add APIs for graceful drain

This patch adds the following APIs for supporting graceful drain:
(1) Inputhost Admin - SealExtent() API to be called by the controller
    to start the graceful drain
(2) New InputHost command type to send DRAIN command to the clients.

Note: A couple of things:
* Since we are just using the SealExtent API, I just moved the SealRequest
  definition to shared.thrift and is used by both store and admin.
* Since now we include shared.thrift, there was a name collision with
  ListDestinations and so had to rename it to ListLoadedDestinations.

* Address CR comments

Use a new DrainExtents() API rather than using the already existing
SealExtent() API.

The new API can get a list of <destinationUUID, extentUUID> pairs to
drain all the respective extents gracefully.

* Make sure we generate files properly