-
Notifications
You must be signed in to change notification settings - Fork 311
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d131462
commit abc93c1
Showing
1 changed file
with
44 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
## v0.1.5 (February 7, 2020) | ||
|
||
ENHANCEMENTS: | ||
|
||
* RudderStack can route events to Redshift and BigQuery warehouses in a single node mode | ||
|
||
* Support for Rate-limiting events via configuration | ||
|
||
* Support for object storage destinations Azure Cloud Storage and Google Cloud Storage | ||
|
||
* New stats to profile the processor module and JobsDB | ||
|
||
* JobsDB table size can be configured by size or number of rows | ||
|
||
* Table dumps file name changes to support faster replays | ||
|
||
* Flexible API format between the backend and the transformer. Support added more HTTP methods and content-types to send data to destinations | ||
|
||
* Improved user transformations memory management | ||
|
||
* Kubernetes support for enterprise edition | ||
|
||
BUG FIXES: | ||
|
||
* OOM crash during table dumps | ||
|
||
* Postgres invalid JSON content crash | ||
|
||
* Multiple alerts issue when the server enters the degraded mode | ||
|
||
* Multiple maintenance databases | ||
|
||
* Recommendations for production deployments | ||
|
||
* Gateway latency fix | ||
|
||
* Created_at timestamp is generated at Postgres now | ||
|
||
|
||
BREAKING CHANGES: | ||
|
||
* Events disk format hasn't changed. To handle the inflight changes, bring down both the services and bring them up back with the latest releases in the following order the transformer and then the backend. This can be a rolling update node by node. | ||
|
||
|