Upcoming Apache Ignite Events

[Denis Magda]

Igniters, 

Let me share with you a list of upcoming Apache Ignite events. Don’t hesitate 
and join, especially, if you live not that far.

* Webinar, May 10th, Apache Ignite and Apache Spark for IoT: 
https://www.gridgain.com/company/news/events/gridgain-webinar-apacher-ignitetm-real-time-processing-iot-generated-streaming

* Meetup in London, May 10th, Apache Flink meets Apache Ignite: 
https://www.meetup.com/Apache-Flink-London-Meetup/events/239663941/

*  Conference talk at OSCON, Austin, May 10th: 
https://conferences.oreilly.com/oscon/oscon-tx/public/schedule/detail/60801 

* Meetup in Miami, May 17th, Apache Ignite and Apache Spark for IoT: 
https://www.gridgain.com/company/news/events/miami-hadoop-user-group-may-17

* Two conference talks at ApacheCon and Apache BigData, Miami, May 18th: 
https://apachecon2017.sched.com/event/9zot
https://apachebigdata2017.sched.com/event/A01a?iframe=no

—
Denis

Re: grant contributor access in jira

[Denis Magda]

Hi,

Welcome to the Ignite community!

Added you to JIRA.

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

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

Once you got familiar and were able to run a few examples, you should pick
a Jira ticket you would like to start on. Send an email to the dev list sharing 
your JIRA id, so we can add you as a contributor in Jira.

These are the easy tickets to start with:
https://issues.apache.org/jira/browse/IGNITE-4549?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20status%20%3D%20OPEN

While those are more advanced but appealing:
https://ignite.apache.org/community/contribute.html#pick-ticket

Looking forward to your contributions!

> On May 3, 2017, at 12:23 PM, Shyam kumar guptha  wrote:
> 
> 
> Hi Dev,
> 
> can you plz give me access to the my jira account for ignite project.
> FYI, below  are my details.  
> 
> -- Forwarded message --
> From: >
> Date: Wed, May 3, 2017 at 12:11 PM
> Subject: [jira] Account signup
> To: shyamasp...@gmail.com 
> 
> 
>  
>  
> Account signup
> 
> You have signed up for a JIRA account at: 
> https://issues.apache.org/jira 
> 
> Here are the details of your account:
> Username: shyamaspari
> Email:shyamasp...@gmail.com 
>  
> Full Name:shyam kumar pasupula
>  
> This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)   
>   
> 
> Thanks & Regards,
> Shyam Kumar Pasupula. 

[jira] [Created] (IGNITE-5161) Provide basic Ignite Compute Grid Examples

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5161:
---

 Summary: Provide basic Ignite Compute Grid Examples
 Key: IGNITE-5161
 URL: https://issues.apache.org/jira/browse/IGNITE-5161
 Project: Ignite
  Issue Type: Sub-task
Reporter: Denis Magda
Assignee: Igor Sapego
 Fix For: 2.1


As a part of Ignite Compute release for C++ we need to provide several examples 
to demonstrate basic capabilities.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Apache Ignite 2.0 Documentation

[Denis Magda]

Well, so many stuff that I eventually forgot about RocketMQ integration, sorry 
Roman ;)
Just released the latest doc: 
https://apacheignite-mix.readme.io/docs/rocketmq-streamer

—
Denis

> On May 3, 2017, at 4:00 PM, Denis Magda  wrote:
> 
> Igniters, thanks to all of you who helped documenting 2.0 features! We could 
> complete the documentation just in time and I’ve just released it.
> 
> Just to give you a sense on how many things were added to Ignite 2.0 here is 
> a list of completely new or significantly updated docs:
>   * Page memory: https://apacheignite.readme.io/docs/page-memory
>   * Memory & Cache Metrics: 
> https://apacheignite.readme.io/docs/memory-and-cache-metrics
>   * Eviction policies: https://apacheignite.readme.io/docs/evictions
> 
>   * DDL: https://apacheignite.readme.io/docs/distributed-ddl
> 
>   * Machine Learning Grid (beta): 
> https://apacheignite.readme.io/docs/machine-learning
> 
>   * Renewed Async API: https://apacheignite.readme.io/docs/async-support
>   * Apache Ignite thread pools including the new custom one: 
> https://apacheignite.readme.io/docs/thread-pools
> 
>   * .NET Plugins: https://apacheignite-net.readme.io/docs/plugins
> 
>   * C++ Continuous Queries remote filters: 
> https://apacheignite-cpp.readme.io/docs/continuous-queries#section-remote-filter
> 
>   * Spring Data Integration: 
> https://apacheignite-mix.readme.io/v2.0/docs/spring-data
> 
> And, for the first time we prepare a migration guide for you dear users: 
> https://apacheignite.readme.io/docs/apache-ignite-20
> 
> —
> Denis
> 
>> On Apr 13, 2017, at 6:46 PM, Dmitriy Setrakyan  wrote:
>> 
>> Denis, thanks for tracking the documentation changes! This is the part that
>> usually gets missed by the community.
>> 
>> On Thu, Apr 13, 2017 at 12:46 PM, Denis Magda  wrote:
>> 
>>> Folks,
>>> 
>>> I’ve prepared a list of changes that have to be documented before the
>>> public release of 2.0:
>>> https://issues.apache.org/jira/browse/IGNITE-4960
>>> 
>>> That’s an impressive release and there are some many things to document.
>>> Actually, I’ll try to document the biggest part contacting contributors in
>>> person but still need a help from some of you:
>>> 
>>> * Nikita, Oleg (Machine Learning): https://issues.apache.org/
>>> jira/browse/IGNITE-4964
>>> * Vovan or Alex P. (DDL indexing statements): https://issues.apache.org/
>>> jira/browse/IGNITE-4967
>>> * Vovan (custom thread pools): https://issues.apache.org/
>>> jira/browse/IGNITE-4969
>>> * Vovan or Taras (next gen async API): https://issues.apache.org/
>>> jira/browse/IGNITE-4972
>>> * Val (Hibernate improvements): https://issues.apache.org/
>>> jira/browse/IGNITE-4972
>>> * Pavel (.NET plugin system): https://issues.apache.org/
>>> jira/browse/IGNITE-4973
>>> * Pavel (.NET dynamically registered classes): https://issues.apache.org/
>>> jira/browse/IGNITE-4974
>>> * Igor Sapego (C++ CQ remote filters): https://issues.apache.org/
>>> jira/browse/IGNITE-4976
>>> 
>>> Let’s pull together and accomplish this part of the release together.
>>> 
>>> —
>>> Denis
>>> 
>>> 
> 

