GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/1070
IGNITE-3858 IGFS: Support direct PROXY mode invocation in methods: create
/ append
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/g
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 https://gith
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
+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 th
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:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
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 wrote:
> +1
>
want to be Contributer
+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 you comment?
>
> —
> Den
+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
> wrote:
>
> Fol
Folks,
I'm seeing more and more requests from users to add an option to specify
the off-heap memory limit globally, for all the caches in total. Currently
we allow this only on per-cache level, which can be not very usable
sometimes.
E.g., imagine that you have 100GB of RAM and two caches with 50
GitHub user ntikhonov opened a pull request:
https://github.com/apache/ignite/pull/1068
ignite-3907
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3907
Alternatively you can review and apply these
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: Bug
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 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 ignite-38
Pavel Tupitsyn created IGNITE-3908:
--
Summary: .NET: Start Ignite automatically in ASP.NET cache provider
Key: IGNITE-3908
URL: https://issues.apache.org/jira/browse/IGNITE-3908
Project: Ignite
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 https://githu
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 https://github.com/gridgain/apach
Nikolay Tikhonov created IGNITE-3907:
Summary: Incorrect initialization CQ when node filter configured
for cache
Key: IGNITE-3907
URL: https://issues.apache.org/jira/browse/IGNITE-3907
Project: Ig
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:
Alexei Scherbakov created IGNITE-3905:
-
Summary: Optimize RendezvousAffinityFunction
Key: IGNITE-3905
URL: https://issues.apache.org/jira/browse/IGNITE-3905
Project: Ignite
Issue Type: Bu
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 is
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 these
22 matches
Mail list logo
