[GitHub] ignite pull request #1069: IGNITE-3911 - add support for user defined aggreg...

GitHub user nrTQgc opened a pull request: https://github.com/apache/ignite/pull/1069 IGNITE-3911 - add support for user defined aggregate in H2 SQL Please review and check my pull request You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-3911) Unable to add user defined aggregate to H2

Tolstokulakov Nikolay created IGNITE-3911: - Summary: Unable to add user defined aggregate to H2 Key: IGNITE-3911 URL: https://issues.apache.org/jira/browse/IGNITE-3911 Project: Ignite

Re: Global off-heap memory limit

+1 I'm particularly interested in the use case where I have caches that are created dynamically and in general I don't know in advance how many of them will exist at any point in time. But I do know the total amount of memory I'm willing to make available to the caches. So it would be nice if

Re: want to be Contributer

Welcome to the Ignite community! You should get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here:

Re: Global off-heap memory limit

To my knowledge, in Ignite 2.0 we will have Memory Policies, and multiple caches will be able to reuse the same policy. Since the memory size will be defined at the policy level, it will essentially solve this problem. Am I wrong? D. On Thu, Sep 15, 2016 at 12:15 PM, Igor Rudyak

Re: Global off-heap memory limit

+1 On Thu, Sep 15, 2016 at 12:11 PM, Denis Magda wrote: > +1 > > I’ve faced with such injuries as well and this feature sounds reasonable > for me. > > However, is this going to be supported in the new memory architecture the > community has been working on? Alex G., can

Re: Global off-heap memory limit

+1 I’ve faced with such injuries as well and this feature sounds reasonable for me. However, is this going to be supported in the new memory architecture the community has been working on? Alex G., can you comment? — Denis > On Sep 15, 2016, at 12:07 PM, Valentin Kulichenko >

[jira] [Created] (IGNITE-3910) ODBC: PDO always passes parameters as strings.

Igor Sapego created IGNITE-3910: --- Summary: ODBC: PDO always passes parameters as strings. Key: IGNITE-3910 URL: https://issues.apache.org/jira/browse/IGNITE-3910 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-3909) Hadoop: invalid classloader definition delegation logic.

Vladimir Ozerov created IGNITE-3909: --- Summary: Hadoop: invalid classloader definition delegation logic. Key: IGNITE-3909 URL: https://issues.apache.org/jira/browse/IGNITE-3909 Project: Ignite

[GitHub] ignite pull request #1067: IGNITE-3875: Create separate thread pool for data...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1067 IGNITE-3875: Create separate thread pool for data streamer. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1066: IGNITE-3621 Make GridCacheTtlManager singleton

GitHub user amartianov opened a pull request: https://github.com/apache/ignite/pull/1066 IGNITE-3621 Make GridCacheTtlManager singleton Use single Ttl Cleanup Worker thread for all caches You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1065: IGNITE-3859 IGFS: Support direct PROXY mode invoc...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1065 IGNITE-3859 IGFS: Support direct PROXY mode invocation in method: open You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-3906) Hadoop: add optional envvar to set additional libraries to classpath.

Vladimir Ozerov created IGNITE-3906: --- Summary: Hadoop: add optional envvar to set additional libraries to classpath. Key: IGNITE-3906 URL: https://issues.apache.org/jira/browse/IGNITE-3906 Project:

[jira] [Created] (IGNITE-3905) Optimize RendezvousAffinityFunction

Alexei Scherbakov created IGNITE-3905: - Summary: Optimize RendezvousAffinityFunction Key: IGNITE-3905 URL: https://issues.apache.org/jira/browse/IGNITE-3905 Project: Ignite Issue Type:

[GitHub] ignite pull request #1056: Cluster state and lost partitions handling

Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/1056 --- 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

[GitHub] ignite pull request #1064: EA1

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