Re: Apache Ignite 2.0 Documentation

[Denis Magda]

Igniters, thanks to all of you who helped documenting 2.0 features! We could 
complete the documentation just in time and I’ve just released it.

Just to give you a sense on how many things were added to Ignite 2.0 here is a 
list of completely new or significantly updated docs:
* Page memory: https://apacheignite.readme.io/docs/page-memory
* Memory & Cache Metrics: 
https://apacheignite.readme.io/docs/memory-and-cache-metrics
* Eviction policies: https://apacheignite.readme.io/docs/evictions

* DDL: https://apacheignite.readme.io/docs/distributed-ddl

* Machine Learning Grid (beta): 
https://apacheignite.readme.io/docs/machine-learning

* Renewed Async API: https://apacheignite.readme.io/docs/async-support
* Apache Ignite thread pools including the new custom one: 
https://apacheignite.readme.io/docs/thread-pools

* .NET Plugins: https://apacheignite-net.readme.io/docs/plugins

* C++ Continuous Queries remote filters: 
https://apacheignite-cpp.readme.io/docs/continuous-queries#section-remote-filter

* Spring Data Integration: 
https://apacheignite-mix.readme.io/v2.0/docs/spring-data

And, for the first time we prepare a migration guide for you dear users: 
https://apacheignite.readme.io/docs/apache-ignite-20

—
Denis

> On Apr 13, 2017, at 6:46 PM, Dmitriy Setrakyan  wrote:
> 
> Denis, thanks for tracking the documentation changes! This is the part that
> usually gets missed by the community.
> 
> On Thu, Apr 13, 2017 at 12:46 PM, Denis Magda  wrote:
> 
>> Folks,
>> 
>> I’ve prepared a list of changes that have to be documented before the
>> public release of 2.0:
>> https://issues.apache.org/jira/browse/IGNITE-4960
>> 
>> That’s an impressive release and there are some many things to document.
>> Actually, I’ll try to document the biggest part contacting contributors in
>> person but still need a help from some of you:
>> 
>> * Nikita, Oleg (Machine Learning): https://issues.apache.org/
>> jira/browse/IGNITE-4964
>> * Vovan or Alex P. (DDL indexing statements): https://issues.apache.org/
>> jira/browse/IGNITE-4967
>> * Vovan (custom thread pools): https://issues.apache.org/
>> jira/browse/IGNITE-4969
>> * Vovan or Taras (next gen async API): https://issues.apache.org/
>> jira/browse/IGNITE-4972
>> * Val (Hibernate improvements): https://issues.apache.org/
>> jira/browse/IGNITE-4972
>> * Pavel (.NET plugin system): https://issues.apache.org/
>> jira/browse/IGNITE-4973
>> * Pavel (.NET dynamically registered classes): https://issues.apache.org/
>> jira/browse/IGNITE-4974
>> * Igor Sapego (C++ CQ remote filters): https://issues.apache.org/
>> jira/browse/IGNITE-4976
>> 
>> Let’s pull together and accomplish this part of the release together.
>> 
>> —
>> Denis
>> 
>> 

Re: Ignite ML, next steps (IGNITE-5029)

[ArtemM]

In the initial implementation of foldMap/map for sparse we considered only
nonzero elements. This is problem because it conflicts with behaviour  of
other matrix implementation. For example, if we try to run map (+1) over
sparse identity matrix, we'll get not matrix with 2's on diagonal and other
elements equal to one, but matrix with 2s on diagonal and 0s in other
positions. Also if we try fold (by fold(f) i mean foldMap(f, identity))
sparse identity matrix with min, we'll get 1 instead of 0. I've started
fixing this behaviour in IGNITE-5102. Basic idea for fixing map is to map
default element along with nondefault elements (we'll now have not necessary
zero as default element). For fold the idea is in performing folding n times
with default element (n is count of default element) after folding on
nondefault elements.  Actually this approach requires accumulator function
to be commutative, but it seems that it does not conflict with javadoc for
foldMap (it does not specify any order of folding explicitly, so there is no
order guaranteed and therefore for operation to be well defined, accumulator
should be commutative). Any objections for this?



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-ML-next-steps-IGNITE-5029-tp17096p17411.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[jira] [Created] (IGNITE-5160) C++ Continuous Queries example has to demonstrate the filter usage

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5160:
---

 Summary: C++ Continuous Queries example has to demonstrate the 
filter usage
 Key: IGNITE-5160
 URL: https://issues.apache.org/jira/browse/IGNITE-5160
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Assignee: Igor Sapego
 Fix For: 2.1


The existing continuous queries example [1] has to be extended to the usage of 
a remote filter explained here [2].

[1] 
https://github.com/apache/ignite/blob/master/modules/platforms/cpp/examples/continuous-query-example/src/continuous_query_example.cpp
[2] 
https://apacheignite-cpp.readme.io/docs/continuous-queries#section-remote-filter



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5159) Create DDL Example

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5159:
---

 Summary: Create DDL Example
 Key: IGNITE-5159
 URL: https://issues.apache.org/jira/browse/IGNITE-5159
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Assignee: Vladimir Ozerov
 Fix For: 2.1


We need to create a DDL example(s) that will demonstrate the following:
- caches creation and removal using CREATE and DROP table commands.
- indexes creation and removal using CREATE and DROP index commands.

If CREATE SCHEME is supported by 2.1 then its usage should be demonstrated as 
well.

The example(s) has to be placed into new "sqlgrid" directory of the examples. 
`CacheQueryExample` and `CacheQueryDmlExample` have to be moved there as well. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

grant contributor access in jira

[Shyam kumar guptha]

Hi Dev,

