[GitHub] ignite pull request #2883: IGNITE-6333 Improve cache transaction metrics to ...

[xtern]

GitHub user xtern reopened a pull request:

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

IGNITE-6333 Improve cache transaction metrics to better understand 
transactions efficiency.



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

$ git pull https://github.com/xtern/ignite IGNITE-6333

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

https://github.com/apache/ignite/pull/2883.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 #2883


commit 78b312d73c947cd62af787838ce42fecf96f87d3
Author: Pereslegin Pavel 
Date:   2017-11-20T18:31:10Z

IGNITE-6333 Added rollbacks due to deadlock/timeout tx metrics.

commit 0dd91820e5bf017d408ff364cd3906d69b76df30
Author: Pereslegin Pavel 
Date:   2017-12-11T20:48:26Z

IGNITE-6333 Removed unrelated changes, fixed test code style.

commit 3c0c2153bbc753eac88bc99f6dde00108397c219
Author: Pavel Pereslegin <30606288+xt...@users.noreply.github.com>
Date:   2017-12-12T07:56:29Z

IGNITE-6333 Wrong Jira issue.




---

[GitHub] ignite pull request #2883: IGNITE-6333 Improve cache transaction metrics to ...

[xtern]

Github user xtern closed the pull request at:

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


---

Re: Apache Ignite as a distributed processing back-ends

[Romain Manni-Bucau]

Hosting integrations in impl more than beam makes a lot of sense IMHO while
you can maintain it and follow beam release cycle. It will enable you to
evolve faster and optimise/adapt it more accurately. If you dont have the
resources, beam would fit better and guarantee it works with each release.

My 2 cts

Le 13 déc. 2017 00:47, "Lukasz Cwik"  a écrit :

> Having it inside the Apache Beam repo makes sense and I could see it being
> a good fit as an IO and as a runner.
>
> On Tue, Dec 12, 2017 at 3:29 PM, Denis Magda  wrote:
>
>> Hi Romain,
>>
>> Thanks for the reference. Do you prefer to have the Ignite runner in
>> Beam’s code base?
>>
>> From what I see, the current runners are hosted there:
>> https://github.com/apache/beam/tree/master/runners
>>
>> As for Ignite community, we would prefer to hold the integration in your
>> repo.
>>
>> —
>> Denis
>>
>> On Dec 7, 2017, at 9:54 PM, Romain Manni-Bucau 
>> wrote:
>>
>> Hi
>>
>> This sounds awesome to have an Ignite runner which could compete with
>> hazelcast-jet.
>>
>> The entry point would be https://beam.apache.org/contribute/runner-guide/
>> IMHO.
>>
>> Being on Ignite cluster also opens a lot of doors - reusing the filesystem
>> or distributed structures. Very exiting.
>>
>> Le 8 déc. 2017 05:46, "Denis Magda"  a écrit :
>>
>> Hello Apache Beam fellows!
>>
>> We at Apache Ignite community came across your project and would be happy
>> to integrate with it.
>>
>> In short, Ignite is a distributed database and computational platform that
>> has its own map-reduce like component:
>> https://apacheignite.readme.io/docs/compute-grid
>>
>> The integration will give Beam users an ability to use Ignite as a
>> distributed processing back-end system and database.
>>
>> How should we proceed? Please share any relevant information.
>>
>> —
>> Denis
>> Ignite PMC
>>
>>
>>
>

[jira] [Created] (IGNITE-7179) Create events for cluster activation/deactivation

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-7179:
---

 Summary: Create events for cluster activation/deactivation
 Key: IGNITE-7179
 URL: https://issues.apache.org/jira/browse/IGNITE-7179
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.3
Reporter: Valentin Kulichenko






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Integration of Spark and Ignite. Prototype.

[Valentin Kulichenko]

Hi Nikolay,

I reviewed the code and left several comments in the ticket [1]. Please
take a look.

[1] https://issues.apache.org/jira/browse/IGNITE-3084

-Val

On Mon, Dec 4, 2017 at 3:03 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Denis,
>
> Nikolay was doing final changes and TC stabilization. I'm planning to do
> final review this week, so hopefully we will merge the code soon.
>
> -Val
>
> On Mon, Dec 4, 2017 at 1:31 PM, Denis Magda  wrote:
>
>> Nikolay, Val,
>>
>> Since we agreed to release the feature without the strategy support, can
>> the current integration meet the world in 2.4 release? Please chime in this
>> conversation:
>> http://apache-ignite-developers.2346864.n4.nabble.com/Time-
>> and-scope-for-Apache-Ignite-2-4-td24987.html
>>
>> —
>> Denis
>>
>> > On Nov 28, 2017, at 5:42 PM, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>> >
>> > Denis,
>> >
>> > Agree. I will do the final review in next few days and merge the code.
>> >
>> > -Val
>> >
>> > On Tue, Nov 28, 2017 at 5:28 PM, Denis Magda  wrote:
>> >
>> >> Guys,
>> >>
>> >> Looking into the parallel discussion about the strategy support I would
>> >> change my initial stance and support the idea of releasing the
>> integration
>> >> in its current state. Is the code ready to be merged into the master?
>> Let’s
>> >> concentrate on this first and handle the strategy support as a separate
>> >> JIRA task. Agree?
>> >>
>> >> —
>> >> Denis
>> >>
>> >>> On Nov 27, 2017, at 3:47 PM, Valentin Kulichenko <
>> >> valentin.kuliche...@gmail.com> wrote:
>> >>>
>> >>> Nikolay,
>> >>>
>> >>> Let's estimate the strategy implementation work, and then decide
>> weather
>> >> to
>> >>> merge the code in current state or not. If anything is unclear, please
>> >>> start a separate discussion.
>> >>>
>> >>> -Val
>> >>>
>> >>> On Fri, Nov 24, 2017 at 5:42 AM, Николай Ижиков <
>> nizhikov@gmail.com>
>> >>> wrote:
>> >>>
>>  Hello, Val, Denis.
>> 
>> > Personally, I think that we should release the integration only
>> after
>>  the strategy is fully supported.
>> 
>>  I see two major reason to propose merge of DataFrame API
>> implementation
>>  without custom strategy:
>> 
>>  1. My PR is relatively huge, already. From my experience of
>> interaction
>>  with Ignite community - the bigger PR becomes, the more time of
>> >> commiters
>>  required to review PR.
>>  So, I propose to move smaller, but complete steps here.
>> 
>>  2. It is not clear for me what exactly includes "custom strategy and
>>  optimization".
>>  Seems, that additional discussion required.
>>  I think, I can put my thoughts on the paper and start discussion
>> right
>>  after basic implementation is done.
>> 
>> > Custom strategy implementation is actually very important for this
>>  integration.
>> 
>>  Understand and fully agreed.
>>  I'm ready to continue work in that area.
>> 
>>  23.11.2017 02:15, Denis Magda пишет:
>> 
>>  Val, Nikolay,
>> >
>> > Personally, I think that we should release the integration only
>> after
>> >> the
>> > strategy is fully supported. Without the strategy we don’t really
>> >> leverage
>> > from Ignite’s SQL engine and introduce redundant data movement
>> between
>> > Ignite and Spark nodes.
>> >
>> > How big is the effort to support the strategy in terms of the
>> amount of
>> > work left? 40%, 60%, 80%?
>> >
>> > —
>> > Denis
>> >
>> > On Nov 22, 2017, at 2:57 PM, Valentin Kulichenko <
>> >> valentin.kuliche...@gmail.com> wrote:
>> >>
>> >> Nikolay,
>> >>
>> >> Custom strategy implementation is actually very important for this
>> >> integration. Basically, it will allow to create a SQL query for
>> Ignite
>> >> and
>> >> execute it directly on the cluster. Your current implementation
>> only
>> >> adds a
>> >> new DataSource which means that Spark will fetch data in its own
>> >> memory
>> >> first, and then do most of the work (like joins for example). Does
>> it
>> >> make
>> >> sense to you? Can you please take a look at this and provide your
>> >> thoughts
>> >> on how much development is implied there?
>> >>
>> >> Current code looks good to me though and I'm OK if the strategy is
>> >> implemented as a next step in a scope of separate ticket. I will do
>> >> final
>> >> review early next week and will merge it if everything is OK.
>> >>
>> >> -Val
>> >>
>> >> On Thu, Oct 19, 2017 at 7:29 AM, Николай Ижиков <
>> >> nizhikov@gmail.com>
>> >> wrote:
>> >>
>> >> Hello.
>> >>>
>> >>> 3. IgniteCatalog vs. IgniteExternalCatalog. Why do we have two
>> >> Catalog
>> 
>> >>> implementations and what is the difference?
>> >>>
>> >>> IgniteCatalog removed.
>> >>>
>> >>> 5. I 

