[jira] [Created] (IGNITE-5754) Web Console: Web agent should use POST instead of GET to get topology

Alexey Kuznetsov created IGNITE-5754: Summary: Web Console: Web agent should use POST instead of GET to get topology Key: IGNITE-5754 URL: https://issues.apache.org/jira/browse/IGNITE-5754

Upcoming Apache Ignite Events

Folks, Check up our the news page [1]! We’re approaching cool meetups and webinars to be conducted by our community members. Take an action - sign up and attend! And if you have anything to share the world about Ignite reach me out ;) * Webinar: Distributed ACID Transactions in Apache Ignite

Cache Metrics

Hi Experts, I am working on https://issues.apache.org/jira/browse/IGNITE-3495 A few words about this issue: It is about that the process of gathering/updating of cache metrics is inconsistent in some cases. Let's consider the following simple topology which contains only two nodes: first node is

[GitHub] ignite pull request #2299: IGNITE-5753: Memory leak fixed

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2299 IGNITE-5753: Memory leak fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5753 Alternatively you can

[jira] [Created] (IGNITE-5753) CPP: Memory leak on argument cleaning for SqlQuery and SqlFieldsQuery

Igor Sapego created IGNITE-5753: --- Summary: CPP: Memory leak on argument cleaning for SqlQuery and SqlFieldsQuery Key: IGNITE-5753 URL: https://issues.apache.org/jira/browse/IGNITE-5753 Project: Ignite

[GitHub] ignite pull request #2298: IGNITE-5750 Change HMSM format to hh:mm:ss.mmm

GitHub user YevIgn opened a pull request: https://github.com/apache/ignite/pull/2298 IGNITE-5750 Change HMSM format to hh:mm:ss.mmm You can merge this pull request into a Git repository by running: $ git pull https://github.com/YevIgn/ignite ignite-5750 Alternatively you can

[GitHub] ignite pull request #2297: IGNITE-5752 Fixed GridDhtPartitionMap updateSeque...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/2297 IGNITE-5752 Fixed GridDhtPartitionMap updateSequence modifying You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-5752) Fix stale sequence updates for local partition map

Pavel Kovalenko created IGNITE-5752: --- Summary: Fix stale sequence updates for local partition map Key: IGNITE-5752 URL: https://issues.apache.org/jira/browse/IGNITE-5752 Project: Ignite

[jira] [Created] (IGNITE-5751) In TcpCommunicationSpi.createTcpClient U.filterReachable waits all addresses to check if they are reachable

Evgenii Zhuravlev created IGNITE-5751: - Summary: In TcpCommunicationSpi.createTcpClient U.filterReachable waits all addresses to check if they are reachable Key: IGNITE-5751 URL:

[jira] [Created] (IGNITE-5750) Format of uptime for metrics

Alexandr Kuramshin created IGNITE-5750: -- Summary: Format of uptime for metrics Key: IGNITE-5750 URL: https://issues.apache.org/jira/browse/IGNITE-5750 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #2296: Ignite-2.1.3

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/2296 Ignite-2.1.3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.3 Alternatively you can review and apply

[GitHub] ignite pull request #2268: ignite-5597 fixed documentation

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2268 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2295: IgniteCacheP2pUnmarshallingRebalanceErrorTest fix

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2295 IgniteCacheP2pUnmarshallingRebalanceErrorTest fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-5749) SQL: add ANY condition support.

Andrew Mashenkov created IGNITE-5749: Summary: SQL: add ANY condition support. Key: IGNITE-5749 URL: https://issues.apache.org/jira/browse/IGNITE-5749 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5748) Extend JTA test coverage

Ryabov Dmitrii created IGNITE-5748: -- Summary: Extend JTA test coverage Key: IGNITE-5748 URL: https://issues.apache.org/jira/browse/IGNITE-5748 Project: Ignite Issue Type: Test

[GitHub] ignite pull request #2294: ignite-5747

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/2294 ignite-5747 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5747 Alternatively you can review and apply these

[GitHub] ignite pull request #2292: IGNITE-5649: Get meta for the specified cache.

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/2292 IGNITE-5649: Get meta for the specified cache. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-5649 Alternatively you

Re: Apache Ignite 2.1 scope

Folks, As far as I see, branch ignite-2.1 contains all necessary commits. Looks like we are ready to start a vote tomorrow as agreed. On Wed, Jul 12, 2017 at 8:54 PM, Denis Magda wrote: > Cos, > > IMO, If we really want to get a valuable feedback from a wider audience > then

[jira] [Created] (IGNITE-5746) Node mustn't start if memory policy is not configured

Pavel Konstantinov created IGNITE-5746: -- Summary: Node mustn't start if memory policy is not configured Key: IGNITE-5746 URL: https://issues.apache.org/jira/browse/IGNITE-5746 Project: Ignite

[GitHub] ignite pull request #2291: Ignite 5061

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/2291 Ignite 5061 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5061 Alternatively you can review and apply these

[jira] [Created] (IGNITE-5745) Web console: Admin panel - add registration date and ability to filter by it

Alexey Kuznetsov created IGNITE-5745: Summary: Web console: Admin panel - add registration date and ability to filter by it Key: IGNITE-5745 URL: https://issues.apache.org/jira/browse/IGNITE-5745

[GitHub] ignite pull request #2110: Add rebalance enabled flag & tests

Github user abeliak closed the pull request at: https://github.com/apache/ignite/pull/2110 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2290: IGNITE-5382: SQL: Added per-schema connection loo...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/2290 IGNITE-5382: SQL: Added per-schema connection lookup You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5382