Hello Team, Please update.
1. Any roadmap will be solved in upcoming releases. 2. In case of exception, if we want to re-try any specific exception type will throw, so that will catch and do the re-try specific case. Br, Ajay Babu Maguluri. On Thu, Jun 23, 2022 at 11:56 AM Ajay Babu <ajay.b...@6dtech.co.in> wrote: > Hello Team, > > Please update. > > 1. Any roadmap will be solved in upcoming releases. > 2. In case of exception, if we want to re-try any specific exception > type will throw, so that will catch and do the re-try. > > Br, > Ajay Babu Maguluri. > > > On Wed, Jun 22, 2022 at 11:53 PM Ajay Babu <ajay.b...@6dtech.co.in> wrote: > >> Hi, >> >> Any roadmap will be solved in upcoming releases. >> >> Br >> Ajay Babu Maguluri. >> >> >> On Wed, Jun 22, 2022 at 11:34 PM Николай Ижиков <nizhi...@apache.org> >> wrote: >> >>> Hello. >>> >>> Ignite SQL is not transactional [1] [2] >>> It seems this exception are expected. >>> >>> For transactional updates [3] you should use key-value API. >>> >>> [1] https://ignite.apache.org/docs/latest/sql-reference/transactions >>> [2] https://ignite.apache.org/docs/latest/transactions/mvcc >>> [3] https://ignite.apache.org/docs/latest/key-value-api/transactions >>> >>> 22 июня 2022 г., в 20:59, Ajay Babu <ajay.b...@6dtech.co.in> написал(а): >>> >>> Hello Team, >>> >>> Please update, Will Ignite support this without any exception. >>> >>> Br, >>> Ajay Babu Maguluri, >>> >>> On Wed, Jun 22, 2022 at 6:29 PM Ajay Babu <ajay.b...@6dtech.co.in> >>> wrote: >>> >>>> Hi Stephen, >>>> >>>> Thanks for your reply. >>>> >>>> Yes, I am doing SQL update via IgniteJdbcThinDriver and I am using >>>> Ignite 2.13.x for one of my requirement. I need to maintain cache in Ignite >>>> cluster and some of the keys values will be update concurrently and >>>> selection also happens parallel from multiple jdbc clients. So here I am >>>> facing an issue. >>>> >>>> Br, >>>> Ajay Babu Maguluri. >>>> >>>> >>>> On Wed, Jun 22, 2022 at 6:04 PM Stephen Darlington < >>>> stephen.darling...@gridgain.com> wrote: >>>> >>>>> You don’t give much information about what you’re doing. I’m guessing >>>>> that you’re doing a SQL update from a JDBC connection? Can you add some >>>>> more colour? >>>>> >>>>> On 22 Jun 2022, at 13:29, Ajay Babu <ajay.b...@6dtech.co.in> wrote: >>>>> >>>>> Hi Team, >>>>> >>>>> Please update. >>>>> >>>>> Br, >>>>> Ajay Babu Maguluri. >>>>> >>>>> >>>>> On Tue, Jun 21, 2022 at 1:44 PM Ajay Babu <ajay.b...@6dtech.co.in> >>>>> wrote: >>>>> >>>>>> >>>>>> Hello Team, >>>>>> >>>>>> I have a requirement to keep cache in ignite and that will update >>>>>> frequently and selection also happens parallel, while i am executing >>>>>> queries iam getting, >>>>>> >>>>>> ava.sql.SQLException: Failed to update some keys because they had >>>>>> been modified concurrently [keys=[ROWKEY [idHash=628930863, >>>>>> hash=1637498765, rowkey=6, id=765436]]] >>>>>> at >>>>>> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009) >>>>>> at >>>>>> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234) >>>>>> at >>>>>> org.apache.ignite.internal.jdbc.thin.JdbcThinPreparedStatement.executeWithArguments(JdbcThinPreparedStatement.java:252) >>>>>> at >>>>>> org.apache.ignite.internal.jdbc.thin.JdbcThinPreparedStatement.executeUpdate(JdbcThinPreparedStatement.java:96) >>>>>> at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown >>>>>> Source) >>>>>> at >>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>>>> at java.lang.reflect.Method.invoke(Method.java:498) >>>>>> at >>>>>> org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:118) >>>>>> at com.sun.proxy.$Proxy16.executeUpdate(Unknown Source) >>>>>> >>>>>> Attached config file in attachment. >>>>>> >>>>>> Thanks & Regards >>>>>> Ajay Babu Maguluri. >>>>>> >>>>> >>>>> >>>