can you plz give me access to the my jira account for ignite project.
FYI, below  are my details.

-- Forwarded message --
From: 
Date: Wed, May 3, 2017 at 12:11 PM
Subject: [jira] Account signup
To: shyamasp...@gmail.com




Account signup

You have signed up for a JIRA account at:
https://issues.apache.org/jira

Here are the details of your account:
Username: shyamaspari
Email: shyamasp...@gmail.com
Full Name: shyam kumar pasupula

This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[image: Atlassian logo]

Thanks & Regards,
Shyam Kumar Pasupula.

[GitHub] ignite pull request #1903: IGNITE-5109 Refactoring for SparseDistributedMatr...

[ybabak]

Github user ybabak closed the pull request at:

https://github.com/apache/ignite/pull/1903


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5155) Need to improve stats dump on exchange timeout

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-5155:
-

 Summary: Need to improve stats dump on exchange timeout
 Key: IGNITE-5155
 URL: https://issues.apache.org/jira/browse/IGNITE-5155
 Project: Ignite
  Issue Type: Improvement
Reporter: Yakov Zhdanov
Assignee: Stanilovsky Evgeny
 Fix For: 2.1


Currently, on large topologies info dumped on "Failed to wait for partition map 
exchange" 
(org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java:1713)
 floods the log and we need to reduce information dumped.

1. Reduce output for exchange futures that are already done. Keep event, 
topology version, servers count, clients count (more?)
2. Do not dump the whole communication stats, but send message to exchange 
coordinator, ask for its status and for number of messages received and for 
acked messages from local node.
3. we can think of sending new message from cache node to coordinator that may 
be a sign of a problem on that node (e.g. unreleased tx locks or still renting 
partitions) and coordinator may include this info to a status thus every Ignite 
node may point to a problem node in the logs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5154) CPP: Add remote filter to continuous queries C++ example.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-5154:
---

 Summary: CPP: Add remote filter to continuous queries C++ example.
 Key: IGNITE-5154
 URL: https://issues.apache.org/jira/browse/IGNITE-5154
 Project: Ignite
  Issue Type: Task
  Components: platforms
Affects Versions: 1.9
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.1


As we have added support for the remote filters for Ignite C++ (IGNITE-3575), 
we now need to modify continuous queries C++ example by adding remote filter to 
it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1903: IGNITE-5109 Refactoring for SparseDistributedMatr...

[ybabak]

GitHub user ybabak opened a pull request:

https://github.com/apache/ignite/pull/1903

IGNITE-5109 Refactoring for SparseDistributedMatrix:

Use one cache for all instances of SparseDistributedMatrix.

Also added some tests and fixed get() and destroy() behavior for 
SparseDistributedMatrix.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5109

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1903.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1903


commit c42f68fb1bb574f5299364152de1655a2ef20ce6
Author: Yury Babak 
Date:   2017-05-02T10:55:06Z

IGNITE-5109 Refactoring for SparseDistributedMatrix:
  WIP

commit 5f24345b28c30a65f29100a4708ed36fa5199c49
Author: Yury Babak 
Date:   2017-05-02T11:25:31Z

IGNITE-5109 Refactoring for SparseDistributedMatrix:
  WIP

commit c4a44e1a9732456b57942257f89d2a45e16e6f94
Author: Yury Babak 
Date:   2017-05-03T15:16:46Z

IGNITE-5109 Refactoring for SparseDistributedMatrix:
  call get from remote node in case we don't have this entry in local node.

commit a9872a574ab3fb36f9695a0a2544dff67774282e
Author: Yury Babak 
Date:   2017-05-03T15:48:08Z

IGNITE-5109 Refactoring for SparseDistributedMatrix:
  fix SparseDistributedMatrix.destroy() behaviour
  added testCacheBehaviour




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[RESULT] [VOTE] Apache Ignite 2.0.0 Release (RC2)

[Denis Magda]

Igniters,

Apache Ignite 2.0.0 release (RC2) has been accepted.

8 "+1" votes received:

- Vladimir Ozerov (binding)
- Valentin Kulichenko (binding)
- Alexey Kuznetsov (binding)
- Sergi Vladykin (binding)
- Nikolai Tikhonov (binding)
- Anton Vinogradov (binding)
- Pavel Tupitsyn (binding)
- Denis Magda (binding)

Vote thread:

http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-0-0-RC2-td17353.html

Ignite 2.0.0 will be released shortly!

Re: partitions exchange protocol details question

[Dmitry Pavlov]

Hi, Aleksey,

