Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/921
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/908
---
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 enab
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/236
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/220
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/155
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/94
---
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 en
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/209
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/231
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/259
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/257
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/253
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/254
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/251
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/258
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/250
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/237
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/267
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/295
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/316
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/339
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/288
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/377
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/346
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/358
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/307
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/370
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/344
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/338
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/347
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/637
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/412
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/644
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/474
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/751
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/310
---
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
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/606
---
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
We keep getting a steady stream of users confused by gridName :)
https://issues.apache.org/jira/browse/IGNITE-3207 seems to be abandoned,
should we unassign it?
Pavel.
On Fri, May 27, 2016 at 8:10 PM, Dmitriy Setrakyan
wrote:
> Great! I think I like “instanceName” better, just in case if this
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/131
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/190
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/142
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/150
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/208
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/256
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/247
---
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 ena
I remember couple more thing for 2.0
How about to drop **ignite-scalar** module in Ignite 2.0?
And may be drop **ignite-spark-2.10** module support as of **Spark** 2 is
on **scala 2.11**.
On Tue, Aug 2, 2016 at 11:09 PM, Denis Magda wrote:
> Let’s add this [1] issue to the list because it requi
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/336
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/273
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/322
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/337
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/386
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/354
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/385
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/601
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/603
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/602
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/759
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/779
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/829
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/856
---
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 ena
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/855
---
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 ena
Pavel Tupitsyn created IGNITE-3630:
--
Summary: .NET: Add pure binary mode example with SQL
Key: IGNITE-3630
URL: https://issues.apache.org/jira/browse/IGNITE-3630
Project: Ignite
Issue Type:
So there is no async support for query, therefore we can't support futures
as return type (paragraph 2).
On Thu, Aug 4, 2016 at 6:08 PM, Eduard Shangareev <
eduard.shangar...@gmail.com> wrote:
> I have looked at Querydsl and QbE and I think their support should be
> postponed.
>
Vladimir Ozerov created IGNITE-3631:
---
Summary: IGFS: Metadata co-location doesn't work for PARTITIONED
cache.
Key: IGNITE-3631
URL: https://issues.apache.org/jira/browse/IGNITE-3631
Project: Ignite
Vladimir Ozerov created IGNITE-3632:
---
Summary: IGFS: Use task execution for PARTITIONED cache when
metadata is co-located and current node is not affinity node.
Key: IGNITE-3632
URL: https://issues.apache.org/ji
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/924
Ignite 1.7.1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.1
Alternatively you can review and apply these
Denis,
Thank you very much for your proposed solution, I will reflect it in
issue's comments and implement this check in code. Most likely this
has to be an issue by itself.
However, it all does not answer the main question of this thread - how
do we automatically supply hash codes for newly buil
A new TreeMap gets created when toBinary() is called, and keys
as well as values are converted to binary objects and added to it.
This fails with a CCE because binary objects are not comparable (so
the comparison logic for the keys is lost after conversion).
Not sure whether there are discussions
Alexander Paschenko created IGNITE-3633:
---
Summary: Throw an exception when an object without explicitly set
hash code
Key: IGNITE-3633
URL: https://issues.apache.org/jira/browse/IGNITE-3633
Proj
Hello!
Apache Ignite 1.7.0 release (RC1) has been accepted.
7 "+1" votes received.
Here are the votes received:
- Vladimir Ozerov (binding)
- Nikolay Tikhonov (binding)
- Sergi Vladykin (binding)
- Denis Magda (binding)
- Valentin Kulichenko (binding)
- Alexey Kuznetsov
- Andrey Novikov
Here i
Dmitriy,
I've updated the issue with current state of work and proposal for
data streamer use, please have a look/advise.
- Alex
2016-08-04 21:16 GMT+03:00 Alexander Paschenko
:
> Sergi,
>
> OK, all fixed, there's no trace of update operations in public API now,
> thanks.
> Will update doc and
+1 (binding)
--AG
2016-08-04 5:08 GMT+03:00 Andrey Novikov :
> +1
>
> --
> Andrey
>
> On Thu, Aug 4, 2016 at 2:38 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > -Val
> >
> > On Wed, Aug 3, 2016 at 12:32 PM, Denis Magda
> wrote:
> >
> > > +1 (binding
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/925
IGNITE-3406 - Interceptor and continuous query can get incorrect old â¦
â¦value during rebalancing
- Fix interceptor beforePup() on rebalancing.
You can merge this pull request into
Github user dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/475
---
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 dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/492
---
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 dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/515
---
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 dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/538
---
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 dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/566
---
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
Ignite 1.7.0 successfully released to
https://dist.apache.org/repos/dist/release/ignite/1.7.0/
Maven repository, NuGet, ignite.apache.org site, readme.io pages also
updated.
On Fri, Aug 5, 2016 at 6:22 PM, Pavel Tupitsyn wrote:
> Hello!
>
> Apache Ignite 1.7.0 release (RC1) has been accepted.
Github user dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/685
---
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 dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/722
---
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 dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/737
---
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 dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/868
---
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
As far as I remember we also should update version in master to next
version. 1.8 I think.
5 Авг 2016 г. 23:23 пользователь "Pavel Tupitsyn"
написал:
> Ignite 1.7.0 successfully released to
>
> https://dist.apache.org/repos/dist/release/ignite/1.7.0/
>
> Maven repository, NuGet, ignite.apache.or
Thank you, Alexey, that's also done.
On Fri, Aug 5, 2016 at 7:37 PM, Alexey Kuznetsov
wrote:
> As far as I remember we also should update version in master to next
> version. 1.8 I think.
>
> 5 Авг 2016 г. 23:23 пользователь "Pavel Tupitsyn"
> написал:
>
> > Ignite 1.7.0 successfully released t
GitHub user samaitra opened a pull request:
https://github.com/apache/ignite/pull/926
IGNITE-3263 Affinity function must check for null keys
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/samaitra/ignite IGNITE-3263
Alternative
Also apacheignite.readme.io should points out on 1.7.0
On Fri, Aug 5, 2016 at 7:37 PM, Alexey Kuznetsov
wrote:
> As far as I remember we also should update version in master to next
> version. 1.8 I think.
>
> 5 Авг 2016 г. 23:23 пользователь "Pavel Tupitsyn"
> написал:
>
> > Ignite 1.7.0 succe
Sergey, it does, as I said in my email. Please recheck.
https://apacheignite-cpp.readme.io/ and https://apacheignite-net.readme.io/
also point to 1.7.
On Fri, Aug 5, 2016 at 10:04 PM, Sergey Kozlov wrote:
> Also apacheignite.readme.io should points out on 1.7.0
>
> On Fri, Aug 5, 2016 at 7:37 P
Valentin Kulichenko created IGNITE-3634:
---
Summary: SpringCacheManager should support null values
Key: IGNITE-3634
URL: https://issues.apache.org/jira/browse/IGNITE-3634
Project: Ignite
Valentin Kulichenko created IGNITE-3635:
---
Summary: StackOeverflowError in BinaryObject.toString()
Key: IGNITE-3635
URL: https://issues.apache.org/jira/browse/IGNITE-3635
Project: Ignite
On Fri, Aug 5, 2016 at 2:46 AM, Alexey Kuznetsov
wrote:
> I remember couple more thing for 2.0
>
> How about to drop **ignite-scalar** module in Ignite 2.0?
>
Why?
> And may be drop **ignite-spark-2.10** module support as of **Spark** 2 is
> on **scala 2.11**.
>
I would drop it only if it is
Biao, are you still working on this ticket or should someone else in the
community pick it up?
On Fri, Aug 5, 2016 at 1:53 AM, Pavel Tupitsyn wrote:
> We keep getting a steady stream of users confused by gridName :)
>
> https://issues.apache.org/jira/browse/IGNITE-3207 seems to be abandoned,
> s
http://ignite.apache.org/download.cgi#binaries
Date is wrong。
在 16/8/6 03:10, Pavel Tupitsyn 写道:
Sergey, it does, as I said in my email. Please recheck.
https://apacheignite-cpp.readme.io/ and https://apacheignite-net.readme.io/
also point to 1.7.
On Fri, Aug 5, 2016 at 10:04 PM, Sergey Kozl
On Fri, Aug 5, 2016 at 5:18 PM, 李玉珏@163 <18624049...@163.com> wrote:
> http://ignite.apache.org/download.cgi#binaries
>
> Date is wrong。
>
Fixed.
>
>
> 在 16/8/6 03:10, Pavel Tupitsyn 写道:
>
> Sergey, it does, as I said in my email. Please recheck.
>>
>> https://apacheignite-cpp.readme.io/ and ht
How about we add a property - auto-generate hashCode() in binary
configuration. If set, then we auto-generate the hashCode() every time a
binary object is built.
Thoughts?
On Fri, Aug 5, 2016 at 5:29 AM, Alexander Paschenko <
alexander.a.pasche...@gmail.com> wrote:
> Denis,
>
> Thank you very mu
On Fri, Aug 5, 2016 at 8:24 AM, Alexander Paschenko <
alexander.a.pasche...@gmail.com> wrote:
> Dmitriy,
>
> I've updated the issue with current state of work and proposal for
> data streamer use, please have a look/advise.
>
Responded in the ticket:
https://issues.apache.org/jira/browse/IGNITE-2
Hi Jens,
The main purpose of binary format is to avoid deploying any classes on
server nodes, but with your approach you will need to deploy the comparator
class. You will also not be able to dynamically change this.
All,
This issue becomes more and more critical as more users face with it in
di
Hi Eduard,
This is too much information :)
I think you should create separate tickets for different aspects of Spring
Data integration and use IGNITE-1192 only as an umbrella, because otherwise
it will be flooded by comments. This will allow to implement this
functionality step by step and track
Valentin Kulichenko created IGNITE-3636:
---
Summary: TcpDiscoveryStatusCheckMessage should contain node ID
instead of node instance
Key: IGNITE-3636
URL: https://issues.apache.org/jira/browse/IGNITE-3636
Valentin Kulichenko created IGNITE-3637:
---
Summary: MemoryEventStorageSpi should not be used by default
Key: IGNITE-3637
URL: https://issues.apache.org/jira/browse/IGNITE-3637
Project: Ignite
99 matches
Mail list logo
