We have 4 new blog posts (starting from May 5) this past week.
https://ignite.apache.org/blogs.html
Next week's action will be in Miami at ApacheCon North America. Denis Magda
will have a couple of talk there on May 18:
* Apache Ignite SQL Grid: Hot Blend of Traditional SQL and Swift Data Grid
GitHub user sboikov opened a pull request:
https://github.com/apache/ignite/pull/1932
ignite-gg-8.0.3.ea7
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.3.ea7
Alternatively you can review
Absolutely agree here. I think if we can add getAll() benchmark and run it
with batch sizes of 5 and 10.
Thanks!
--
Yakov Zhdanov, Director R
*GridGain Systems*
www.gridgain.com
2017-05-12 10:48 GMT+03:00 Sergi Vladykin :
> According to our benchmarks Ignite 2.0 is not
Ksenia Rybakova created IGNITE-5209:
---
Summary: "IllegalStateException: Already swapped" error with
offheap_tired indexed cache
Key: IGNITE-5209
URL: https://issues.apache.org/jira/browse/IGNITE-5209
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1933
---
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
Pavel Tupitsyn created IGNITE-5207:
--
Summary: .NET: Non-Int32 enums can't be serialized
Key: IGNITE-5207
URL: https://issues.apache.org/jira/browse/IGNITE-5207
Project: Ignite
Issue Type:
Tolga HOŞGÖR created IGNITE-5208:
Summary: C++ Segfault on Put
Key: IGNITE-5208
URL: https://issues.apache.org/jira/browse/IGNITE-5208
Project: Ignite
Issue Type: Bug
Components:
Sasha,
The idea behind the ticket was as follows: currently, the rebalanceDelay
property is set in CacheConfiguration, which is not very flexible. In
certain circumstances, a user might expect particularly large load on some
segments of the cluster and want to disable rebalancing for those
GitHub user ybabak opened a pull request:
https://github.com/apache/ignite/pull/1934
Ignite 5112
OLS regression example and tests refactoring.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5112
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/1896
---
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 user agoncharuk closed the pull request at:
https://github.com/apache/ignite/pull/42
---
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 closed the pull request at:
https://github.com/apache/ignite/pull/348
---
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 closed the pull request at:
https://github.com/apache/ignite/pull/332
---
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 closed the pull request at:
https://github.com/apache/ignite/pull/343
---
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 closed the pull request at:
https://github.com/apache/ignite/pull/471
---
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
Alexei Scherbakov created IGNITE-5212:
-
Summary: Allow custom affinity for system caches
Key: IGNITE-5212
URL: https://issues.apache.org/jira/browse/IGNITE-5212
Project: Ignite
Issue
GitHub user WilliamDo opened a pull request:
https://github.com/apache/ignite/pull/1935
IGNITE-4324 Check node list is non-empty before query execution
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/WilliamDo/ignite IGNITE-4324
Chris,
After looking at your code, the only slow down that may have occurred
between 1.9 and 2.0 is the actual cache "get(...)" operation. As you may
already know, Ignite 2.0 has moved data off-heap completely, so we do not
cache data in the deserialized form any more, by default. However, you
Folks,
The repository with the donation is ready and available for review:
https://github.com/agoncharuk/ignite/tree/pds-donate
Big and main part of the sources is aggregated in “modules/pds”. The rest, that
connects Apache Ignite memory architecture and SQL engine is under “core” and
19 matches
Mail list logo