Vyacheslav, Denis,
7 July is too abrupt date. Scope of 2.1 is still too broad, and what is
more important - persistent store has been merged only several days ago. We
need some room for stabilization. I propose the following timeline:
16 July - code freeze
17-21 July - QA
21-24 July - vote and rel
Cos,
I am not aware of performance degradation in regards to Cassandra. AFAIK
there were extensive benchmarking prior to 2.0 release. And in the end 2.0
release had performance not worse than 1.9. If you have more information on
the matter, let's discuss it in the separate thread.
On Thu, Jul 6,
Igniters,
We are still based on Java 7. However, a lot of our users already use Java
8 and some of it's classes. As a result we cannot test certain scenarios.
For examples, there is a bug in *LocalDateTime* type handling [1]. This
class appeared in Java 8, so we cannot test it.
Is it possible to
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2251
Ignite 2.1.2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.2
Alternatively you can review and apply thes
Hi Vladimir,
+1 from me, in addition we will be able to use java8 lambdas in test code.
This make code shorter, and in the same time more expressive.
Please involve me in this activity when it starts.
Best Regards,
Dmitriy Pavlov
чт, 6 июл. 2017 г. в 11:21, Vladimir Ozerov :
> Igniters,
Hi Dmitriy, Denis,
Thank you for your effort to find out solution.
It sound good for me, I have assigned IGNITE-5698 to myself.
Best Regards,
Dmitriy Pavlov
чт, 6 июл. 2017 г. в 2:45, Denis Magda :
> Dmitriy P.,
>
> Does it sound good to you? If yes, please make sure the plugin is
> available
Github user agoncharuk closed the pull request at:
https://github.com/apache/ignite/pull/2249
---
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 sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/2252
logging
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite donnet-hangs-debug
Alternatively you can review an
Hi Vladimir,
One more thing need to be mentioned. Source and target version of java is
determined by module pom file (I am not aware if it can be configured by
main/test scope).
This means tests that requires java 8 compile and target versions should be
placed in separate maven module. This m
Github user nizhikov closed the pull request at:
https://github.com/apache/ignite/pull/2090
---
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 e
Ksenia Rybakova created IGNITE-5707:
---
Summary: Client can't resume streaming even after topology got
stable during load test
Key: IGNITE-5707
URL: https://issues.apache.org/jira/browse/IGNITE-5707
P
Github user kukushal closed the pull request at:
https://github.com/apache/ignite/pull/2223
---
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 e
The idea so far is to have a single system property in configuration that
turns this off completely. I envision that this will be prominently
featured on Ignite website so that everyone who would like to disable it -
can do it in seconds.
Thoughts?
--
Nikita Ivanov
Founder & CTO
GridGain Systems
Igor Sapego created IGNITE-5708:
---
Summary: CPP: Implement Cluster API
Key: IGNITE-5708
URL: https://issues.apache.org/jira/browse/IGNITE-5708
Project: Ignite
Issue Type: New Feature
C
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/2253
IGNITE-GG-12466 Refactor Snapshots API
Moved all possible stuff from ignite to ggprivate
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/2254
IGNITE-5448: SQL: tables(cache) must only return tables belonging to given
cache.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgai
Hello Apache-Ignite team.
Hi,
Welcome to the Ignite community!
Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists
Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
Instructions on how
Alexander Belyak created IGNITE-5709:
Summary: Node stopped on OutOfMemoryException with persistence
Key: IGNITE-5709
URL: https://issues.apache.org/jira/browse/IGNITE-5709
Project: Ignite
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/2255
for testing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.13
Alternatively you can review and apply the
Vasiliy Sisko created IGNITE-5710:
-
Summary: Web console: H2 version in pom file depends from Ignite
version
Key: IGNITE-5710
URL: https://issues.apache.org/jira/browse/IGNITE-5710
Project: Ignite
21 matches
Mail list logo
