Zen

Source string Source string

221/10000 · 221
English Actions
**[Breaking change]**: Arithmetic operators must now have numeric operands. String operands are illegal.
For example, ``SELECT 1 + '1'`` was ``2`` in version 2.8. Now it causes an error.
**[Breaking change]** in operations on SCALAR columns. Since the type of a value no longer determines whether an operation is valid, comparisons and functions that require a specific type no longer work.
For example, table ``T`` has only one row with a scalar column containing ``'a'``. ``UPPER(scalar_column)`` was ``'A'`` in version 2.8. Now it causes an error.
**[Breaking change]** for the ``HEX()`` function (:tarantool-release:`2.10.0-beta1`). ``STRING`` arguments are no longer acceptable; only ``VARBINARY`` arguments are allowed.
For example, ``HEX('a')`` was ``'41'`` in version 2.8. Now it causes an error.
**[Breaking change]** for the ``POSITION()`` function (:tarantool-release:`2.10.0-beta1`). ``VARBINARY`` arguments are no longer acceptable; only ``STRING`` arguments are allowed.
For example, ``POSITION(X'41',X'41')`` was ``1`` in version 2.8. Now it causes an error.
Luarocks
Set ``FORCE_CONFIG=false`` for luarocks config to allow loading project-side ``.rocks/config-5.1.lua`` (:tarantool-release:`2.10.0-beta1`).
Build
Fedora 34 builds are now supported (:tarantool-release:`2.8.2`, :tarantool-release:`2.10.0-beta1`, :tarantool-issue:`6074`).
Fedora 28 and 29 builds are no longer supported.
Bugs fixed
**[Breaking change]** ``fiber.wakeup()`` in Lua and ``fiber_wakeup()`` in C became NOP on the currently running fiber. Previously they allowed “ignoring” the next yield or sleep, which resulted in unexpected erroneous wake-ups. Calling these functions right before ``fiber.create()`` in Lua or ``fiber_start()`` in C could lead to a crash (in debug build) or undefined behaviour (in release build) (:tarantool-issue:`6043`).
There was a single use case for the previous behaviour: rescheduling in the same event loop iteration, which is not the same as ``fiber.sleep(0)`` in Lua and ``fiber_sleep(0)`` in C. It could be done in the following way:
in C:
fiber_wakeup(fiber_self());
fiber_yield();
and in Lua:
fiber.self():wakeup()
fiber.yield()
To get the same effect in C, one can now use ``fiber_reschedule()``. In Lua, it is now impossible to reschedule the current fiber directly in the same event loop iteration. One can reschedule self through a second fiber, but it is strongly discouraged:
-- do not use this code
local self = fiber.self()
fiber.new(function() self:wakeup() end)
fiber.sleep(0)
Fixed memory leak on ``box.on_commit()`` and ``box.on_rollback()`` (:tarantool-issue:`6025`).
``fiber_join()`` now checks if the argument is a joinable fiber. The absence of this check could lead to unpredictable results. Note that the change affects the C level only; in the Lua interface, ``fiber:join()`` protection is already enabled (:tarantool-release:`2.8.2`, :tarantool-release:`2.10.0-beta1`, :tarantool-release:`2.7.3`).
Now Tarantool yields when it scans ``.xlog`` files for the latest applied vclock and finds the right place to start recovering from. It means that the instance becomes responsive right after the ``box.cfg`` call even if an empty ``.xlog`` was not created on the previous exit.
This fix also prevents the relay from timing out when a freshly subscribed replica needs rows from the end of a relatively long (hundreds of MBs) ``.xlog`` file (:tarantool-release:`2.8.2`, :tarantool-release:`2.7.3`, :tarantool-release:`2.10.0-beta1`, :tarantool-issue:`5979`).
The counter in ``N rows processed`` log messages no longer resets on each newly recovered ``xlog`` (:tarantool-release:`2.8.2`, :tarantool-release:`2.7.3`, :tarantool-release:`2.10.0-beta1`).
Fixed wrong type specification when printing fiber state change. It could lead to negative fiber IDs in the logs (:tarantool-release:`2.10.0-beta1`, :tarantool-issue:`5846`).
For example,
main/-244760339/cartridge.failover.task I> Instance state changed
instead of proper

Loading…

User avatar None

New source string

testing_project / Documentation: release/2021-08-releases — English

There was a single use case for the previous behaviour: rescheduling in the same event loop iteration, which is not the same as ``fiber.sleep(0)`` in Lua and ``fiber_sleep(0)`` in C. It could be done in the following way:
a year ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatched colon: Russian, Russian

Reset

Glossary

English English
No related strings found in the glossary.

String information

Flags
read-only
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
string 92