| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
404e999bcffb20d5497161a98f48f566b5245704
|
|
|
|
| |
e6d585180289325f8082f42f85a60478194ba266
|
|
|
|
| |
5c990fdee5899ef1cfcc5429f3631998277cd218
|
|
|
|
| |
d547e94dc63865b96a5cdfbe9866d87b11a57193
|
|
|
|
| |
7ae047ef618cc44d7dd3e817dc27f2336d9e38c3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this PR yt/cpp and yt/yt/core are possible to be built both with Arcadia protobuf (that uses TString as a string) and vanilla protobuf (that uses std::string as a string). To achieve so, a couple of interoperability primitives are introduced.
* `TProtobufString` is an alias to protobuf string type, i.e. it can be `TString` or `std::string` depending on the protobuf implementation.
* `IsVanillaProtobuf` and `IsArcadiaProtobuf` are the constexpr boolean values that allow to check protobuf implementation both in the compile time and runtime.
The most challenging interoperability issue solved here is a string copy between protobuf message and C++ code that has a form of `TString str = msg.str()`. This code works perfect with Arcadia protobuf but does not work with vanilla protobuf. To solve it, a previously introduced primitive `FromProto<TString>` is used. This expression makes the most efficient cast possible between protobuf string and C++ string. Internally, it is just a copy in both cases. Since TString is CoW by default, this expression is almost zero-cost (actually it's just one atomic operation), so no degradation is expected for YTsaurus server builds. The most hot code is handled differently to avoid even atomic operations (see `GetRequestTargetYPath`). In case of vanilla protobuf string is copied, however there are no places in C++ SDK where it might be a problem. If such issues would appear, performance-critial code can be rewritten in `GetRequestTargetYPath`-style.
---
1a6f3e02cb6e83915102c24b73bc8734f6a48e74
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/466
|
|
|
|
| |
febae4e49cd0f600bf21616025f210e99235cfdc
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
default
Executed command: `./erm --verbose --profile update @yatool/prebuilder`
|
|
|
|
| |
Relates: https://st.yandex-team.ru/, https://st.yandex-team.ru/
|
| |
|
|
|
|
|
| |
* Library import 5, delete go dependencies
* Fix yt client
|
| |
|
|
|
|
| |
Update tools: yexport, os-yexport
|
|
|
|
| |
before sending to network
|
|
|
|
|
|
| |
add options
YT-20315: Support retries of cross cell copying
|
|
|
|
|
|
|
|
|
|
|
|
| |
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Fix for https://github.com/ytsaurus/ytsaurus/issues/173
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/174
Co-authored-by: ermolovd <[email protected]>
|
|
|
|
|
| |
This reverts commit 9b45f88f366c2a170ab826922dd6eeaa64ea4192, reversing
changes made to d6dc5a658da5b61fd71e72f1a60479989c5c64c5.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Example
YT_PROXY=https://freud.yt.yandex.net
|
| |
|
|
|
|
|
|
|
|
| |
test with acquire ram buffers
Add test on write with acquiring hard limit on file writer
Implement acquire ram buffers setting for parallel file writer
|
| |
|
|
|
|
|
|
| |
add using http-proxy for reading table from YT
Нам нужна возможность ходить в YT через HTTP proxy для чтения таблиц, используя С++ клиент не из контура Яндекса, к сожалению, сейчас такой возможности нет. В этом ПР черновик изменения, которого нам достаточно
https://a.yandex-team.ru/review/4676436/details - тут это же изменение в YT + коммит с тем, как мы планируем использовать
|
|
|
|
| |
https://clubs.at.yandex-team.ru/arcadia/29404
|
| |
|
|
|
|
| |
https://clubs.at.yandex-team.ru/arcadia/29404
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
---
Pull Request resolved: #93
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
system for the job's user id
* simply set the user name to 'u' + euid
|
|
|
|
| |
After this, a new target libyqlplugin.so appears. in open-source cmake build.
Diff in open-source YDB repo looks like the following: https://paste.yandex-team.ru/f302bdb4-7ef2-4362-91c7-6ca45f329264
|