empty remaining set
(org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture#remaining)
is the mandatory condition of sendAllPartitions() to be activated.

When coordinator receives single partition message (
GridDhtPartitionsSingleMessage), it removes one node from remaining set.
The same is true for node left message.

Best Regards,
Dmitry Pavlov

ср, 3 мая 2017 г. в 19:10, ALEKSEY KUZNETSOV :

> Hi, Igntrs! When processing single partitions message in
> GridDhtPartitionsExchangeFuture#processMessage() then , coordinator could
> answer with GridDhtPartitionsFullMessage
> from sendAllPartitions.
> But the field GridDhtPartitionsExchangeFuture#remaining must be empty in
> this case.
>
> I wounder, how could it be empty in case if "remaining" held 2 nodes, or
> more ?
>
>
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

Re: [VOTE] Apache Ignite 2.0.0 RC2

[Denis Magda]

+1 (binding)

—
Denis

> On May 3, 2017, at 6:34 AM, Pavel Tupitsyn  wrote:
> 
> Rishi, yes, this vote should be closed in a couple of hours and then
> release happens.
> 
> On Wed, May 3, 2017 at 3:27 PM, Rishi Yagnik  wrote:
> 
>> Hello Igniters,
>> 
>> Are we releasing Ignite 2.0 this week ? OR any time soon..
>> 
>> On Tue, May 2, 2017 at 6:44 AM, Pavel Tupitsyn 
>> wrote:
>> 
>>> +1
>>> 
>>> Verified Ignite.NET:
>>> * Build from sources
>>> * Run examples
>>> * Run examples from binary package
>>> * Run LINQPad examples
>>> * Install NuGet package, start node
>>> 
>>> On Tue, May 2, 2017 at 12:50 PM, Anton Vinogradov <
>>> avinogra...@gridgain.com>
>>> wrote:
>>> 
 +1 binding
 
 On Tue, May 2, 2017 at 10:44 AM, Nikolai Tikhonov <
>> ntikho...@apache.org>
 wrote:
 
> +1 binding
> 
> On Tue, May 2, 2017 at 10:42 AM, Sergi Vladykin <
 sergi.vlady...@gmail.com>
> wrote:
> 
>> +1 binding
>> 
>> Sergi
>> 
>> 2017-05-02 10:31 GMT+03:00 Alexey Kuznetsov >> :
>> 
>>> Download zip with sorces: OK
>>> Build: mvn clean package -DskipTests -Dmaven.javadoc.skip=true:
>> OK
>>> Build Web console from sources: OK
>>> Build Web agent  from sources: OK
>>> Start node: OK
>>> Start Web Console locally: OK
>>> Start Web agent: OK
>>> Web agent connected to node and shown in Web Console: OK
>>> 
>>> +1 (binding)
>>> 
>>> On Tue, May 2, 2017 at 2:31 AM, Valentin Kulichenko <
>>> valentin.kuliche...@gmail.com> wrote:
>>> 
 +1
 
 On Mon, May 1, 2017 at 3:12 PM Vladimir Ozerov <
 voze...@gridgain.com
>> 
 wrote:
 
> +1
> 
> 30 апр. 2017 г. 17:46 пользователь "Denis Magda" <
> dma...@apache.org>
> написал:
> 
>> Igniters!
>> 
>> We have uploaded a 2.0.0 release candidate to
>> https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc2/ <
>> https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc2/>
>> 
>> Git tag name is
>> 2.0.0-rc2
>> 
>> This release includes the following changes:
>> 
>> Ignite:
>> * Introduced new page memory architecture.
>> * Machine Learning beta: distributed algebra support for
>>> dense
> and
 sparse
>> data sets.
>> * Reworked and simplified API for asynchronous operations.
>> * Custom thread pool executors for compute tasks.
>> * Removed CLOCK mode in ATOMIC cache.
>> * Deprecated schema-import utility in favor of Web Console.
>> * Integration with Spring Data.
>> * Integration with Hibernate 5.
>> * Integration with RocketMQ.
>> * Integration with ZeroMQ.
>> * SQL: CREATE INDEX and DROP INDEX commands.
>> * SQL: Ability to execute queries over specific set of
> partitions.
>> * SQL: Improved REPLICATED cache support.
>> * SQL: Updated H2 version to 1.4.195.
>> * SQL: Improved performance of MIN/MAX aggregate functions.
>> * ODBC: Added Time data type support.
>> * Massive performance improvements.
>> 
>> Ignite.NET :
>> * Custom plugin API.
>> * Generic cache store.
>> * Binary types now can be registered dynamically.
>> * LINQ: join, "contains" and DateTime property support.
>> 
>> Ignite CPP:
>> * Implemented Cache::Invoke.
>> * Added remote filters support to continuous queries.
>> 
>> Ignite Web Console:
>> * Multi-cluster support.
>> * Possibility to configure Kubernetes IP finder.
>> * EnforceJoinOrder option on Queries screen.
>> 
>> Complete list of closed issues:
>> https://issues.apache.org/jira/issues/?jql=project%20%
 3D%20IGNITE%20AND%
>> 20fixVersion%20%3D%202.0%20AND%20(status%20%3D%
>> 20closed%20or%20status%20%3D%20resolved) <
>> https://issues.apache.org/
>> jira/issues/?jql=project%20%3D%20IGNITE%20AND%
 20fixVersion%20%3D%202.0%
>> 20AND%20(status%20%3D%20closed%20or%20status%20%3D%
 20resolved)>
>> 
>> DEVNOTES
>> https://git-wip-us.apache.org/
>> repos/asf?p=ignite.git;a=blob_
>> plain;f=DEVNOTES.txt;hb=refs/tags/2.0.0-rc2 <
>>> https://git-wip-us.apache
 .
>> org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=
>> refs/tags/2.0.0-rc1>
>> 
>> RELEASENOTES
>> https://git-wip-us.apache.org/
>> repos/asf?p=ignite.git;a=blob_
>> plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.0.0-rc2 <
>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=
>> blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.0.0-rc1>

[jira] [Created] (IGNITE-5153) CPP: BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vyacheslav Daradur (JIRA)]

Vyacheslav Daradur created IGNITE-5153:
--

 Summary: CPP: BinaryMarshaller should write ints in "varint" 
encoding where it makes sense
 Key: IGNITE-5153
 URL: https://issues.apache.org/jira/browse/IGNITE-5153
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: 2.0
Reporter: Vyacheslav Daradur
 Fix For: 2.1


Need to implement IGNITE-5097



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

partitions exchange protocol details question

[ALEKSEY KUZNETSOV]

Hi, Igntrs! When processing single partitions message in
GridDhtPartitionsExchangeFuture#processMessage() then , coordinator could
answer with GridDhtPartitionsFullMessage
from sendAllPartitions.
But the field GridDhtPartitionsExchangeFuture#remaining must be empty in
this case.

I wounder, how could it be empty in case if "remaining" held 2 nodes, or
more ?


-- 

*Best Regards,*

*Kuznetsov Aleksey*

[jira] [Created] (IGNITE-5152) .NET: BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vyacheslav Daradur (JIRA)]

Vyacheslav Daradur created IGNITE-5152:
--

 Summary: .NET: BinaryMarshaller should write ints in "varint" 
encoding where it makes sense
 Key: IGNITE-5152
 URL: https://issues.apache.org/jira/browse/IGNITE-5152
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: 2.0
Reporter: Vyacheslav Daradur
 Fix For: 2.1


Need to implement IGNITE-5097



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1902: IGNITE-5097

[daradurvs]

GitHub user daradurvs opened a pull request:

https://github.com/apache/ignite/pull/1902

IGNITE-5097



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/daradurvs/ignite ignite-5097

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1902.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1902