Re: Apache Ignite as a distributed processing back-ends

[Lukasz Cwik]

Having it inside the Apache Beam repo makes sense and I could see it being
a good fit as an IO and as a runner.

On Tue, Dec 12, 2017 at 3:29 PM, Denis Magda  wrote:

> Hi Romain,
>
> Thanks for the reference. Do you prefer to have the Ignite runner in
> Beam’s code base?
>
> From what I see, the current runners are hosted there: https://github.com/
> apache/beam/tree/master/runners
>
> As for Ignite community, we would prefer to hold the integration in your
> repo.
>
> —
> Denis
>
> On Dec 7, 2017, at 9:54 PM, Romain Manni-Bucau 
> wrote:
>
> Hi
>
> This sounds awesome to have an Ignite runner which could compete with
> hazelcast-jet.
>
> The entry point would be https://beam.apache.org/contribute/runner-guide/
> IMHO.
>
> Being on Ignite cluster also opens a lot of doors - reusing the filesystem
> or distributed structures. Very exiting.
>
> Le 8 déc. 2017 05:46, "Denis Magda"  a écrit :
>
> Hello Apache Beam fellows!
>
> We at Apache Ignite community came across your project and would be happy
> to integrate with it.
>
> In short, Ignite is a distributed database and computational platform that
> has its own map-reduce like component:
> https://apacheignite.readme.io/docs/compute-grid
>
> The integration will give Beam users an ability to use Ignite as a
> distributed processing back-end system and database.
>
> How should we proceed? Please share any relevant information.
>
> —
> Denis
> Ignite PMC
>
>
>

Re: Apache Ignite as a distributed processing back-ends

[Denis Magda]

Hi Romain,

Thanks for the reference. Do you prefer to have the Ignite runner in Beam’s 
code base?

From what I see, the current runners are hosted there: 
https://github.com/apache/beam/tree/master/runners 


As for Ignite community, we would prefer to hold the integration in your repo.

—
Denis

> On Dec 7, 2017, at 9:54 PM, Romain Manni-Bucau  wrote:
> 
> Hi
> 
> This sounds awesome to have an Ignite runner which could compete with
> hazelcast-jet.
> 
> The entry point would be https://beam.apache.org/contribute/runner-guide/
> IMHO.
> 
> Being on Ignite cluster also opens a lot of doors - reusing the filesystem
> or distributed structures. Very exiting.
> 
> Le 8 déc. 2017 05:46, "Denis Magda"  a écrit :
> 
>> Hello Apache Beam fellows!
>> 
>> We at Apache Ignite community came across your project and would be happy
>> to integrate with it.
>> 
>> In short, Ignite is a distributed database and computational platform that
>> has its own map-reduce like component:
>> https://apacheignite.readme.io/docs/compute-grid
>> 
>> The integration will give Beam users an ability to use Ignite as a
>> distributed processing back-end system and database.
>> 
>> How should we proceed? Please share any relevant information.
>> 
>> —
>> Denis
>> Ignite PMC
>> 

[GitHub] ignite pull request #3216: Ignite 2.1.7 p3

[ascherbakoff]

GitHub user ascherbakoff opened a pull request:

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

Ignite 2.1.7 p3

Release TC run.

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

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

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

https://github.com/apache/ignite/pull/3216.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 #3216


commit 943736b36d67381157fc2807cd7af4b03d44fef3
Author: nikolay_tikhonov 
Date:   2017-08-24T15:58:16Z

Revert "IGNITE-5947 Fixed "ClassCastException when two-dimensional array is 
fetched from cache".
* Due to this changes break compatibility with .NET;
* This fix doesn't cover all cases.

Signed-off-by: nikolay_tikhonov 

commit c2e836b5b9b183404f4507c64c13ab5c05653d24
Author: EdShangGG 
Date:   2017-08-24T16:15:24Z

ignite-6175 JVM Crash in Ignite Binary Objects Simple Mapper Basic suite

Signed-off-by: Andrey Gura 

commit b2b596b4f59bcf7a1b7397a6fd681a0ae47092db
Author: Andrey Novikov 
Date:   2017-08-25T03:48:15Z

IGNITE-5200 Web Console: Don't cache generated chunks in production.
(cherry picked from commit e1eb1b9)

commit 9399610d2dd4b67b1da6475ce2141787fb8dbb0e
Author: Ilya Lantukh 
Date:   2017-08-25T10:12:32Z

