ydb/yt/cpp/mapreduce/client/retryful_writer_v2.cpp, branch CLI_2.21.0

YT-25104: Align new writer behaviour with the oldest ones

2025-05-20T11:35:08Z

commit_hash:a33872f7bf427339504d82c86c97504eb38757d9

YT-23616: Move RequestWithRetry to common

2025-02-08T17:40:43Z

commit_hash:d85d90291b5eb4cf0c68c9c1c2387124cb9927b2

YT-23616: Rename raw_client to http_client

2025-01-22T06:04:11Z

commit_hash:df330f3a0c0ca36d9bcf801fd96b964f1be6383a

Migrate THolder to std::unique_ptr in yt/cpp/mapreduce internals

2024-12-24T18:37:04Z

commit_hash:99bfa41ffc42ed3622660b15d7ce68802e53f902

[yt/cpp/mapreduce] YT-23616: Move rest of Cypress methods to THttpRawClient

2024-12-15T19:19:07Z

commit_hash:2d705aa0369f1425152547803e0fcf80780e1bf6

yt/cpp/mapreduce: move Get, TryGet, Exists, MultisetAttributes to THttpRawClient

2024-12-13T14:04:18Z

commit_hash:bd2228f98fa92de408ca850f9bc1608fdf99e7f5

Fix more problems with RetryfulWriterV2

2024-04-17T06:45:11Z

404e999bcffb20d5497161a98f48f566b5245704

BufferMemory usage for retryful writer v2

2024-04-12T21:43:22Z

ca66c0e73475f3596f6fb2e4e655f2ec378a71a9

Fix crash in retryful writer v2

2024-04-11T22:37:07Z

d95cdb95b36efff7cbf942996a10ee4ff755bbfc

Support building yt/cpp and yt/yt/core with vanilla protobuf

2024-03-19T11:16:23Z

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` 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