Hi Andrey.
Would it make sense to include the following to the list of type
changes that do not require validation?
1. Increasing precision for a type containing a time component (TIME,
DATETIME, TIMESTAMP)
2. Conversion of anything to VARCHAR (with enough capacity)
ср, 14 июн. 2023 г. в 19:27,
Yes, see the root issue [1], but it [2] is happened during the recovery.
> AFAIK all required parts of txn processing are already properly linearized
I see a DCL replacements like IgniteTxAdapter#finishFuture() which call
this into question.
Anyway, this may be the correct statement, but TX proce
Do we have a real reproducer for thread unsafe behavior, which causes data
inconsistency ?
AFAIK all required parts of txn processing are already properly linearized,
and other parts are ready to be processed in parallel (like txn recovery)
пн, 19 июн. 2023 г. в 22:25, Anton Vinogradov :
> Folks,
A new feedback has been added, go to bugyard.io to see all the details...
https://bugyard.io
A new feedback has been added
"This is not working for windows, i get an exception message saying this is
only supported for Linux.
Maybe put a disclaimer message about this only being supported on Lin
