Is there anything I can do to associate the cacheevent with the logged in
jdbc client(DBEAVER user) (Can I do something in any of the methods of the
Security Plugin ) .
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Another thing I noticed is that during a update through jdbc client, there
could be 2 kinds of threads acting on it. The 'client-connector' thread and
the 'sys-stripe'. If the client-connector thread completes the transaction
and calls the record, it is able to send a 'cache_put' event with the uui
t; This was discussed in the 'Ignite users' group
>
> http://apache-ignite-users.70518.x6.nabble.com/JDBC-thin-client-incorrect-security-context-td31354.html
>
> And I was advised to continue my conversation here.
>
> Andrei mentions that the uuid associated with the event sho
This was discussed in the 'Ignite users' group
http://apache-ignite-users.70518.x6.nabble.com/JDBC-thin-client-incorrect-security-context-td31354.html
And I was advised to continue my conversation here.
Andrei mentions that the uuid associated with the event should be that of
the jdbc
