Hello Team,

Any update here.

Thanks & Regards
Ajay Babu Maguluri.


On Thu, Mar 9, 2023 at 6:51 PM Ajay Babu <ajay.b...@6dtech.co.in> wrote:

> Hello Team,
>
> Any update?
>
> Thanks & Regards
> ----------------------------
> Ajay Babu Maguluri
>
>
> On Fri, Jun 24, 2022 at 1:31 PM Gianluca Bonetti <
> gianluca.bone...@gmail.com> wrote:
>
>> Hello
>>
>> Unfortunately reiterating the question won't help.
>> If you have no positive answer in days, it means there's no such features
>> in the making.
>> Also this is a community-based mailing list, it's not a commercial
>> support service and there's no ETA for tickets, just best efforts from the
>> Apache Ignite team who is actually doing an amazing job with development
>> and support.
>>
>> SQL transactions are still marked as beta, so you really shouldn't rely
>> on beta software for your work which seems to be urgent, and not even plan
>> on top of beta features.
>> I think the focus is on the 3.0 release and features with lower user
>> demand will be postponed.
>> Please remember free software is provided "as is" and with no guarantee
>> of "fitness for a particular purpose".
>>
>> Your alternatives are...
>> - switch to key/value approach (widely used, super fast, and rock solid)
>> - if you have extra developer resources, contribute to development
>> - get a support subscription from GridGain (I don't work for that
>> company) and push for developing that feature as a paying customer of the
>> commercially supported version
>> - if you have a wealthy end customer you're developing for, ask them to
>> fund development by GridGain developers, extra developers of your own, or a
>> bountysource
>>
>> I know I am not being particularly helpful on the specific topic, but I
>> just wanted to help in sorting out what options you have out there.
>>
>> Thank you
>> Cheers
>> Gianluca
>>
>> On Fri, 24 Jun 2022 at 08:14, 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 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.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>

Reply via email to