Hi Igniters, I also do not see any reasons against this solution. But I have concern about performance. How can you estimate impact to performance ?
Sincerely, Dmitriy Pavlov чт, 5 апр. 2018 г. в 17:20, Nikolay Izhikov <nizhi...@apache.org>: > +1 from me. > > Let's have this events! > > I think `EVT_USR_TX_*START*` is more convinient name for it. > As far as we have method `IgniteTransctions#txStart` > > В Чт, 05/04/2018 в 16:06 +0300, Anton Vinogradov пишет: > > Igniters, > > > > As far as I know we're working on additional 'label' field for > transactions > > [1]. > > That's great and will be helpful for customers with huge deploymens to > see > > reason of each transaction. > > But, since 'label' is optional field, there is no way to guarantee it > will > > be filled. > > > > I'd like to propose an idea of brand new event EVT_USR_TX_CREATED (local > > transaction created). > > > > Local listener on such event will allow to guarantee tx's 'label' field > > filled, timeout is correct and so on. > > > > Thoughts? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-6827
