[jira] [Created] (IGNITE-6876) ODBC: Add support for SQL_ATTR_CONNECTION_TIMEOUT

Alexey Popov created IGNITE-6876: Summary: ODBC: Add support for SQL_ATTR_CONNECTION_TIMEOUT Key: IGNITE-6876 URL: https://issues.apache.org/jira/browse/IGNITE-6876 Project: Ignite Issue

[jira] [Created] (IGNITE-6877) Improve behaviour for non-correlated subqueries

Alin Andrei Corodescu created IGNITE-6877: - Summary: Improve behaviour for non-correlated subqueries Key: IGNITE-6877 URL: https://issues.apache.org/jira/browse/IGNITE-6877 Project: Ignite

[jira] [Created] (IGNITE-6880) KNN(k nearest neighbor) algorithm

Yury Babak created IGNITE-6880: -- Summary: KNN(k nearest neighbor) algorithm Key: IGNITE-6880 URL: https://issues.apache.org/jira/browse/IGNITE-6880 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #2951: Ignite-gg13021: NPE on node stop when SSL is used...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/2951 ---

[jira] [Created] (IGNITE-6878) Naive Bayes classifier for ML module

Yury Babak created IGNITE-6878: -- Summary: Naive Bayes classifier for ML module Key: IGNITE-6878 URL: https://issues.apache.org/jira/browse/IGNITE-6878 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #3022: Ignite-1.9.8.b1

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

[jira] [Created] (IGNITE-6884) Implement of tensorFold() and tensorProduct() for vectors and matrices

Yury Babak created IGNITE-6884: -- Summary: Implement of tensorFold() and tensorProduct() for vectors and matrices Key: IGNITE-6884 URL: https://issues.apache.org/jira/browse/IGNITE-6884 Project: Ignite

[jira] [Created] (IGNITE-6882) Introduction of computation graph

Yury Babak created IGNITE-6882: -- Summary: Introduction of computation graph Key: IGNITE-6882 URL: https://issues.apache.org/jira/browse/IGNITE-6882 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #2998: Ignite-gg-13021

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/2998 ---

[jira] [Created] (IGNITE-6879) Support Spring 2.0

Alexey Kukushkin created IGNITE-6879: Summary: Support Spring 2.0 Key: IGNITE-6879 URL: https://issues.apache.org/jira/browse/IGNITE-6879 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6881) More flexible metrics aggregation

Alin Andrei Corodescu created IGNITE-6881: - Summary: More flexible metrics aggregation Key: IGNITE-6881 URL: https://issues.apache.org/jira/browse/IGNITE-6881 Project: Ignite Issue

Re: GA Grid: Request to contribute GA library to Apache Ignite

Yury, Thanks for feedback. I reviewed the Trainer API at: https://github.com/apache/ignite/blob/db7697b17cf6eb94754edb2b5e200655a3610dc1/modules/ml/src/main/java/org/apache/ignite/ml/Trainer.java and also recommend approach that new "GA trainers" should be implemented that will use GA Grid".

[GitHub] ignite pull request #3023: Ignite-gg-12943

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

[jira] [Created] (IGNITE-6883) Distributed sub-query support

Alin Andrei Corodescu created IGNITE-6883: - Summary: Distributed sub-query support Key: IGNITE-6883 URL: https://issues.apache.org/jira/browse/IGNITE-6883 Project: Ignite Issue Type:

[GitHub] ignite pull request #3024: ignite-6866: remove offheap allocation on client ...

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/3024 ignite-6866: remove offheap allocation on client nodes Completely remove offheap from client nodes You can merge this pull request into a Git repository by running: $ git pull

Re: Ignite Enhancement Proposal #6 (Metrics)

Here is the link: [1] https://issues.apache.org/jira/browse/IGNITE-6846 -Val On Mon, Nov 13, 2017 at 4:53 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > One of the users also brought up the issue that we don't have any metrics > for entry processors [1]. Probably, makes

Re: GA Grid: Request to contribute GA library to Apache Ignite

In addition to that, we need to push GA grid through the IP clearance process: http://incubator.apache.org/ip-clearance/ip-clearance-template.html This is how an IP clearance form looked like and process happened when GridGain was donating Ignite persistence:

Re: Ignite Enhancement Proposal #6 (Metrics)

Hi Anton, Thanks for brining this out! The memory metrics really need a serious overhaul. For instance we a missing basic things like: - Bytes used per data region. - Bytes used per cache. - Size of checkpointing buffer. Plus advanced memory metrics will not be harmful: - Space occupied by

[jira] [Created] (IGNITE-6897) Visor doesn't show the list of caches after persistence enabled cluster restart

Valentin Kulichenko created IGNITE-6897: --- Summary: Visor doesn't show the list of caches after persistence enabled cluster restart Key: IGNITE-6897 URL: https://issues.apache.org/jira/browse/IGNITE-6897

Re: Ignite Enhancement Proposal #6 (Metrics)

One of the users also brought up the issue that we don't have any metrics for entry processors [1]. Probably, makes sense to include this into IEP as well. -Val On Mon, Nov 13, 2017 at 4:48 PM, Denis Magda wrote: > Hi Anton, > > Thanks for brining this out! > > The memory

Re: GA Grid: Request to contribute GA library to Apache Ignite

Denis, Ok. It's not clear what stage we are in this process. Do I need to fill out the IP Clearance form here? http://incubator.apache.org/ip-clearance/ip-clearance-template.html If so, I will simply model what was done for Ignite Persistence Store. Also, What about the software grant form?