commit 8156af3f7c9d2e05bda0dd19522af1418987886a
Author: Vyacheslav Daradur 
Date:   2017-04-28T11:11:29Z

ignite-5097: wip

commit 49f9019abfc495fc5ffaf8fe53302e8de735489e
Author: Vyacheslav Daradur 
Date:   2017-04-28T13:47:10Z

ignite-5097: writing string with varint was implemented

commit 9907d647dce33413bd1e3cedeb1efa6bdf4b8dd9
Author: Vyacheslav Daradur 
Date:   2017-04-28T13:55:10Z

ignite-5097: writing enum ordinals in varint was implemented

commit 6a7349a50e173ac964ac60e2b89da272c213c293
Author: Vyacheslav Daradur 
Date:   2017-04-28T14:23:32Z

ignite-5097: writing of decimal scale and bytes array length in varint 
format was implemented

commit c3ee1e2d54ba428a5acd7007ca309089849a877d
Author: Vyacheslav Daradur 
Date:   2017-05-02T14:44:46Z

ignite-5097: writing array/collection/map lengths in varint encoding was 
implemented

commit fba5e97ed7515718d2d87573b0059d14ea61d01e
Author: Vyacheslav Daradur 
Date:   2017-05-03T08:30:24Z

ignite-5097: refactoring

commit 6166519ed06a1d30da15046792e93a15f9bde528
Author: Vyacheslav Daradur 
Date:   2017-05-03T11:51:04Z

ignite-5097: refactoring; tests for sizeof-methods were added

commit d75dda28559926db1422b2c2f28c6b8d32290c01
Author: Vyacheslav Daradur 
Date:   2017-05-03T12:29:53Z

ignite-5097: fixes

commit 9707585a3c2b82fb03e460eee6a49b0c920acc93
Author: Vyacheslav Daradur 
Date:   2017-05-03T15:38:24Z

ignite-5097: fixes part 2




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5151) Add some warning when offheap eviction occurs

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-5151:
---

 Summary: Add some warning when offheap eviction occurs
 Key: IGNITE-5151
 URL: https://issues.apache.org/jira/browse/IGNITE-5151
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.0
Reporter: Ksenia Rybakova


Currently if offheap eviction occurs we are silently losing data. It whould be 
helpful to have some warning in log as it's done for onheap eviction.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5150) Allocated memory pages count is incorrect during load test

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-5150:
---

 Summary: Allocated memory pages count is incorrect during load test
 Key: IGNITE-5150
 URL: https://issues.apache.org/jira/browse/IGNITE-5150
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Ksenia Rybakova


Load test config:
- CacheRandomOpearion benchmark
- 1 server (-Xms4g -Xmx4g)
- 1 client (-Xms4g -Xmx4g)
- 1 cache with following config
{noformat}

































{noformat}
- preloaded data: 40M entries
- backup count: 0
- memory config:
{noformat}



 
 
 
 
























{noformat}

40M entries consume about 4Gb offheap memory. It might be proved by [[top]] 
command (RES value - JVM memory = 8Gb - 4Gb) or by summing all "Allocated next 
memory segment" printed in server log.

After all data preloaded metrics show the following:
{noformat}
[18:37:18,152][INFO ][grid-timeout-worker-#23%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=dc009e3c, name=null, uptime=00:02:10:102]
^-- H/N/C [hosts=2, nodes=2, CPUs=32]
^-- CPU [cur=19.53%, avg=11.99%, GC=0.03%]
^-- PageMemory [pages=22527667]
^-- Heap [used=238MB, free=94.17%, comm=4096MB]
^-- Non heap [used=40MB, free=68.18%, comm=45MB]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=10, qSize=0]
^-- Outbound messages queue [size=0]
{noformat}

pages=22527667 seems to be wrong, otherwise offheap memory size would be 
22527667 * 2KB = about 43Gb. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Apache Ignite 2.0.0 RC2

[Pavel Tupitsyn]

Rishi, yes, this vote should be closed in a couple of hours and then
release happens.

On Wed, May 3, 2017 at 3:27 PM, Rishi Yagnik  wrote:

> Hello Igniters,
>
> Are we releasing Ignite 2.0 this week ? OR any time soon..
>
> On Tue, May 2, 2017 at 6:44 AM, Pavel Tupitsyn 
> wrote:
>
> > +1
> >
> > Verified Ignite.NET:
> > * Build from sources
> > * Run examples
> > * Run examples from binary package
> > * Run LINQPad examples
> > * Install NuGet package, start node
> >
> > On Tue, May 2, 2017 at 12:50 PM, Anton Vinogradov <
> > avinogra...@gridgain.com>
> > wrote:
> >
> > > +1 binding
> > >
> > > On Tue, May 2, 2017 at 10:44 AM, Nikolai Tikhonov <
> ntikho...@apache.org>
> > > wrote:
> > >
> > > > +1 binding
> > > >
> > > > On Tue, May 2, 2017 at 10:42 AM, Sergi Vladykin <
> > > sergi.vlady...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1 binding
> > > > >
> > > > > Sergi
> > > > >
> > > > > 2017-05-02 10:31 GMT+03:00 Alexey Kuznetsov  >:
> > > > >
> > > > > > Download zip with sorces: OK
> > > > > > Build: mvn clean package -DskipTests -Dmaven.javadoc.skip=true:
> OK
> > > > > > Build Web console from sources: OK
> > > > > > Build Web agent  from sources: OK
> > > > > > Start node: OK
> > > > > > Start Web Console locally: OK
> > > > > > Start Web agent: OK
> > > > > > Web agent connected to node and shown in Web Console: OK
> > > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > On Tue, May 2, 2017 at 2:31 AM, Valentin Kulichenko <
> > > > > > valentin.kuliche...@gmail.com> wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > On Mon, May 1, 2017 at 3:12 PM Vladimir Ozerov <
> > > voze...@gridgain.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > 30 апр. 2017 г. 17:46 пользователь "Denis Magda" <
> > > > dma...@apache.org>
> > > > > > > > написал:
> > > > > > > >
> > > > > > > > > Igniters!
> > > > > > > > >
> > > > > > > > > We have uploaded a 2.0.0 release candidate to
> > > > > > > > > https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc2/ <
> > > > > > > > > https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc2/>
> > > > > > > > >
> > > > > > > > > Git tag name is
> > > > > > > > > 2.0.0-rc2
> > > > > > > > >
> > > > > > > > > This release includes the following changes:
> > > > > > > > >
> > > > > > > > > Ignite:
> > > > > > > > > * Introduced new page memory architecture.
> > > > > > > > > * Machine Learning beta: distributed algebra support for
> > dense
> > > > and
> > > > > > > sparse
> > > > > > > > > data sets.
> > > > > > > > > * Reworked and simplified API for asynchronous operations.
> > > > > > > > > * Custom thread pool executors for compute tasks.
> > > > > > > > > * Removed CLOCK mode in ATOMIC cache.
> > > > > > > > > * Deprecated schema-import utility in favor of Web Console.
> > > > > > > > > * Integration with Spring Data.
> > > > > > > > > * Integration with Hibernate 5.
> > > > > > > > > * Integration with RocketMQ.
> > > > > > > > > * Integration with ZeroMQ.
> > > > > > > > > * SQL: CREATE INDEX and DROP INDEX commands.
> > > > > > > > > * SQL: Ability to execute queries over specific set of
> > > > partitions.
> > > > > > > > > * SQL: Improved REPLICATED cache support.
> > > > > > > > > * SQL: Updated H2 version to 1.4.195.
> > > > > > > > > * SQL: Improved performance of MIN/MAX aggregate functions.
> > > > > > > > > * ODBC: Added Time data type support.
> > > > > > > > > * Massive performance improvements.
> > > > > > > > >
> > > > > > > > > Ignite.NET :
> > > > > > > > > * Custom plugin API.
> > > > > > > > > * Generic cache store.
> > > > > > > > > * Binary types now can be registered dynamically.
> > > > > > > > > * LINQ: join, "contains" and DateTime property support.
> > > > > > > > >
> > > > > > > > > Ignite CPP:
> > > > > > > > > * Implemented Cache::Invoke.
> > > > > > > > > * Added remote filters support to continuous queries.
> > > > > > > > >
> > > > > > > > > Ignite Web Console:
> > > > > > > > > * Multi-cluster support.
> > > > > > > > > * Possibility to configure Kubernetes IP finder.
> > > > > > > > > * EnforceJoinOrder option on Queries screen.
> > > > > > > > >
> > > > > > > > > Complete list of closed issues:
> > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > > > > > 3D%20IGNITE%20AND%
> > > > > > > > > 20fixVersion%20%3D%202.0%20AND%20(status%20%3D%
> > > > > > > > > 20closed%20or%20status%20%3D%20resolved) <
> > > > > https://issues.apache.org/
> > > > > > > > > jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > > > > > > 20fixVersion%20%3D%202.0%
> > > > > > > > > 20AND%20(status%20%3D%20closed%20or%20status%20%3D%
> > > 20resolved)>
> > > > > > > > >
> > > > > > > > > DEVNOTES
> > > > > > > > > https://git-wip-us.apache.org/
> repos/asf?p=ignite.git;a=blob_
> > > > > > > > > plain;f=DEVNOTES.txt;hb=refs/tags/2.0.0-rc2 <
> > > > > > https://git-wip-us.apache
> > > > > > 

[GitHub] ignite pull request #1901: Ignite 4862 mux

[iveselovskiy]

GitHub user iveselovskiy opened a pull request:

https://github.com/apache/ignite/pull/1901

Ignite 4862 mux



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4862-mux

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1901.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1901






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1897: IGNITE-5132: Fixed PutGet example.

[isapego]

Github user isapego closed the pull request at:

https://github.com/apache/ignite/pull/1897


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Apache Ignite 2.0.0 RC2

[Rishi Yagnik]

Hello Igniters,

Are we releasing Ignite 2.0 this week ? OR any time soon..

On Tue, May 2, 2017 at 6:44 AM, Pavel Tupitsyn  wrote:

