|
| 1 | +Tarantool 1.10.13 |
| 2 | +================= |
| 3 | + |
| 4 | +Released on 2022-04-25. |
| 5 | + |
| 6 | +* Release: :tarantool-release:`1.10.13`. |
| 7 | +* Tag: ``1.10.13``. |
| 8 | + |
| 9 | +Overview |
| 10 | +-------- |
| 11 | + |
| 12 | +1.10.13 is the next stable release in the :doc:`long-term support (LTS) version </release/policy>` |
| 13 | +1.10.x release series. |
| 14 | + |
| 15 | +The label “stable” means there are 1.10.x-based applications running in |
| 16 | +production for quite a while without known crashes, incorrect results or |
| 17 | +other showstopper bugs. |
| 18 | + |
| 19 | +This release introduces 1 improvement and resolves roughly 13 issues |
| 20 | +since the :doc:`1.10.12 </release/1.10.12>` version. |
| 21 | + |
| 22 | +Compatibility |
| 23 | +------------- |
| 24 | + |
| 25 | +Tarantool 1.10.x is backward compatible with Tarantool 1.9.x in binary |
| 26 | +data layout, client-server protocol and replication protocol. |
| 27 | + |
| 28 | +Please |
| 29 | +`upgrade <https://www.tarantool.io/en/doc/1.10/book/admin/upgrades/>`__ |
| 30 | +using the ``box.schema.upgrade()`` procedure to unlock all the new |
| 31 | +features of the 1.10.x series. |
| 32 | + |
| 33 | +Functionality added or changed |
| 34 | +------------------------------ |
| 35 | + |
| 36 | +Build |
| 37 | +~~~~~ |
| 38 | + |
| 39 | +- Support fedora-35 build (:tarantool-issue:`6692`). |
| 40 | + |
| 41 | +Bugs fixed |
| 42 | +---------- |
| 43 | + |
| 44 | +Core |
| 45 | +~~~~ |
| 46 | + |
| 47 | +- Fixed memory leak in interactive console (:tarantool-issue:`6817`). |
| 48 | + |
| 49 | +- Fixed an assertion fail when passing tuple without primary key fields |
| 50 | + to ``before_replace`` trigger. Now tuple format is checked before the |
| 51 | + execution of ``before_replace`` triggers and after each one (:tarantool-issue:`6780`). |
| 52 | + |
| 53 | +- Now inserting a tuple with the wrong ``id`` field into the ``_priv`` space |
| 54 | + returns the correct error (:tarantool-issue:`6295`). |
| 55 | + |
| 56 | +- Fixed a bug due to which all fibers created with |
| 57 | + ``fiber_attr_setstacksize()`` leaked until the thread exit. Their |
| 58 | + stacks also leaked except when ``fiber_set_joinable(..., true)`` was |
| 59 | + used. |
| 60 | + |
| 61 | +- Fixed a crash when Tarantool was launched with multiple ``-e`` or ``-l`` |
| 62 | + options without a space between the option and the value (:tarantool-issue:`5747`). |
| 63 | + |
| 64 | +Vinyl |
| 65 | +~~~~~ |
| 66 | + |
| 67 | +- Immediate removal of compacted run files created after the last |
| 68 | + checkpoint optimization now works for replica’s initial JOIN stage |
| 69 | + (:tarantool-issue:`6568`). |
| 70 | + |
| 71 | +- Fixed crash during recovery of a secondary index in case the primary |
| 72 | + index contains incompatible phantom tuples (:tarantool-issue:`6778`). |
| 73 | + |
| 74 | +Replication |
| 75 | +~~~~~~~~~~~ |
| 76 | + |
| 77 | +- Fixed replicas failing to bootstrap when master is just re-started |
| 78 | + (:tarantool-issue:`6966`). |
| 79 | + |
| 80 | +LuaJIT |
| 81 | +~~~~~~ |
| 82 | + |
| 83 | +- Fixed top part of Lua stack (red zone, free slots, top slot) |
| 84 | + unwinding in ``lj-stack`` command. |
| 85 | + |
| 86 | +- Added the value of ``g->gc.mmudata`` field to ``lj-gc`` output. |
| 87 | +- ``string.char()`` builtin recording is fixed in case when no |
| 88 | + arguments are given (:tarantool-issue:`6371`, :tarantool-issue:`6548`). |
| 89 | + |
| 90 | +- Actually made JIT respect ``maxirconst`` trace limit while recording |
| 91 | + (:tarantool-issue:`6548`). |
| 92 | + |
| 93 | +Box |
| 94 | +~~~ |
| 95 | + |
| 96 | +- Added iterator type checking and allow passing iterator as a |
| 97 | + ``box.index.{ALL,GT,…}`` directly (:tarantool-issue:`6501`). |
| 98 | + |
| 99 | +Recovery |
| 100 | +~~~~~~~~ |
| 101 | + |
| 102 | +- When ``force_recovery`` cfg option is set, Tarantool is able to boot |
| 103 | + from ``snap``/``xlog`` combinations where ``xlog`` covers changes |
| 104 | + committed both before and after ``snap`` creation. For example, |
| 105 | + ``0...0.xlog``, covering everything up to ``vclock {1: 15}`` and |
| 106 | + ``0...09.snap``, corresponding to ``vclock {1: 9}`` (:tarantool-issue:`6794`). |
0 commit comments