ignite-6180: restoring marshaller mappings on node start is implemented

commit 5bda4090f1580ea7b6557c8716e57a12572c322f
Author: Ivan Rakov 
Date:   2017-08-24T15:18:31Z

IGNITE-6178 Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 
default in persistent store confguration

commit 316312d2ae9015228e67f959e492b2c5c4a9366d
Author: Dmitry Pavlov 
Date:   2017-07-27T11:51:25Z

ignite-5682 Added stale version check for GridDhtPartFullMessage not 
related to exchange.

(cherry picked from commit eb9d06d)

commit 6f7011aa9c69280c76e03335ce4851a38cfc334e
Author: sboikov 
Date:   2017-08-25T13:59:02Z

Added test for rebalance after restart.

commit d31c43c1465ec33f9a1be81dedb958296ecc5068
Author: sboikov 
Date:   2017-08-25T14:50:01Z

Increment GridDhtPartitionMap update sequence when assign new state on 
coordinator.

commit 85fd8ce91f1e5827600aa32645552039e5a2298a
Author: Ilya Lantukh 
Date:   2017-08-25T18:23:19Z

Fixed update sequence.

commit 8c249b77533c95a4bef3d19ca583feb992322325
Author: Eduard Shangareev 
Date:   2017-08-26T14:01:46Z

GG-12609: Fixed OOM at initiator during LIST

commit a857c5ba5a24f41b5ebfaef0a15fde2906a7e0fd
Author: Ilya Lantukh 
Date:   2017-08-26T14:21:44Z

Fixed update sequence.

commit fc55ade9b5a586fb39701b4e8b7ce2105bff2fd0
Author: Sergey Chugunov 
Date:   2017-08-26T18:44:13Z

IGNITE-6124: fix for lastVer field on GridDhtPartitionsSingleMessage message

commit a01837b5028fc8739e16658d85ffe64aad01afdb
Author: Eduard Shangareev 
Date:   2017-08-27T14:30:21Z

GG-12682 Restart cluster during snapshot RESTORE fails

commit 4907f7d87a08fb5ca5d4d74ef8b61db0fd207855
Author: Ilya Lantukh 
Date:   2017-08-28T11:58:50Z

Fixed update sequence.

commit 5a6808f13e1f55ae76afb8f6b201396f3340a351
Author: Andrey V. Mashenkov 
Date:   2017-08-28T09:31:15Z

Disable leading wildcard in query.

(cherry picked from commit 75cc957)

commit ac7f21298f8fd49c2a42034fb955d3c78089ed70
Author: Ilya Lantukh 
Date:   2017-08-28T17:31:18Z

gg-12688 : Fixed updateSequence in ClientTopology.

commit eb5c4d081dca1bc9ba666960afe9a4da7c76d5b2
Author: devozerov 
Date:   2017-08-29T07:56:26Z

Merge branch 'ignite-2.1.4' into ignite-2.1.5

commit 8b47ffb886a8db950dd42ce0cae84870356ab90b
Author: tledkov-gridgain 
Date:   2017-08-29T07:53:48Z

IGNITE-6118: JDBC thin driver: added lazy execution flag. This closes #2491.

commit 5df5e2cc0e42a073de9107014876a4b646dd1b65
Author: Andrey Gura 
Date:   2017-08-29T10:14:02Z

Minor. Typo fixed.

commit 8241ea40e88ea586c8bbfb41cdd1c0f838c7be7a
Author: Igor Sapego 
Date:   2017-08-29T13:59:50Z

IGNITE-6122: Propagated SqlFieldsQuery.lazy property for C++.

(cherry picked from commit 8fd4f74)

commit bd6ae0f0aa6b6b24ad06f1ecbff1c223107a2cab
Author: tledkov-gridgain 
Date:   2017-08-29T14:18:15Z

IGNITE-4642: Added "enforceJoinOrder" and "lazy" flags to thick JDBC 
driver. This closes #2446.

commit 054955e6a2d87b209eedb58805695bf1e35be06f

Re: WEBINARS: Apache Ignite Essentials for Architects and Java Developers

[Denis Magda]

Igniters,

The second part of the series is already tomorrow at 11:00am PT / 2:00pm ET:
https://ignite.apache.org/events.html#in-memory-computing-essentials-architects-and-developers-part-2

The goal for this part is to explain the benefits of affinity collocation and 
how to apply it in practices, how Ignite memory architecture is designed and 
operates, and a coverage of the genetic and machine learning algorithms of 
Ignite.

As usual, theoretical concepts will be accompanied with vivid examples and 
demos.

—
Denis

> On Nov 16, 2017, at 4:38 PM, Denis Magda  wrote:
> 
> Igniters,
> 
> I’m pleased to invite all of you to a series of webinars that will introduce 
> you to the fundamental capabilities of in-memory computing platforms such as 
> Apache Ignite.
> 
> That will be a mix of theory and practice. A lot of code examples are waiting 
> to be shown so that you can apply the theory in practice right away. The 
> series consists of two parts.
> 
> More details are here:
> https://blogs.apache.org/ignite/entry/apache-ignite-essentials-series-for
> 
> Please help to spread a word about this event!
> https://twitter.com/denismagda/status/931318985353605120
> 
> —
> Denis

[GitHub] ignite pull request #3215: ignite-2.1.7-p3

[ascherbakoff]

Github user ascherbakoff closed the pull request at:

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


---

[GitHub] ignite pull request #3215: ignite-2.1.7-p3

[ascherbakoff]

GitHub user ascherbakoff opened a pull request:

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

ignite-2.1.7-p3

Release TC run.

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

$ git pull https://github.com/ascherbakoff/ignite ignite-2.1.7-p3

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

https://github.com/apache/ignite/pull/3215.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 #3215


commit 943736b36d67381157fc2807cd7af4b03d44fef3
Author: nikolay_tikhonov 
Date:   2017-08-24T15:58:16Z

Revert "IGNITE-5947 Fixed "ClassCastException when two-dimensional array is 
fetched from cache".
* Due to this changes break compatibility with .NET;
* This fix doesn't cover all cases.

Signed-off-by: nikolay_tikhonov 

commit c2e836b5b9b183404f4507c64c13ab5c05653d24
Author: EdShangGG 
Date:   2017-08-24T16:15:24Z

ignite-6175 JVM Crash in Ignite Binary Objects Simple Mapper Basic suite

Signed-off-by: Andrey Gura 

commit b2b596b4f59bcf7a1b7397a6fd681a0ae47092db
Author: Andrey Novikov 
Date:   2017-08-25T03:48:15Z

