You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
YTsaurus supports prerequisite transactions, this is a possibility to annotate any Cypress query with a list of transactions and the action (either read or write) will be executed if and only if transaction is still alive.
This method overrides provided option, so in case if client already has some preprequisite transactions they will be overridden by a new list, however the natural logic is to join both lists.
Maybe it's a good idea to make a list of prerequisites not a generic option but a separate list.
The text was updated successfully, but these errors were encountered:
YTsaurus supports prerequisite transactions, this is a possibility to annotate any Cypress query with a list of transactions and the action (either read or write) will be executed if and only if transaction is still alive.
Python SDK supports prerequisite transactions as well, however interface is not perfect. Consider the following example or usage: https://github.com/ytsaurus/ytsaurus/blob/dfcacd4b69f19b59ade7e035d088d2edb079507d/yt/python/yt/wrapper/tests/test_command_params.py#L16C25-L16C58. It seems good (however, I'd prefer an explicit method .with_prerequiste) but it is actually error-prone.
ytsaurus/yt/python/yt/wrapper/client.py
Lines 44 to 48 in dfcacd4
Maybe it's a good idea to make a list of prerequisites not a generic option but a separate list.
The text was updated successfully, but these errors were encountered: