> Then I suppose the behavior you describe should be enabled/disabled by flag.
Yes. This feature will change Ignite behavior.
It will be enabled by the flag.
> How do you plan to implement this?
Sent tx state to the node performing table/index scan and combine both Btree
and tx data there.
> W
Hi Nikolay!
I have a few questions:
Ignite primary use-cases are around OLTP workload which means we deal with
> small and fast transactions that change coupld of entries
I know at least one popular use-case of our clients. Some clients have
pretty complex logic of clearing data. They use Scan
Hello, Igniters.
About decade Ignite 2.x lacks of support of transactions aware queries.
This IEP [1] is tend to fill this gap.
Any comments are welcome.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-125+Transactions+aware+queries
