[MTCGA]: new failures in builds [3159869] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

[jira] [Created] (IGNITE-11535) AtomicLong cannot be found after creation

Vyacheslav Koptilin created IGNITE-11535: Summary: AtomicLong cannot be found after creation Key: IGNITE-11535 URL: https://issues.apache.org/jira/browse/IGNITE-11535 Project: Ignite

[MTCGA]: new failures in builds [3298550] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

[MTCGA]: new failures in builds [3163283] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

Re: Consistent ID specification from previous random UUID

Igniters, I came across the same issue during development and found no sane workaround for this issue. I believe the solution should be as simple as possible because we are already adding a warning to let users know that it is good to specify a consistent ID in production deployments. As for the

Re: Consistent ID specification from previous random UUID

Hi Igniters, A full description can be found at wiki page https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-SubfoldersGeneration I like the idea of introducing a property like nodeStorageName to specify exactly name of

[jira] [Created] (IGNITE-11534) Partition loss policy is not handled properly for implicit single key transactions

Ivan Pavlukhin created IGNITE-11534: --- Summary: Partition loss policy is not handled properly for implicit single key transactions Key: IGNITE-11534 URL: https://issues.apache.org/jira/browse/IGNITE-11534

Re: I would like to pick up JIRA Ticket IGNITE-11508

Hello! Your JIRA login ARAVINDAREDDY was added to list of contributors, you can assign tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute You can notify me (@ilyak) for review in JIRA once you have anything in Patch Available. Regards, -- Ilya

Re: Review of IGNITE-11521

Hi, I didn't know that IgniteConfiguration#setLocalEventListeners existed, since we followed the documentation at readme.io which only mentions 'Ignite.events().localListen'. We'll try it to see if it works for us. In the meantime I'll expand the JIRA

Re: Review of IGNITE-11521

Hi Lukas, Thank you for your efforts! I am not 100% sure but perhaps IgniteConfiguration#setLocalEventListeners can help in your use case? But added BEFORE_CLUSTER_CONNNECTION lifecycle event can be still valuable. It is good idea to describe implemented approach in jira ticket and how can it be

Review of IGNITE-11521

Hi, this is my first contribution to Apache Ignite. I've created a bug , made a pull request which the TC Bot is happy about

[jira] [Created] (IGNITE-11533) Improve memory usage reporting in the logs

Stanislav Lukyanov created IGNITE-11533: --- Summary: Improve memory usage reporting in the logs Key: IGNITE-11533 URL: https://issues.apache.org/jira/browse/IGNITE-11533 Project: Ignite

[jira] [Created] (IGNITE-11532) Performance trace of executed query

Yury Gerzhedovich created IGNITE-11532: -- Summary: Performance trace of executed query Key: IGNITE-11532 URL: https://issues.apache.org/jira/browse/IGNITE-11532 Project: Ignite Issue

[jira] [Created] (IGNITE-11531) Merge concurrent registrations of the same binary type

Denis Mekhanikov created IGNITE-11531: - Summary: Merge concurrent registrations of the same binary type Key: IGNITE-11531 URL: https://issues.apache.org/jira/browse/IGNITE-11531 Project: Ignite

[jira] [Created] (IGNITE-11530) SQL Index performance monitoring

Yury Gerzhedovich created IGNITE-11530: -- Summary: SQL Index performance monitoring Key: IGNITE-11530 URL: https://issues.apache.org/jira/browse/IGNITE-11530 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-11529) SQL: Deprecate SqlQuery for nodejs platform

Taras Ledkov created IGNITE-11529: - Summary: SQL: Deprecate SqlQuery for nodejs platform Key: IGNITE-11529 URL: https://issues.apache.org/jira/browse/IGNITE-11529 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-11528) SQL: Deprecate SqlQuery for python platform

Taras Ledkov created IGNITE-11528: - Summary: SQL: Deprecate SqlQuery for python platform Key: IGNITE-11528 URL: https://issues.apache.org/jira/browse/IGNITE-11528 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-11527) SQL: Deprecate SqlQuery for php platform

Taras Ledkov created IGNITE-11527: - Summary: SQL: Deprecate SqlQuery for php platform Key: IGNITE-11527 URL: https://issues.apache.org/jira/browse/IGNITE-11527 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-11526) SQL: Deprecate SqlQuery for c++ platform

Taras Ledkov created IGNITE-11526: - Summary: SQL: Deprecate SqlQuery for c++ platform Key: IGNITE-11526 URL: https://issues.apache.org/jira/browse/IGNITE-11526 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-11525) SQL: Deprecate SqlQuery for .NET platform

Taras Ledkov created IGNITE-11525: - Summary: SQL: Deprecate SqlQuery for .NET platform Key: IGNITE-11525 URL: https://issues.apache.org/jira/browse/IGNITE-11525 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-11524) Memory leak caused by executing an jdbc prepared statement

Pavel Vinokurov created IGNITE-11524: Summary: Memory leak caused by executing an jdbc prepared statement Key: IGNITE-11524 URL: https://issues.apache.org/jira/browse/IGNITE-11524 Project: Ignite