IGNITE-5200 Web Console: Don't cache generated chunks in production.
(cherry picked from commit e1eb1b9)

commit 9399610d2dd4b67b1da6475ce2141787fb8dbb0e
Author: Ilya Lantukh 
Date:   2017-08-25T10:12:32Z

ignite-6180: restoring marshaller mappings on node start is implemented

commit 5bda4090f1580ea7b6557c8716e57a12572c322f
Author: Ivan Rakov 
Date:   2017-08-24T15:18:31Z

IGNITE-6178 Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 
default in persistent store confguration

commit 316312d2ae9015228e67f959e492b2c5c4a9366d
Author: Dmitry Pavlov 
Date:   2017-07-27T11:51:25Z

ignite-5682 Added stale version check for GridDhtPartFullMessage not 
related to exchange.

(cherry picked from commit eb9d06d)

commit 6f7011aa9c69280c76e03335ce4851a38cfc334e
Author: sboikov 
Date:   2017-08-25T13:59:02Z

Added test for rebalance after restart.

commit d31c43c1465ec33f9a1be81dedb958296ecc5068
Author: sboikov 
Date:   2017-08-25T14:50:01Z

Increment GridDhtPartitionMap update sequence when assign new state on 
coordinator.

commit 85fd8ce91f1e5827600aa32645552039e5a2298a
Author: Ilya Lantukh 
Date:   2017-08-25T18:23:19Z

Fixed update sequence.

commit 8c249b77533c95a4bef3d19ca583feb992322325
Author: Eduard Shangareev 
Date:   2017-08-26T14:01:46Z

GG-12609: Fixed OOM at initiator during LIST

commit a857c5ba5a24f41b5ebfaef0a15fde2906a7e0fd
Author: Ilya Lantukh 
Date:   2017-08-26T14:21:44Z

Fixed update sequence.

commit fc55ade9b5a586fb39701b4e8b7ce2105bff2fd0
Author: Sergey Chugunov 
Date:   2017-08-26T18:44:13Z

IGNITE-6124: fix for lastVer field on GridDhtPartitionsSingleMessage message

commit a01837b5028fc8739e16658d85ffe64aad01afdb
Author: Eduard Shangareev 
Date:   2017-08-27T14:30:21Z

GG-12682 Restart cluster during snapshot RESTORE fails

commit 4907f7d87a08fb5ca5d4d74ef8b61db0fd207855
Author: Ilya Lantukh 
Date:   2017-08-28T11:58:50Z

Fixed update sequence.

commit 5a6808f13e1f55ae76afb8f6b201396f3340a351
Author: Andrey V. Mashenkov 
Date:   2017-08-28T09:31:15Z

Disable leading wildcard in query.

(cherry picked from commit 75cc957)

commit ac7f21298f8fd49c2a42034fb955d3c78089ed70
Author: Ilya Lantukh 
Date:   2017-08-28T17:31:18Z

gg-12688 : Fixed updateSequence in ClientTopology.

commit eb5c4d081dca1bc9ba666960afe9a4da7c76d5b2
Author: devozerov 
Date:   2017-08-29T07:56:26Z

Merge branch 'ignite-2.1.4' into ignite-2.1.5

commit 8b47ffb886a8db950dd42ce0cae84870356ab90b
Author: tledkov-gridgain 
Date:   2017-08-29T07:53:48Z

IGNITE-6118: JDBC thin driver: added lazy execution flag. This closes #2491.

commit 5df5e2cc0e42a073de9107014876a4b646dd1b65
Author: Andrey Gura 
Date:   2017-08-29T10:14:02Z

Minor. Typo fixed.

commit 8241ea40e88ea586c8bbfb41cdd1c0f838c7be7a
Author: Igor Sapego 
Date:   2017-08-29T13:59:50Z

IGNITE-6122: Propagated SqlFieldsQuery.lazy property for C++.

(cherry picked from commit 8fd4f74)

commit bd6ae0f0aa6b6b24ad06f1ecbff1c223107a2cab
Author: tledkov-gridgain 
Date:   2017-08-29T14:18:15Z

IGNITE-4642: Added "enforceJoinOrder" and "lazy" flags to thick JDBC 
driver. This closes #2446.

commit 054955e6a2d87b209eedb58805695bf1e35be06f
Author: 

[GitHub] ignite pull request #3214: ignite-2.1.7-p3

[ascherbakoff]

Github user ascherbakoff closed the pull request at:

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


---

[GitHub] ignite pull request #3214: ignite-2.1.7-p3

[ascherbakoff]

GitHub user ascherbakoff opened a pull request:

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

ignite-2.1.7-p3

Release TC run.

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

$ git pull https://github.com/ascherbakoff/ignite ignite-2.1.7-p3

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

https://github.com/apache/ignite/pull/3214.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 #3214


commit 943736b36d67381157fc2807cd7af4b03d44fef3
Author: nikolay_tikhonov 
Date:   2017-08-24T15:58:16Z

Revert "IGNITE-5947 Fixed "ClassCastException when two-dimensional array is 
fetched from cache".
* Due to this changes break compatibility with .NET;
* This fix doesn't cover all cases.

Signed-off-by: nikolay_tikhonov 

commit c2e836b5b9b183404f4507c64c13ab5c05653d24
Author: EdShangGG 
Date:   2017-08-24T16:15:24Z

ignite-6175 JVM Crash in Ignite Binary Objects Simple Mapper Basic suite

Signed-off-by: Andrey Gura 

commit b2b596b4f59bcf7a1b7397a6fd681a0ae47092db
Author: Andrey Novikov 
Date:   2017-08-25T03:48:15Z

IGNITE-5200 Web Console: Don't cache generated chunks in production.
(cherry picked from commit e1eb1b9)

commit 9399610d2dd4b67b1da6475ce2141787fb8dbb0e
Author: Ilya Lantukh 
Date:   2017-08-25T10:12:32Z

ignite-6180: restoring marshaller mappings on node start is implemented

commit 5bda4090f1580ea7b6557c8716e57a12572c322f
Author: Ivan Rakov 
Date:   2017-08-24T15:18:31Z

IGNITE-6178 Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 
default in persistent store confguration

commit 316312d2ae9015228e67f959e492b2c5c4a9366d
Author: Dmitry Pavlov 
Date:   2017-07-27T11:51:25Z

ignite-5682 Added stale version check for GridDhtPartFullMessage not 
related to exchange.

(cherry picked from commit eb9d06d)

commit 6f7011aa9c69280c76e03335ce4851a38cfc334e
Author: sboikov 
Date:   2017-08-25T13:59:02Z