> +1
>
> Verified Ignite.NET:
> * Build from sources
> * Run examples
> * Run examples from binary package
> * Run LINQPad examples
> * Install NuGet package, start node
>
> On Tue, May 2, 2017 at 12:50 PM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > +1 binding
> >
> > On Tue, May 2, 2017 at 10:44 AM, Nikolai Tikhonov 
> > wrote:
> >
> > > +1 binding
> > >
> > > On Tue, May 2, 2017 at 10:42 AM, Sergi Vladykin <
> > sergi.vlady...@gmail.com>
> > > wrote:
> > >
> > > > +1 binding
> > > >
> > > > Sergi
> > > >
> > > > 2017-05-02 10:31 GMT+03:00 Alexey Kuznetsov :
> > > >
> > > > > Download zip with sorces: OK
> > > > > Build: mvn clean package -DskipTests -Dmaven.javadoc.skip=true: OK
> > > > > Build Web console from sources: OK
> > > > > Build Web agent  from sources: OK
> > > > > Start node: OK
> > > > > Start Web Console locally: OK
> > > > > Start Web agent: OK
> > > > > Web agent connected to node and shown in Web Console: OK
> > > > >
> > > > > +1 (binding)
> > > > >
> > > > > On Tue, May 2, 2017 at 2:31 AM, Valentin Kulichenko <
> > > > > valentin.kuliche...@gmail.com> wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > On Mon, May 1, 2017 at 3:12 PM Vladimir Ozerov <
> > voze...@gridgain.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > 30 апр. 2017 г. 17:46 пользователь "Denis Magda" <
> > > dma...@apache.org>
> > > > > > > написал:
> > > > > > >
> > > > > > > > Igniters!
> > > > > > > >
> > > > > > > > We have uploaded a 2.0.0 release candidate to
> > > > > > > > https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc2/ <
> > > > > > > > https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc2/>
> > > > > > > >
> > > > > > > > Git tag name is
> > > > > > > > 2.0.0-rc2
> > > > > > > >
> > > > > > > > This release includes the following changes:
> > > > > > > >
> > > > > > > > Ignite:
> > > > > > > > * Introduced new page memory architecture.
> > > > > > > > * Machine Learning beta: distributed algebra support for
> dense
> > > and
> > > > > > sparse
> > > > > > > > data sets.
> > > > > > > > * Reworked and simplified API for asynchronous operations.
> > > > > > > > * Custom thread pool executors for compute tasks.
> > > > > > > > * Removed CLOCK mode in ATOMIC cache.
> > > > > > > > * Deprecated schema-import utility in favor of Web Console.
> > > > > > > > * Integration with Spring Data.
> > > > > > > > * Integration with Hibernate 5.
> > > > > > > > * Integration with RocketMQ.
> > > > > > > > * Integration with ZeroMQ.
> > > > > > > > * SQL: CREATE INDEX and DROP INDEX commands.
> > > > > > > > * SQL: Ability to execute queries over specific set of
> > > partitions.
> > > > > > > > * SQL: Improved REPLICATED cache support.
> > > > > > > > * SQL: Updated H2 version to 1.4.195.
> > > > > > > > * SQL: Improved performance of MIN/MAX aggregate functions.
> > > > > > > > * ODBC: Added Time data type support.
> > > > > > > > * Massive performance improvements.
> > > > > > > >
> > > > > > > > Ignite.NET :
> > > > > > > > * Custom plugin API.
> > > > > > > > * Generic cache store.
> > > > > > > > * Binary types now can be registered dynamically.
> > > > > > > > * LINQ: join, "contains" and DateTime property support.
> > > > > > > >
> > > > > > > > Ignite CPP:
> > > > > > > > * Implemented Cache::Invoke.
> > > > > > > > * Added remote filters support to continuous queries.
> > > > > > > >
> > > > > > > > Ignite Web Console:
> > > > > > > > * Multi-cluster support.
> > > > > > > > * Possibility to configure Kubernetes IP finder.
> > > > > > > > * EnforceJoinOrder option on Queries screen.
> > > > > > > >
> > > > > > > > Complete list of closed issues:
> > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > > > > 3D%20IGNITE%20AND%
> > > > > > > > 20fixVersion%20%3D%202.0%20AND%20(status%20%3D%
> > > > > > > > 20closed%20or%20status%20%3D%20resolved) <
> > > > https://issues.apache.org/
> > > > > > > > jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > > > > > 20fixVersion%20%3D%202.0%
> > > > > > > > 20AND%20(status%20%3D%20closed%20or%20status%20%3D%
> > 20resolved)>
> > > > > > > >
> > > > > > > > DEVNOTES
> > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > > > > > > plain;f=DEVNOTES.txt;hb=refs/tags/2.0.0-rc2 <
> > > > > https://git-wip-us.apache
> > > > > > .
> > > > > > > > org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=
> > > > > > > > refs/tags/2.0.0-rc1>
> > > > > > > >
> > > > > > > > RELEASENOTES
> > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > > > > > > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.0.0-rc2 <
> > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=
> > > > > > > > 

[GitHub] ignite pull request #1900: Ignite 1.7.11

[AMashenkov]

GitHub user AMashenkov opened a pull request:

https://github.com/apache/ignite/pull/1900

Ignite 1.7.11



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.11

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1900.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1900


commit 717e91fed944082df35ecdc2e647de2ad3fca2c7
Author: ascherbakoff 
Date:   2016-10-17T19:30:38Z

GG-11360 Fix java8 compilation.

commit 44eff48f72d2a4c5c6a9a2ba6ed903834bcb63f9
Author: Igor Sapego 
Date:   2016-10-18T08:53:46Z

IGNITE-4090: CPP: Fixed compilation for GCC 4.4.7. This closes #1165.

commit 4edcf126baf75840e3816a3e0876200c7e9c0d45
Author: vozerov-gridgain 
Date:   2016-10-18T09:25:56Z

Revert "IGNITE-3875: Added separate thread pool for data streamer. This 
closes #1067."

This reverts commit f597aff1bdf65d3d430cf85c9932391a72c2d7dc.

commit ccae52cc1af3fa2077ece6f6a9c4146e3ba72cb4
Author: tledkov-gridgain 
Date:   2016-10-18T10:01:03Z

IGNITE-2355 Fixed the test HadoopClientProtocolMultipleServersSelfTest. 
Close FileSystem after each test to prevent using the one Client delegate for 
all tests.

commit e6430bdf14e457e7497bf6e84013747f06f71fc3
Author: tledkov-gridgain 
Date:   2016-10-18T10:01:41Z

Merge remote-tracking branch 'community/ignite-1.6.10' into ignite-1.6.10

commit a863eeed9d152eed8418416291b9b19bd5b5e88b
Author: Anton Vinogradov 
Date:   2016-10-18T10:20:30Z

IGNITE-1924 Incomplete marshaller cache rebalancing causes Grid hangs under 
SSL (HOTFIX)

commit 7290d88e14a15a3d030b7381dbd0a3f14cb65a12
Author: Pavel Tupitsyn 
Date:   2016-10-18T14:17:17Z

IGNITE-4030 Streamline PlatformTarget operation methods

This closes #1167

commit 66c76d1f30f024b58db8cab07ba9e7d429f596f8
Author: tledkov-gridgain 
Date:   2016-10-18T15:45:06Z

IGNITE-2355 Fixed the test HadoopClientProtocolMultipleServersSelfTest. 
Clear connection poll after the test, cosmetic.

commit f37fbcab1ae2c7553696e96b7a9c3194a570d7af
Author: isapego 
Date:   2016-10-19T10:06:42Z

IGNITE-3705: Fixed compiliation warnings. This closes #1169.

commit 7ed2bb7e341701d052220a36a2b2f8f0a46fd644
Author: AMRepo 
Date:   2016-10-19T15:33:59Z

IGNITE-3448 Support SQL queries with distinct aggregates added. This closes 
#3448.

commit 551a4dfae6169a07a5e28f9b266f90311f3216b7
Author: tledkov-gridgain 
Date:   2016-10-21T10:25:57Z

IGNITE-2355 Fixed the test HadoopClientProtocolMultipleServersSelfTest. 
Clear connection poll before and after  the test

