Continuous query not transactional ?

Hello team, This is in continuation to these posts on the ignite users http://apache-ignite-users.70518.x6.nabble.com/Continuous-query-not-transactional-td34270.html and http://apache-ignite-users.70518.x6.nabble.com/Lag-before-records-are-visible-after-transaction-commit-tp33787p33861.html

IGNITE-12781 - ache_put event contains the node id instead of the remote_client subject id

Posting this here, as guided in the ignite users group. Hi Team, 1. I noticed that this issue ( https://issues.apache.org/jira/browse/IGNITE-12781) is not resolved in 2.8.1. Could you guide how can we get audit information if a cache record modification is done on dbeaver and the cache_put event

Re: Server Node comes down with : (err) Failed to notify listener: GridDhtTxPrepareFuture Error

>>As a temporary solution you can stop relying on peer class loading for continuous queries and provide the code of remote filters to the classpath of server nodes. Yes.. I was thinking of a solution on similar lines. Thank you for the reply. -- Sent from:

Re: Server Node comes down with : (err) Failed to notify listener: GridDhtTxPrepareFuture Error

Raised this jira : https://issues.apache.org/jira/browse/IGNITE-12784 Observed in 2.7.6. Unable to easily test in 2.8.0 because of other issues. One of them being - http://apache-ignite-users.70518.x6.nabble.com/2-8-0-JDBC-Thin-Client-Unable-to-load-the-tables-via-DBeaver-td31681.html Please

Re: Security Subject of thin client on remote nodes

HI , Created this jira : https://issues.apache.org/jira/browse/IGNITE-12781 regards, Veena. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Server Node comes down with : (err) Failed to notify listener: GridDhtTxPrepareFuture Error

Hi , Did anyone get a chance to look at this ? Summary of the issue I am facing. : We have a 3 node server cluster A 4th node joins as a client with a continuous query on a Table A( Transaction_mode = transactional ). Now If I bring the client down and issue an update to the Table A within

Re: Security Subject of thin client on remote nodes

>>2. Method GridSecurityProcessor#authenticatedSubject returns authenticated *node subject* (from JavaDoc). I dont think that is true. Nothing stops an implementer to return a Remote Client Security Subject. The primary issue is how to link the event which contains the remote node uuid ( but

Server Node comes down with : (err) Failed to notify listener: GridDhtTxPrepareFuture Error

Hi Team, We have a 3 node server cluster A 4th node joins as a client with a continuous query on a Table A( Transaction_mode = transactional ). Now If I bring the client down and issue an update to the Table A within failureDetectionTimeout 3 , I get the following error and */this error

Re: Security Subject of thin client on remote nodes

The biggest blocker is the one I mention here : http://apache-ignite-developers.2346864.n4.nabble.com/JDBC-thin-client-incorrect-security-context-td45929.html -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Security Subject of thin client on remote nodes

Hi Denis, Thank you for working on the security issues w.r.to thin client logins . We plan to use the thin clients extensively in our project , it will really help if the blockers around it are resolved, regards, Veena. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Security Subject of thin client on remote nodes

HI Denis, Ref : https://cwiki.apache.org/confluence/display/IGNITE/IEP-41%3A+Security+Context+of+thin+client+on+remote+nodes How is this method public interface GridSecurityProcessor extends GridProcessor { // Other methods. /** * Gets security context. * * @param

Re: Unable to get the security context

HI Denis, Which version of Apache Ignite are the changes you mention in the comment( security context always not null ) above available with ? In 2.7.6 I do get security context as null in authorize method. regards, Veena. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: JDBC thin client incorrect security context

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/

Re: JDBC thin client incorrect security context

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

JDBC thin client incorrect security context

Hi , Hi , We have built a security and audit plugin for security of our ignite cluster. We are unable to get the right audit information i.e. we are unable to get the right subject for users logged in through dbeaver ( jdbc thin client. ). This is because the subjectid associated with