Added test for rebalance after restart.

commit d31c43c1465ec33f9a1be81dedb958296ecc5068
Author: sboikov 
Date:   2017-08-25T14:50:01Z

Increment GridDhtPartitionMap update sequence when assign new state on 
coordinator.

commit 85fd8ce91f1e5827600aa32645552039e5a2298a
Author: Ilya Lantukh 
Date:   2017-08-25T18:23:19Z

Fixed update sequence.

commit 8c249b77533c95a4bef3d19ca583feb992322325
Author: Eduard Shangareev 
Date:   2017-08-26T14:01:46Z

GG-12609: Fixed OOM at initiator during LIST

commit a857c5ba5a24f41b5ebfaef0a15fde2906a7e0fd
Author: Ilya Lantukh 
Date:   2017-08-26T14:21:44Z

Fixed update sequence.

commit fc55ade9b5a586fb39701b4e8b7ce2105bff2fd0
Author: Sergey Chugunov 
Date:   2017-08-26T18:44:13Z

IGNITE-6124: fix for lastVer field on GridDhtPartitionsSingleMessage message

commit a01837b5028fc8739e16658d85ffe64aad01afdb
Author: Eduard Shangareev 
Date:   2017-08-27T14:30:21Z

GG-12682 Restart cluster during snapshot RESTORE fails

commit 4907f7d87a08fb5ca5d4d74ef8b61db0fd207855
Author: Ilya Lantukh 
Date:   2017-08-28T11:58:50Z

Fixed update sequence.

commit 5a6808f13e1f55ae76afb8f6b201396f3340a351
Author: Andrey V. Mashenkov 
Date:   2017-08-28T09:31:15Z

Disable leading wildcard in query.

(cherry picked from commit 75cc957)

commit ac7f21298f8fd49c2a42034fb955d3c78089ed70
Author: Ilya Lantukh 
Date:   2017-08-28T17:31:18Z

gg-12688 : Fixed updateSequence in ClientTopology.

commit eb5c4d081dca1bc9ba666960afe9a4da7c76d5b2
Author: devozerov 
Date:   2017-08-29T07:56:26Z

Merge branch 'ignite-2.1.4' into ignite-2.1.5

commit 8b47ffb886a8db950dd42ce0cae84870356ab90b
Author: tledkov-gridgain 
Date:   2017-08-29T07:53:48Z

IGNITE-6118: JDBC thin driver: added lazy execution flag. This closes #2491.

commit 5df5e2cc0e42a073de9107014876a4b646dd1b65
Author: Andrey Gura 
Date:   2017-08-29T10:14:02Z

Minor. Typo fixed.

commit 8241ea40e88ea586c8bbfb41cdd1c0f838c7be7a
Author: Igor Sapego 
Date:   2017-08-29T13:59:50Z

IGNITE-6122: Propagated SqlFieldsQuery.lazy property for C++.

(cherry picked from commit 8fd4f74)

commit bd6ae0f0aa6b6b24ad06f1ecbff1c223107a2cab
Author: tledkov-gridgain 
Date:   2017-08-29T14:18:15Z

IGNITE-4642: Added "enforceJoinOrder" and "lazy" flags to thick JDBC 
driver. This closes #2446.

commit 054955e6a2d87b209eedb58805695bf1e35be06f
Author: 

[jira] [Created] (IGNITE-7178) Ignite fails to start on non x86/64 architectures

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7178:
---

 Summary: Ignite fails to start on non x86/64 architectures
 Key: IGNITE-7178
 URL: https://issues.apache.org/jira/browse/IGNITE-7178
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Denis Magda
Priority: Blocker
 Fix For: 2.4


Ignite fails with the exception below on AIX and Solar Spark. Most likely 
because of the bug that pops up on big-endian and non x86/64 CPU architectures:

