Skip to content

Commit e42d3e3

Browse files
committed
doc: create 0.1.20 changelog
1 parent ec4437d commit e42d3e3

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed

changelogs/0.1.20.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
Date: 23-05-2022
2+
3+
Tag: 0.1.20
4+
5+
## Compatibility
6+
7+
VShard 0.1.20 is fully compatible with the previous VShard versions. But since
8+
this release VShard supports only Tarantool >= 1.10.1.
9+
10+
## Functionality added or changed
11+
12+
* The configuration option `collect_lua_garbage` is deprecated. Now it doesn't
13+
do anything except printing a warning in the logs that it should not be used.
14+
15+
* The router now supports `msgpack.object` feature. It can be passed to all
16+
`vshard.router.call...()` and `.map_call...()` functions. They can also accept
17+
the netbox option `return_raw` to get an msgpack object in return (gh-312).
18+
19+
* The URIs in the config now support everything what can be passed to
20+
`box.cfg.listen` and `netbox.connect()`: number, string, table. There is also
21+
a new config option - `<replica_object>.listen`. It can be used to setup
22+
listen on multiple ports on storages and for SSL in Tarantool Enterprise
23+
(gh-325).
24+
25+
## Bugs fixed
26+
27+
* Fixed a bug when router could raise a Lua exception about `vshard.error` being
28+
not defined if a storage was disabled (implicitly or via
29+
`vshard.storage.disable()`).
30+
31+
* Fixed a bug when router could raise a Lua exception about `master_uuid`
32+
variable being not defined when `master='auto'` feature was used.
33+
34+
* Fixed a bug when usage of `memtx_use_mvcc_engine` option in `box.cfg` could
35+
make bucket garbage collector not work. As a result, rebalancing also could
36+
stop working and there could be `'garbage'` and `'sent'` buckets visible in
37+
the monitoring (gh-314).

0 commit comments

Comments
 (0)