-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 1.2.0 #363
Merged
Merged
Release 1.2.0 #363
Conversation
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
Cartridge 1.2.0 was deprecated a long time ago after 2.x release. Now CI actually doesn't run with cartridge 1.2.0: after [1] we run tests with migrations, which depends on `cartridge >= 2.0.1-1, <3.0.0`, installing latest cartridge 2.x over expected 1.2.0. 1. 4409775
In metrics 0.17.0 cartridge hotreload was migrated to metrics cartridge role. The role must be enabled if we want to work with metrics+cartridge features.
DifferentialOrange
force-pushed
the
DifferentialOrange/release-1.2.0
branch
4 times, most recently
from
June 7, 2023 08:09
718f05a
to
af9cbe8
Compare
Before this patch, we ran coverage tests even when results weren't used in coveralls. Running coverage tests is significantly more expensive (up to 5 times in length).
DifferentialOrange
force-pushed
the
DifferentialOrange/release-1.2.0
branch
2 times, most recently
from
June 7, 2023 09:00
4e176a1
to
bbfb3e5
Compare
Running tests for cartridge roles reload with vshard 0.1.22+ may stuck on old Tarantool versions (1.10.6, 2.2, 2.3, 2.4). The reason is rather unclear (it is somehow related to new vshard retrying utils), but since it concerns out of support versions, it is not worth to inspect it too long or file an issue. ``` main/137/vshard.recovery util.lua:103 E> recovery_f has been failed: .../.rocks/share/tarantool/vshard/storage/init.lua:1268: assertion failed! main/136/vshard.gc util.lua:103 E> gc_bucket_f has been failed: .../.rocks/share/tarantool/vshard/storage/init.lua:2530: assertion failed! ```
DifferentialOrange
force-pushed
the
DifferentialOrange/release-1.2.0
branch
from
June 7, 2023 09:32
bbfb3e5
to
74b9983
Compare
Overview This release add two new flags: `noreturn` to ignore return values excessive transfer and encoding/decoding for insert/replace/etc (performance improvement up to 10% for batch requests) and `fetch_latest_metadata` to force fetching latest space format metadata right after a live migration (performance overhead may be up to 15%). New features * Add `noreturn` option for operations: `insert`, `insert_object`, `insert_many`, `insert_object_many`, `replace`, `replace_object`, `replace_many`, `insert_object_many`, `upsert`, `upsert_object`, `upsert_many`, `upsert_object_many`, `update`, `delete` (#267). Bugfixes * Crud DML operations returning stale schema for metadata generation. Now you may use `fetch_latest_metadata` flag to work with latest schema (#236).
DifferentialOrange
force-pushed
the
DifferentialOrange/release-1.2.0
branch
from
June 7, 2023 11:26
74b9983
to
2bb749d
Compare
GRISHNOV
approved these changes
Jun 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This release add two new flags:
noreturn
to ignore return values excessive transfer and encoding/decoding for insert/replace/etc (performance improvement up to 10% for batch requests) andfetch_latest_metadata
to force fetching latest space format metadata right after a live migration (performance overhead may be up to 15%).New features
noreturn
option for operations:insert
,insert_object
,insert_many
,insert_object_many
,replace
,replace_object
,replace_many
,insert_object_many
,upsert
,upsert_object
,upsert_many
,upsert_object_many
,update
,delete
(Add new flag "return nothing" in options for DML operations #267).Bugfixes
fetch_latest_metadata
flag to work with latest schema (crud.update() may use stale schema for metadata generation #236).