{code}
ERROR 2017-11-02 11:59:01.331 [grid-nio-worker-tcp-comm-1-#22]
org.apache.ignite.internal.util.nio.GridDirectParser: Failed to read message
[msg=GridIoMessage [plc=0, topic=null, topicOrd=-1, ordered=false,
timeout=0, skipOnTimeout=false, msg=null],
buf=java.nio.DirectByteBuffer[pos=16841 lim=16844 cap=32768],
reader=DirectMessageReader [state=DirectMessageState [pos=0,
stack=[StateItem [stream=DirectByteBufferStreamImplV2
[baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
msgTypeDone=true, msg=GridDhtPartitionsFullMessage [parts=null,
partCntrs=null, partCntrs2=null, partHistSuppliers=null, partsToReload=null,
topVer=null, errs=null, compress=false, resTopVer=null, partCnt=0,
super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
[topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0], discoEvt=null,
nodeId=e3ac3f40, evt=NODE_JOINED], lastVer=GridCacheVersion [topVer=0,
order=1509612963224, nodeOrder=0], super=GridCacheMessage [msgId=369,
depInfo=null, err=null, skipPrepare=false]]], mapIt=null, it=null,
arrPos=-1, keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0,
uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
state=0], StateItem [stream=DirectByteBufferStreamImplV2
[baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
msgTypeDone=true, msg=CacheGroupAffinityMessage [], mapIt=null, it=null,
arrPos=-1, keyDone=true, readSize=7, readItems=2, prim=0, primShift=0,
uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
state=0], StateItem [stream=DirectByteBufferStreamImplV2
[baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
msgTypeDone=true, msg=GridLongList [idx=0, arr=[]], mapIt=null, it=null,
arrPos=-1, keyDone=false, readSize=512, readItems=47, prim=0, primShift=0,
uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
state=0], StateItem [stream=DirectByteBufferStreamImplV2
[baseOff=1100144027456, arrOff=-1, tmpArrOff=40, tmpArrBytes=40,
msgTypeDone=false, msg=null, mapIt=null, it=null, arrPos=-1, keyDone=false,
readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0, uuidMost=0,
uuidLeast=0, uuidLocId=0, lastFinished=true], state=0], null, null, null,
null, null, null]], lastRead=true], ses=GridSelectorNioSessionImpl
[worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=1,
bytesRcvd=404253, bytesSent=1989, bytesRcvd0=16886, bytesSent0=28,
select=true, super=GridWorker [name=grid-nio-worker-tcp-comm-1,
igniteInstanceName=null, finished=false, hashCode=-2134841549,
interrupted=false, runner=grid-nio-worker-tcp-comm-1-#22]]],
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
readBuf=java.nio.DirectByteBuffer[pos=16841 lim=16844 cap=32768],
inRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
[id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
isClient=false], connected=true, connectCnt=11, queueLimit=131072,
reserveCnt=175, pairedConnections=false],
outRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
[id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
isClient=false], connected=true, connectCnt=11, queueLimit=131072,
reserveCnt=175, pairedConnections=false], super=GridNioSessionImpl
[locAddr=/127.0.0.1:6284, rmtAddr=/127.0.0.1:61790,
createTime=1509613141318, closeTime=0, bytesSent=28, bytesRcvd=16886,
bytesSent0=28, bytesRcvd0=16886, sndSchedTime=1509613141318,
lastSndTime=1509613141318, lastRcvTime=1509613141318, readsPaused=false,
filterChain=FilterChain[filters=[GridNioCodecFilter
[parser=o.a.i.i.util.nio.GridDirectParser@8e66d834, directMode=true],
GridConnectionBytesVerifyFilter], accepted=true]]]
java.lang.IllegalArgumentException: null
at java.nio.Buffer.position(Buffer.java:255) ~[?:1.8.0]
at
org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1587)
~[ignite-core-2.3.0.jar:2.3.0]
at

[GitHub] ignite pull request #3202: IGNITE-7166

[devozerov]

Github user devozerov closed the pull request at:

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


---

[GitHub] ignite pull request #3213: IGNITE-6495 performance measurement of decision t...

[oignatenko]

GitHub user oignatenko opened a pull request:

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

IGNITE-6495 performance measurement of decision trees algorithms

- benchmark drafted a while ago integrated with recent changes in master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results

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

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

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

https://github.com/apache/ignite/pull/3213.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 #3213


commit f6782229ed97e848ff4770d5c8f49c5d97a4f2fb
Author: Oleg Ignatenko 
Date:   2017-12-12T16:24:41Z

IGNITE-6495 performance measurement of decision trees algorithms
- benchmark drafted a while ago integrated with recent changes in master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results




---

[jira] [Created] (IGNITE-7177) Custom discovery messages from plugins are handled incorrectly

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-7177:


 Summary: Custom discovery messages from plugins are handled 
incorrectly
 Key: IGNITE-7177
 URL: https://issues.apache.org/jira/browse/IGNITE-7177
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Alexey Goncharuk
 Fix For: 2.4


We call onServerNodeJoin for custom messages which do not change affinity



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3212: IGNITE-6343: Index is not used properly if changi...

[dolphin1414]

GitHub user dolphin1414 opened a pull request:

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

IGNITE-6343: Index is not used properly if changing sort order.

Index is not used properly if changing sort order.

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

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

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

https://github.com/apache/ignite/pull/3212.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 #3212


commit bcaac3a76af07f63a023d4e21916278906be4ac8
Author: rkondakov 
Date:   2017-12-11T07:51:37Z

IGNITE-6343: Workaround - reversed index creation for each user index.




---

[GitHub] ignite pull request #3211: IGNITE-7118 performance measurement for distribut...

[oignatenko]

Github user oignatenko closed the pull request at:

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


---

[jira] [Created] (IGNITE-7176) SqlQuery does not always find matching entries

[Markus Kinzler (JIRA)]

Markus Kinzler created IGNITE-7176:
--

 Summary: SqlQuery does not always find matching entries
 Key: IGNITE-7176
 URL: https://issues.apache.org/jira/browse/IGNITE-7176
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Markus Kinzler


When the @QuerySqlField annotation is put on a custom class, the sql query 
sometimes does not find the entry.
With an cache of 100'000 entries, the problem occurs in about 50% of the test 
runs for 1 - 2 entries.

When the entry is not found, no log statement is written and no exception is 
thrown, but the result is missing, despite beeing accessible via cache.get(key).

Note that i could not reproduce the Issue when i rename the class 
LegaldocAcceptPk to TestEntityPk.

A reproducible unit test is attached.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3211: IGNITE-7118 performance measurement for distribut...

[oignatenko]

GitHub user oignatenko opened a pull request:

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

IGNITE-7118 performance measurement for distributed k-means clustering



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

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

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

https://github.com/apache/ignite/pull/3211.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 #3211


commit a782ee3f944d556686e8d0a68acb3f534e3ecb13
Author: Oleg Ignatenko 
Date:   2017-12-12T13:30:11Z

IGNITE-7118 performance measurement for distributed k-means clustering
- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results

commit 125b3d1fe182dbaeba3ba99476e92a48f6daf9aa
Author: Oleg Ignatenko 
Date:   2017-12-12T14:04:42Z

IGNITE-7118 performance measurement for distributed k-means clustering
- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results




---

[GitHub] ignite pull request #3210: IGNITE-7118 performance measurement for distribut...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3208: IGNITE-7169: Missed javadoc for IgniteToDoubleFun...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3210: IGNITE-7118 performance measurement for distribut...

[oignatenko]

GitHub user oignatenko opened a pull request:

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

IGNITE-7118 performance measurement for distributed k-means clustering

- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results

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

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

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

https://github.com/apache/ignite/pull/3210.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 #3210


commit a782ee3f944d556686e8d0a68acb3f534e3ecb13
Author: Oleg Ignatenko 
Date:   2017-12-12T13:30:11Z

IGNITE-7118 performance measurement for distributed k-means clustering
- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results




---

[GitHub] ignite pull request #3209: IGNITE-7175: Throttling is not applied to page al...

[dspavlov]

GitHub user dspavlov opened a pull request:

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

IGNITE-7175: Throttling is not applied to page allocation



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

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

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

https://github.com/apache/ignite/pull/3209.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 #3209


commit c4b794f4d6d2efe50b75094d06196d174b821b55
Author: dpavlov 
Date:   2017-12-12T13:24:59Z

IGNITE-7175: Throttling is not applied to page allocation




---

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

[Anton Vinogradov]

Hi,

Seems we have merge conflict.

https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteStartNodes=buildTypeHistoryList_Ignite20Tests=%3Cdefault%3E

On Tue, Dec 12, 2017 at 3:55 PM, Andrey Kuznetsov  wrote:

> Hi Igniters,
>
> IgniteProjectionStartStopRestartSelfTest fails with timeout on TeamCity,
> maybe due to some infrastructure issues. Can anybody take a look?
>
> --
> Best regards,
>   Andrey Kuznetsov.
>

[GitHub] ignite pull request #3141: IGNITE-7095: close & cleanup internal H2 JDBC Con...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3208: IGNITE-7169: Missed javadoc for IgniteToDoubleFun...

[ybabak]

GitHub user ybabak opened a pull request:

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

IGNITE-7169: Missed javadoc for IgniteToDoubleFunction

fixed

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

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

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

https://github.com/apache/ignite/pull/3208.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 #3208


commit 9bab0d8cca9873cfb0ee1ee87442025bf9d658f6
Author: YuriBabak 
Date:   2017-12-12T13:17:58Z

IGNITE-7169: Missed javadoc for IgniteToDoubleFunction

fixed




---

[jira] [Created] (IGNITE-7175) Throttling is not applied to page allocation

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7175:
--

 Summary: Throttling is not applied to page allocation
 Key: IGNITE-7175
 URL: https://issues.apache.org/jira/browse/IGNITE-7175
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Affects Versions: 2.3
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
 Fix For: 2.4


Found during IGNITE-6341 testing, throttling check is not done for newly 
allocated pages.

Allocated page already has dirty flag, but Throttling parkNanos is applied only 
for intially not dirty page.

For initial load case it is required to do Throttling check for mostly new pages



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3207: IGNITE-7143: Fixed Decimal serialization issue

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-7143: Fixed Decimal serialization issue



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

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

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

https://github.com/apache/ignite/pull/3207.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 #3207


commit f0dfad560ce7b6013346454bff2700282de4ca65
Author: Igor Sapego 
Date:   2017-12-12T13:08:35Z

IGNITE-7143: Fixed Decimal serialization issue




---

[GitHub] ignite pull request #3206: IGNITE-6743: Cleaning direct buffer through refle...

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-6743: Cleaning direct buffer through reflection.



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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6743

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

https://github.com/apache/ignite/pull/3206.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 #3206


commit b37392cbbdd3fd04d7e4640563a12af9e5a6f09d
Author: Andrey Kuznetsov 
Date:   2017-12-12T13:11:17Z

IGNITE-6743: Cleaning direct buffer through reflection.




---

[GitHub] ignite pull request #3157: IGNITE-7122: Fixed assertion in BPlusTree printin...

[asfgit]

Github user asfgit closed the pull request at:

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


---

IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

[Andrey Kuznetsov]

Hi Igniters,

IgniteProjectionStartStopRestartSelfTest fails with timeout on TeamCity,
maybe due to some infrastructure issues. Can anybody take a look?

-- 
Best regards,
  Andrey Kuznetsov.

[jira] [Created] (IGNITE-7174) Local MLP

[Yury Babak (JIRA)]

Yury Babak created IGNITE-7174:
--

 Summary: Local MLP
 Key: IGNITE-7174
 URL: https://issues.apache.org/jira/browse/IGNITE-7174
 Project: Ignite
  Issue Type: Sub-task
  Components: ml
Reporter: Yury Babak
 Fix For: 2.4


local version of MLP



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3205: Fixed affinity calculation on snapshot discovery ...

[ilantukh]

GitHub user ilantukh opened a pull request:

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

Fixed affinity calculation on snapshot discovery message.



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

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

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

https://github.com/apache/ignite/pull/3205.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 #3205


commit e7ca9b65a68de7752195c8f4d2b5180f3c77d19f
Author: Dmitriy Govorukhin 
Date:   2017-11-13T18:52:47Z

ignite-blt-merge -> ignite-2.4.1

commit cc8168fc184bb7f5e3cc3bbb0743397097f78bfb
Author: Dmitriy Govorukhin 
Date:   2017-11-13T19:13:01Z

merge ignite-pitr-rc1 -> ignite-2.4.1

commit 87e6d74cf6a251c7984f9e68c391f790feccc281
Author: Dmitriy Govorukhin 
Date:   2017-11-14T12:49:33Z

ignite-gg-12877 Compact consistent ID in WAL

commit 9f5a22711baea05bd37ab07c8f928a4837dd83a4
Author: Ilya Lantukh 
Date:   2017-11-14T14:12:28Z

Fixed javadoc.

commit d5af2d78dd8eef8eca8ac5391d31d8c779649bb0
Author: Alexey Kuznetsov 
Date:   2017-11-15T08:09:00Z

IGNITE-6913 Baseline: Added new options to controls.sh for baseline 
manipulations.

commit 713924ce865752b6e99b03bd624136541cea5f9f
Author: Sergey Chugunov 
Date:   2017-11-15T09:03:12Z

IGNITE-5850 failover tests for cache operations during BaselineTopology 
changes

commit b65fd134e748d496f732ec2aa0953a0531f544b8
Author: Ilya Lantukh 
Date:   2017-11-15T12:54:35Z

TX read logging if PITR is enabled.

commit 9b2a567c0e04dc33116b51f88bee75f76e9107d1
Author: Ilya Lantukh 
Date:   2017-11-15T13:45:16Z

TX read logging if PITR is enabled.

commit 993058ccf0b2b8d9e80750c3e45a9ffa31d85dfa
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:51:54Z

ignite-2.4.1 optimization for store full set node more compacted

commit 1eba521f608d39967aec376b397b7fc800234e54
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:52:22Z

Merge remote-tracking branch 'professional/ignite-2.4.1' into ignite-2.4.1

commit 564b3fd51f8a7d1d81cb6874df66d0270623049c
Author: Sergey Chugunov 
Date:   2017-11-15T14:00:51Z

IGNITE-5850 fixed issue with initialization of data regions on node 
activation, fixed issue with auto-activation when random node joins inactive 
cluster with existing BLT

commit c6d1fa4da7adfadc80abdc7eaf6452b86a4f6aa4
Author: Sergey Chugunov 
Date:   2017-11-15T16:23:08Z

IGNITE-5850 transitionResult is set earlier when request for changing 
BaselineTopology is sent

commit d65674363163e38a4c5fdd73d1c8d8e1c7610797
Author: Sergey Chugunov 
Date:   2017-11-16T11:59:07Z

IGNITE-5850 new failover tests for changing BaselineTopology up (new node 
added to topology)

commit 20552f3851fe8825191b144179be032965e0b5c6
Author: Sergey Chugunov 
Date:   2017-11-16T12:53:43Z

IGNITE-5850 improved error message when online node is removed from baseline

commit 108bbcae4505ac904a6db774643ad600bfb42c21
Author: Sergey Chugunov 
Date:   2017-11-16T13:45:52Z

IGNITE-5850 BaselineTopology should not change on cluster deactivation

commit deb641ad3bdbf260fa60ad6bf607629652e324bd
Author: Dmitriy Govorukhin 
Date:   2017-11-17T09:45:44Z

ignite-2.4.1 truncate wal and checkpoint history on move/delete snapshot

commit 3c8b06f3659af30d1fd148ccc0f40e216a56c998
Author: Alexey Goncharuk 
Date:   2017-11-17T12:48:12Z

IGNITE-6947 Abandon remap after single map if future is done (fixes NPE)

commit ba2047e5ae7d271a677e0c418375d82d78c4023e
Author: devozerov 
Date:   2017-11-14T12:26:31Z

IGNITE-6901: Fixed assertion during 
IgniteH2Indexing.rebuildIndexesFromHash. This closes #3027.

commit abfc0466d6d61d87255d0fe38cbdf11ad46d4f89
Author: Sergey Chugunov 
Date:   2017-11-17T13:40:57Z

IGNITE-5850 tests for queries in presence of BaselineTopology

commit f4eabaf2a905abacc4c60c01d3ca04f6ca9ec188
Author: Sergey Chugunov 
Date:   2017-11-17T17:23:02Z

IGNITE-5850 implementation for setBaselineTopology(long topVer) migrated 
from wc-251

commit 4edeccd3e0b671aa277f58995df9ff9935baa95a
Author: EdShangGG 
Date:   2017-11-17T18:21:17Z

GG-13074 Multiple snapshot test failures after baseline topology is 
introduced
-adding baseline test to suite
-fixing issues with baseline

commit 

[GitHub] ignite pull request #3086: IGNITE-6663: SQL: optimize primary key equality l...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (IGNITE-7173) SQL: implement optional row cache

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7173:
---

 Summary: SQL: implement optional row cache
 Key: IGNITE-7173
 URL: https://issues.apache.org/jira/browse/IGNITE-7173
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.4






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2780: Ignite 6123

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3203: IGNITE-7170 Fix javadoc MemoryConfiguration (20% ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3204: IGNITE-4447: Remove "Ignite 150 Clients" suite.

[SomeFire]

GitHub user SomeFire opened a pull request:

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

IGNITE-4447: Remove "Ignite 150 Clients" suite.

Picked from 
https://github.com/apache/ignite/pull/1952/commits/f9d64f1e58b794caee47e584aa32ec18246fe434
 by vadopolski.

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

$ git pull https://github.com/SomeFire/ignite ignite-4447

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

https://github.com/apache/ignite/pull/3204.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 #3204


commit 146c785326b9091f0fa07308677a7dc4ce630fe2
Author: Dmitrii Ryabov 
Date:   2017-12-12T11:19:37Z

IGNITE-4447: Remove "Ignite 150 Clients" suite.




---

[jira] [Created] (IGNITE-7172) Web console: Add example to queries page

[Dmitriy Shabalin (JIRA)]

Dmitriy Shabalin created IGNITE-7172:


 Summary: Web console: Add example to queries page
 Key: IGNITE-7172
 URL: https://issues.apache.org/jira/browse/IGNITE-7172
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitriy Shabalin
Assignee: Dmitriy Shabalin






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7171) .NET: Support additional Data Region metrics

[Andrey Kuznetsov (JIRA)]

Andrey Kuznetsov created IGNITE-7171:


 Summary: .NET: Support additional Data Region metrics
 Key: IGNITE-7171
 URL: https://issues.apache.org/jira/browse/IGNITE-7171
 Project: Ignite
  Issue Type: New Feature
Reporter: Andrey Kuznetsov
 Fix For: 2.4


Issue [1] adds two new Data Region metrics. Both should be added to .NET as 
well.

[1] https://issues.apache.org/jira/browse/IGNITE-6902



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3203: IGNITE-7170 Fix javadoc MemoryConfiguration (20% ...

[apopovgg]

GitHub user apopovgg opened a pull request:

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

IGNITE-7170 Fix javadoc MemoryConfiguration (20% instead of 80%)



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

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

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

https://github.com/apache/ignite/pull/3203.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 #3203


commit 104b43cec4e8b07bbb8f2d00852bda6b762a5716
Author: apopov 
Date:   2017-12-12T09:20:40Z

IGNITE-7170 Fix javadoc MemoryConfiguration (20% instead of 80%)




---

[GitHub] ignite pull request #1209: IGNITE-4172: SQL: Add support for Java 8 Time API...

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #1730: IGNITE-1267: JobStealingCollisionSpi never sends ...

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #2320: Ignite 1.7.12 p1

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #3126: Ignite-2.1.8.b2

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #2730: Ignite-1.9.6-b6

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #2892: Ignite-2.1.6.b3

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[jira] [Created] (IGNITE-7170) Fix javadoc MemoryConfiguration (20% instead of 80%)

[Alexey Popov (JIRA)]

Alexey Popov created IGNITE-7170:


 Summary: Fix javadoc MemoryConfiguration (20% instead of 80%)
 Key: IGNITE-7170
 URL: https://issues.apache.org/jira/browse/IGNITE-7170
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.3
Reporter: Alexey Popov
Assignee: Alexey Popov
Priority: Trivial






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3078: IGNITE-6984: Make cache creation slightly more ve...

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #3193: IGNITE-7157: Fixed deadlock when partition evicti...

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #1747: Ignite-1267-1

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #3153: Ignite 1267 1.x

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[jira] [Created] (IGNITE-7169) Missed javadoc for IgniteToDoubleFunction

[Yury Babak (JIRA)]

Yury Babak created IGNITE-7169:
--

 Summary: Missed javadoc for IgniteToDoubleFunction
 Key: IGNITE-7169
 URL: https://issues.apache.org/jira/browse/IGNITE-7169
 Project: Ignite
  Issue Type: Bug
  Components: ml
Reporter: Yury Babak
Assignee: Yury Babak
 Fix For: 2.4


Missed javadoc for IgniteToDoubleFunction



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3202: IGNITE-7166

[devozerov]

GitHub user devozerov opened a pull request:

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

IGNITE-7166



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

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

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

https://github.com/apache/ignite/pull/3202.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 #3202


commit f86f15ce3c5563626acfed62f20ae97f894b83b0
Author: devozerov 
Date:   2017-12-12T07:11:30Z

Test.

commit c2e492c89983a6f732968296e2dc0ed87310c9a2
Author: devozerov 
Date:   2017-12-12T07:29:04Z

Simplifying test.

commit 40e86a21f61ecd73298995d22b7d7b423c9d3624
Author: devozerov 
Date:   2017-12-12T07:33:31Z

Simplifying test.

commit bd3aa152dbd638dc94b0ecfde0112a2c6d535832
Author: devozerov 
Date:   2017-12-12T08:02:02Z

Fix.

commit 7a6bcadeeaddd3b44999baae743cc7ba93c46762
Author: devozerov 
Date:   2017-12-12T08:10:51Z

Finalization.




---