commit 3fa0124c554b65ffbd319c2b8b34f7e70985fbe1
Author: vozerov-gridgain 
Date:   2016-10-24T07:39:53Z

Merge commit 'bba019fd' into ignite-1.7.3

commit 2a09d22182ad065f1ee449441d41825c87cd55ea
Author: vozerov-gridgain 
Date:   2016-10-24T07:51:09Z

Merge commit 'b9c776a8' into ignite-1.7.3

commit c6c198f38a012b37a2f1b1d5c7a58e1e6ec965c5
Author: vozerov-gridgain 
Date:   2016-10-24T08:25:49Z

Merge commit 'f9a0676f' into ignite-1.7.3

commit 958f16bb0ae0ebf5307029b9fafc2cd6f0df55c5
Author: vozerov-gridgain 
Date:   2016-10-24T08:26:35Z

IGNITE-4041: Ported pool processor to 1.7.3 version.

commit 09db00d0447ee8862388d4ed444f83a4f432b079
Author: vozerov-gridgain 
Date:   2016-10-24T08:29:22Z

Merge commit '359a392f' into ignite-1.7.3

commit 4dd735ffa01966b400afba2403ed609f54117884
Author: vozerov-gridgain 
Date:   2016-10-24T08:33:41Z

Merge commit '60d27547' into ignite-1.7.3

commit 2c4c7a4b0539aac35f91e0e9cc61f2e74a088d83
Author: vozerov-gridgain 
Date:   2016-10-24T08:50:29Z

Merge commit '2ab094e0' into ignite-1.7.3

commit b9bb1f6bc02cb3054b1e9b9bfbd34b886db77624
Author: vozerov-gridgain 
Date:   2016-10-24T08:50:51Z

Merge commit '2ab094e0' into ignite-1.7.3.

commit bab33016dd7ba99e288f2eaed089a57f867f8af2
Author: Pavel Tupitsyn 
Date:   2016-10-24T09:12:33Z

merge eaf8ae24: IGNITE-4034 Get rid of specialized methods in platform 
targets

commit f97170b723e8ced39c7acae19fadb0039e7cafb7
Author: Pavel Tupitsyn 
Date:   2016-10-24T09:21:00Z

merge eaf8ae24: IGNITE-4034 Get rid of specialized methods in platform 
targets

commit e73125d96c2a8d1f5a53a5fc3d3ed58db1dc7713
Author: Pavel Tupitsyn 
Date:   2016-10-24T09:50:22Z

merge eaf8ae24: IGNITE-4034 Get rid 

[GitHub] ignite pull request #1894: IGNITE-4989 Assertion error in BPlusTree#finishTa...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/1894


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5148) Unstable test IgniteCachePartitionLossPolicySelfTest testReadWriteSafe() seems to be flaky in 2.0

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5148:
--

 Summary: Unstable test IgniteCachePartitionLossPolicySelfTest 
testReadWriteSafe() seems to be flaky in 2.0
 Key: IGNITE-5148
 URL: https://issues.apache.org/jira/browse/IGNITE-5148
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.0
Reporter: Dmitriy Pavlov
Priority: Minor
 Fix For: 2.1


Branch ignite 2.0:

org.apache.ignite.internal.processors.cache.distributed.
IgniteCachePartitionLossPolicySelfTest#testReadWriteSafe
locally each 10th lauch failed with
{noformat}

junit.framework.AssertionFailedError: Failed to find expected lost partition 
[exp=0, lost=[]]

at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.verifyCacheOps(IgniteCachePartitionLossPolicySelfTest.java:234)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.checkLostPartition(IgniteCachePartitionLossPolicySelfTest.java:181)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.testReadWriteSafe(IgniteCachePartitionLossPolicySelfTest.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1930)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:125)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1845)
at java.lang.Thread.run(Thread.java:748)


{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5147) Web console: Not POJO models are showed in project structure

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-5147:
-

 Summary: Web console: Not POJO models are showed in project 
structure
 Key: IGNITE-5147
 URL: https://issues.apache.org/jira/browse/IGNITE-5147
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
 Fix For: 2.1


# Configure model with filled section 'Domain model for cache store' and 
disabled options 'Generate POJO classes',
# Open summary page,
# Click by 'Project structure' button and extend src -> main -> java folder in 
tree.

File for configured model is shown. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5146) Web console: Simplify generation of user properties file

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-5146:
-

 Summary: Web console: Simplify generation of user properties file
 Key: IGNITE-5146
 URL: https://issues.apache.org/jira/browse/IGNITE-5146
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
 Fix For: 2.1


Secret properties file generator has duplicate code for different fields. 
Similar generations have different implementations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[Review] IGNITE-4648: IgniteInternalTx.prepare() does not wait for async operations to complete

[Дмитрий Рябов]

Hello, igniters, please review.

JIRA: https://issues.apache.org/jira/browse/IGNITE-4648

PR: https://github.com/apache/ignite/pull/1876/files

CI:
http://ci.ignite.apache.org/viewLog.html?buildId=590583=buildResultsDiv=IgniteTests_RunAllTemp

[GitHub] ignite pull request #1895: IGNITE-5134: Explicit cast to PageMemoryNoStoreIm...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/1895


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5145) Support multiple service deployment in API

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-5145:
---

 Summary: Support multiple service deployment in API
 Key: IGNITE-5145
 URL: https://issues.apache.org/jira/browse/IGNITE-5145
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.0
Reporter: Dmitry Karachentsev
 Fix For: None


IgniteServices should support possibility of deploying batch of services at 
once to speed up deployment.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5144) Do not start remappings in DataStreamer on client node leave/arrive

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-5144:
---

 Summary: Do not start remappings in DataStreamer on client node 
leave/arrive
 Key: IGNITE-5144
 URL: https://issues.apache.org/jira/browse/IGNITE-5144
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Dmitry Karachentsev
Priority: Minor


DataStreamerImpl shouldn't start remappings if topology changed by node that is 
not participate in cache (or at least by client node).

Currently data streamer compares topology versions despite of what node caused 
this change: !topVer.equals(reqTopVer).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)