[jira] [Created] (IGNITE-6885) .NET: Binary serialization performance: eliminate virtual calls on hot path

Pavel Tupitsyn created IGNITE-6885: -- Summary: .NET: Binary serialization performance: eliminate virtual calls on hot path Key: IGNITE-6885 URL: https://issues.apache.org/jira/browse/IGNITE-6885

[jira] [Created] (IGNITE-6890) Proper behavior on ExchangeWorker exits with error

Anton Vinogradov created IGNITE-6890: Summary: Proper behavior on ExchangeWorker exits with error Key: IGNITE-6890 URL: https://issues.apache.org/jira/browse/IGNITE-6890 Project: Ignite

[jira] [Created] (IGNITE-6889) ignite.queue() returns null when queue configuration is null

Alexey Kukushkin created IGNITE-6889: Summary: ignite.queue() returns null when queue configuration is null Key: IGNITE-6889 URL: https://issues.apache.org/jira/browse/IGNITE-6889 Project: Ignite

[GitHub] ignite pull request #2927: IGNITE-6752 JDBC thin: connection property refact...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2927 ---

[jira] [Created] (IGNITE-6886) .NET: Performance: Pre-calculate fieldId in reflective serializer

Pavel Tupitsyn created IGNITE-6886: -- Summary: .NET: Performance: Pre-calculate fieldId in reflective serializer Key: IGNITE-6886 URL: https://issues.apache.org/jira/browse/IGNITE-6886 Project:

[jira] [Created] (IGNITE-6888) Cache involved tables set for statement

Igor Seliverstov created IGNITE-6888: Summary: Cache involved tables set for statement Key: IGNITE-6888 URL: https://issues.apache.org/jira/browse/IGNITE-6888 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6891) Proper behavior on Persistence errors

Anton Vinogradov created IGNITE-6891: Summary: Proper behavior on Persistence errors Key: IGNITE-6891 URL: https://issues.apache.org/jira/browse/IGNITE-6891 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6896) .NET: support Multidimensional Arrays in binary serializer

Alexey Popov created IGNITE-6896: Summary: .NET: support Multidimensional Arrays in binary serializer Key: IGNITE-6896 URL: https://issues.apache.org/jira/browse/IGNITE-6896 Project: Ignite

Re: Fair affinity resurrection with baseline topology

+1 In fact, after implementing this, we will no longer need rendezvous affinity. Why do we need other affinity if we already provided ideal assignment to user ? I suggest hiding affinity function from public API and make available publicly only things like partition count and backup filter,

Re: GA Grid: Request to contribute GA library to Apache Ignite

Turik, >From my point of view our first step is add GA Grid as is into package org.apache.ignite.ml.genetic in ML module. It shouldn't be a problem, but before this we should check that GA Grid fits to our codestyle. So please prepare pull-request with GA Grid. Also if nobody object I will

[GitHub] ignite pull request #3025: Ignite-2.4.1

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

[jira] [Created] (IGNITE-6892) Proper behavior on OOM/IgniteOutOfMemoryException

Anton Vinogradov created IGNITE-6892: Summary: Proper behavior on OOM/IgniteOutOfMemoryException Key: IGNITE-6892 URL: https://issues.apache.org/jira/browse/IGNITE-6892 Project: Ignite

[jira] [Created] (IGNITE-6895) Provide metric to monitor any TX deadlock

Anton Vinogradov created IGNITE-6895: Summary: Provide metric to monitor any TX deadlock Key: IGNITE-6895 URL: https://issues.apache.org/jira/browse/IGNITE-6895 Project: Ignite Issue

[jira] [Created] (IGNITE-6894) Provide metric to monitor Internal threads stuck

Anton Vinogradov created IGNITE-6894: Summary: Provide metric to monitor Internal threads stuck Key: IGNITE-6894 URL: https://issues.apache.org/jira/browse/IGNITE-6894 Project: Ignite

[jira] [Created] (IGNITE-6893) Provide metric to monitor Java Deadlocks

Anton Vinogradov created IGNITE-6893: Summary: Provide metric to monitor Java Deadlocks Key: IGNITE-6893 URL: https://issues.apache.org/jira/browse/IGNITE-6893 Project: Ignite Issue

Ignite Enhancement Proposal #6 (Metrics)

Igniters, As you may know Ignite have a lot of JMX based metric, but to perform more effective grid monitoring some new JMX metrics needs to be implemented. Here's the accumulated list of metrics I'd like to see at nearest Ignite version: Topology - Current topology version - Total server nodes

Re: Fair affinity resurrection with baseline topology

On Mon, Nov 13, 2017 at 7:49 AM, Alexei Scherbakov < alexey.scherbak...@gmail.com> wrote: > +1 > > In fact, after implementing this, we will no longer need rendezvous > affinity. > > Why do we need other affinity if we already provided ideal assignment to > user ? > Because rendezvous is

Re: Problem in Ignite Server When using it with hiredis to Store and retrieve C++ Class Object

Hello, Below is my redis client code through which i'm trying to store multiple C++ Object to Ignite Server after serializing the object in to string using protobuf serialization library. The same code works fine in storing and retrieving for 10lakshs objects with redis server. But the same

Re: Ignite Enhancement Proposal #6 (Metrics)

Thanks, Anton! All makes sense. I was actually under impression that Ignite already provides some of these metrics. Can you please create relevant tickets and add them to the IEP page? Perhaps someone in the community could pick these up. This would be a very nice way to get started with the