Fwd: [ignite] your /dist/ artifacts - 1 BAD signature

[Denis Magda]

Igniters,

Especially Sergey K., Ilya S and Alexey Chetaev,

Could you explain what those “TEST” artifacts are doing in the dist folder? Are 
you trying out the new release procedure?

In addition to the questions, please fix the issue following the issue brought 
out below.

—
Denis

> Begin forwarded message:
> 
> From: Henk Penning 
> Subject: [ignite] your /dist/ artifacts - 1 BAD signature
> Date: July 14, 2017 at 10:07:11 PM PDT
> To: priv...@ignite.apache.org
> Cc: he...@apache.org, sboi...@apache.org
> Reply-To: priv...@ignite.apache.org
> 
> Hi PMC ignite,
> 
>  I watch 'www.apache.org/dist/', and I noticed that :
> 
>  -- you have 1 BAD pgp signature
> 
>   ignite/2.1.0-TEST/apache-ignite-2.1.0-TEST-src.zip.asc
> 
>  -- you have 3 unsigned artifacts :
> 
>   ignite/2.1.0-TEST/apache-ignite-fabric-2.1.0-TEST-bin.zip
>   ignite/2.1.0-TEST/apache-ignite-fabric-lgpl-2.1.0-TEST-bin.zip
>   ignite/2.1.0-TEST/apache-ignite-hadoop-2.1.0-TEST-bin.zip
> 
>  Please fix these problems soon ; for details, see
> 
>http://mirror-vm.apache.org/~henkp/checker/sig.html#project-ignite
>http://mirror-vm.apache.org/~henkp/checker/md5.html
> 
>  For information on how to fix problems, see the faq :
> 
>http://mirror-vm.apache.org/~henkp/checker/faq.html
> 
>  Thanks a lot, regards,
> 
>  Henk Penning -- apache.org infrastructure
> 
>  PS. The contents of this message is generated,
>  but the mail itself is sent "by hand".
>  PS. Please cc me on all relevant emails.
> 
>    _
> Henk P. Penning, ICT-beta R Uithof BBL-761   _/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Princetonplein 5, 3584CC Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> 

[GitHub] ignite pull request #2292: IGNITE-5649: Get meta for the specified cache.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Hello

[Andrey Mashenkov]

Hi,

Welcome to the Ignite community!

Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how 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 Wed, Jul 12, 2017 at 6:02 PM,  wrote:

> Hello Pavel. I’m has no experience how to contribute to apache backed
> projects. But I would like to implement https://issues.apache.org/jira
> /browse/IGNITE-5602 feature. Issue was created after my request in
> freshdesk. I’ve already post patch in issue comment.
>
> Отправлено из Почты для Windows 10
>
> От: Pavel Tupitsyn
> Отправлено: 12 июля 2017 г. в 17:57
> Кому: dev@ignite.apache.org
> Тема: Re: Hello
>
> Hello Andrey, welcome to Apache Ignite developers mailing list.
> Do you need help with something?
>
> On Wed, Jul 12, 2017 at 5:45 PM,  wrote:
>
> > Hello
> >
> >
>
>


-- 
Best regards,
Andrey V. Mashenkov

[GitHub] ignite pull request #2305: IGNITE-5078: refix according to latets changes

[dspavlov]

GitHub user dspavlov opened a pull request:

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

IGNITE-5078: refix according to latets changes

https://issues.apache.org/jira/browse/IGNITE-5078

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

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

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

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


commit 18bdfe96a1e579371108c661e3374183c58a296d
Author: Alexey Goncharuk 
Date:   2017-07-13T12:42:30Z

Fixed NPE in tests

commit d9ed07c67e4a4ff3a9de543cbe039ac2a48f03a0
Author: Sergey Chugunov 
Date:   2017-07-13T14:32:06Z

Functionality of muted test is debated now

commit 871d9260f3b32bed5273852dbdb74c758f73d383
Author: Sergey Chugunov 
Date:   2017-07-13T15:34:01Z

Functionality of GridVersionSelfTest is debated now

commit 2788a740c9aec88d14808d5927a346d121ad42b1
Author: Alexey Goncharuk 
Date:   2017-07-14T09:23:42Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-2.1.3

commit 1e7e692bd4ce0fe2e092117190b59382840317a7
Author: Alexey Goncharuk 
Date:   2017-07-14T09:25:08Z

Merge branch 'ignite-2.1.3' of https://github.com/gridgain/apache-ignite 
into ignite-2.1.3

commit 9fa78849c1ecc45fa56f518ad229e76725c27790
Author: Andrey V. Mashenkov 
Date:   2017-07-14T11:12:29Z

IGNITE-4831: Add an option to disable MBeans. This closes #2265.

(cherry picked from commit 7283edb)

commit d5cc82cb09cf37da783c9bcfbf6743b8910ceb30
Author: Sergey Chugunov 
Date:   2017-07-14T11:52:09Z

GridCacheAbstractNodeRestartSelfTest stopping all grids after each test to 
prevent subsequent test failures when one test fails or hangs

commit 8f1d732fc8065e59a29bb538456194d7f4edd3e9
Author: Sergey Chugunov 
Date:   2017-07-14T11:52:17Z

Merge branch 'ignite-2.1.3' of https://github.com/gridgain/apache-ignite 
into ignite-2.1.3

commit 1d75560f9f418628da7d212207267482a1ea16aa
Author: devozerov 
Date:   2017-07-14T13:07:49Z

Merge branch 'master' into ignite-2.1.3

commit e7ed26b6d305485d3a48ffcca0b9f4069e1fad30
Author: Sergey Chugunov 
Date:   2017-07-14T14:04:51Z

Test configuration fix to pass validation.

commit b32800a0ec573fb60b77bd00cb04578c5114233b
Author: Alexey Goncharuk 
Date:   2017-07-14T17:17:15Z

Corrected benchmark output

commit eed8b5e07d6fdca9109bc2daf645bbf8d1a88b6e
Author: dpavlov 
Date:   2017-07-14T18:02:03Z

IGNITE-5078: previous fix code migration, work in progress




---
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 #2304: Ignite 1.7.13

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite 1.7.13

for test purposes

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

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

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

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


commit 5fac786b6dbb179127ac725180acb54d0f6f4b0a
Author: devozerov 
Date:   2016-10-31T18:31:05Z

Merge branch 'ignite-1.6.10' into ignite-1.7.3

commit b8b9abe863ed8139553a9ad7013dfad5a363b4da
Author: devozerov 
Date:   2016-10-31T18:31:22Z

Fixes after merge.

commit 61ab650ecd353b4014a30f793090e9dab3519ad5
Author: devozerov 
Date:   2016-10-31T18:33:59Z

Fixes after merge.

commit 4495efc2aa37ca31214558968fa83598317e830a
Author: Pavel Tupitsyn 
Date:   2016-11-01T10:22:30Z

IGNITE-4117 .NET: Fix ClientReconnectTask completion timing

This closes #1195

commit dc0adf641f0ddac19af84ba0d701b33ee520b067
Author: Pavel Tupitsyn 
Date:   2016-08-16T15:11:34Z

IGNITE-3368 .NET: Improve test coverage

This closes #953

# Conflicts:
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Cache/CacheAbstractTest.cs

commit cd0275d95dc6524464a154c74b1e62559b3d8af4
Author: Pavel Tupitsyn 
Date:   2016-08-19T14:34:00Z

IGNITE-3711 .NET: Fix PlatformRawMemory coverage issue

commit d7dee5248332c6c6276c9e21aed4afb3abdd4340
Author: Pavel Tupitsyn 
Date:   2016-07-29T12:40:42Z

IGNITE-3604 .NET: Fix inconsistent namespace imports in examples

Conflicts:
modules/platforms/dotnet/Apache.Ignite.sln.DotSettings

commit 390c8d59cf8d44d9703e5fbf8d9c0f8028a4a172
Author: Pavel Tupitsyn 
Date:   2016-08-11T13:18:14Z

IGNITE-3675 .NET: Use separate caches for different entities in 
QueryExample.

commit 861c1736facdf76c71e93ddada0d8e15b5b2950c
Author: Pavel Tupitsyn 
Date:   2016-08-11T14:32:13Z

IGNITE-3673 .NET: Add examples for distributed joins.

commit 3a9cbed4e692e76ad884e60a4f5edc670e6b3c8f
Author: Pavel Tupitsyn 
Date:   2016-08-08T14:00:04Z

IGNITE-3630 .NET: Add pure binary mode example with put-get and queries.

commit d5e15af76044cf65385672f8528d48ecdeca3cb6
Author: Pavel Tupitsyn 
Date:   2016-11-02T09:02:00Z

IGNITE-4121 .NET: add ScanQuery example

commit 74f8308d10fc011c00e52efcdb315b35cc79e60a
Author: Pavel Tupitsyn 
Date:   2016-11-02T12:59:15Z

IGNITE-4123 .NET: Remove [Serializable] from Employee in examples

commit 92fff630fbf36c82f93bbd9ddd53d11bed44e772
Author: devozerov 
Date:   2016-11-02T14:50:51Z

Restored services compatibility.

commit a62a0136d295486d95c6e2ab5bba88270d831753
Author: dkarachentsev 
Date:   2016-11-02T16:07:45Z

GG-11655 - Fix merge

commit 348593986b56ddfcec4a4455e49d9b279eae4dc8
Author: devozerov 
Date:   2016-11-05T10:28:03Z

Merge branch 'ignite-1.7.3' into ignite-1.7.4

commit 175da6b7e394dd76c27d5155ff98a5b2ef03bb9d
Author: tledkov-gridgain 
Date:   2016-11-07T06:16:58Z

IGNITE-3432:  check data/meta cache names are different for different IGFS 
instances. This closes #1201

commit ead15193899d08f41491166003cabed0560f0c59
Author: Pavel Tupitsyn 
Date:   2016-11-07T07:49:03Z

IGNITE-4028 Get rid of OP_META in PlatformAbstractTarget

This closes #1192

commit 40ef2f5ae42826fe8fd077e3013e8f55c8512bdd
Author: Dmitriy Govorukhin 
Date:   2016-11-07T09:09:41Z

ignite-4178 support permission builder

commit df670c7d64046d282c053f296c47a4743c58c8b1
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:40:00Z

IGNITE-4118 .NET: Optimistic transaction example

This closes #1200

commit 474f22fda4c7cf4d7b2623c451cd7c10f0d8c636
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:55:20Z

IGNITE-4119 .NET: add TransactionDeadlockException

commit fc7ce5a4d72145f2e8a86debeda264ef0a5b37e3
Author: isapego 
Date:   2016-11-07T10:26:05Z

IGNITE-4090: Added flags so stdint and limits can be used in C++.

commit a98804a249496ba9bafbc96daa7aaf25b3d36724
Author: Igor Sapego 
Date:   2016-11-07T11:00:00Z

IGNITE-4113: Added tests. Added Statement::Set/GetAttribute.

commit b1c7c9bb95c900083702d0ba0362edf3aea5a7b4
Author: sboikov 
Date:   2016-11-07T12:40:36Z

GG-11360 - Implement SQL queries cancellation
Fix for 

[VOTE] Apache Ignite 2.1.0 RC1

[Vladimir Ozerov]

gniters!

We have uploaded a 2.1.0 release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc1/

Git tag name is
2.1.0-rc1

This release includes the following changes:

Ignite:
* Persistent cache store
* Added IgniteFuture.listenAsync() and IgniteFuture.chainAsync() mehtods
* Deprecated IgniteConfiguration.marshaller
* Updated Lucene dependency to version 5.5.2
* Machine learning: implemented K-means clusterization algorithm optimized
for distributed storages
* SQL: CREATE TABLE and DROP TABLE commands support
* SQL: New thin JDBC driver
* SQL: Improved performance of certain queries, when affinity node can be
calculated in advance
* SQL: Fixed return type of AVG() function
* SQL: BLOB type support added to thick JDBC driver
* SQL: Improved LocalDate, LocalTime and LocalDateTime support for Java 8
* SQL: Added FieldsQueryCursor interface to get fields metadata for
SqlFieldsQuery
* ODBC: Implemented DML statement batching
* Massive performance and stability improvements

Ignite.NET:
* Automatic remote assembly loading
* NuGet-based standalone node deployment
* Added conditional data removeal via LINQ DeleteAll
* Added TimestampAttribute to control DateTime serialization mode
* Added local collections joins support to LINQ.

Ignite CPP:
* Added Compute::Call and Compute::Broadcast methods

Web Console:
* Implemented support for UNIQUE indexes for key fields on import model
from RDBMS
* Added option to show full stack trace on Queries screen
* Added PK alias generation on Models screen.

Complete list of closed issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.1%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.1.0-rc1

RELEASE NOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.1.0-rc1

Please start voting.

+1 - to accept Apache Ignite 2.1.0-rc1
0 - don't care either way
-1 - DO NOT accept Apache Ignite 2.1.0-rc1 (explain why)

This vote will go for 72 hours.

Vladimir.

[GitHub] ignite pull request #2279: IGNITE-5452

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: delete upsource review

[Igor Sapego]

If you really want to start from the beginning, I guess you
should just close your review and create a new one. I'm not sure
you should really do that to just get rid of comments. The whole
point of the review is to collect comments and keep the history and
reasoning of changes in a single place.

Best Regards,
Igor

On Fri, Jul 14, 2017 at 4:46 PM, ALEKSEY KUZNETSOV  wrote:

> if request is pollutted by comments, and i just want to get rid of them.
>
> пт, 14 июл. 2017 г. в 16:40, Igor Sapego :
>
> > Why would you like to delete it?
> >
> > You can close it if it's not actual.
> >
> > Best Regards,
> > Igor
> >
> > On Fri, Jul 14, 2017 at 11:52 AM, ALEKSEY KUZNETSOV <
> > alkuznetsov...@gmail.com> wrote:
> >
> > > Igntrs! Do smbd know how to delete upsource review ?
> > > --
> > >
> > > *Best Regards,*
> > >
> > > *Kuznetsov Aleksey*
> > >
> >
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

[GitHub] ignite pull request #2303: Test eviction read through

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

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

Test eviction read through



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

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

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

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


commit 18bdfe96a1e579371108c661e3374183c58a296d
Author: Alexey Goncharuk 
Date:   2017-07-13T12:42:30Z

Fixed NPE in tests

commit d9ed07c67e4a4ff3a9de543cbe039ac2a48f03a0
Author: Sergey Chugunov 
Date:   2017-07-13T14:32:06Z

Functionality of muted test is debated now

commit 871d9260f3b32bed5273852dbdb74c758f73d383
Author: Sergey Chugunov 
Date:   2017-07-13T15:34:01Z

Functionality of GridVersionSelfTest is debated now

commit 2788a740c9aec88d14808d5927a346d121ad42b1
Author: Alexey Goncharuk 
Date:   2017-07-14T09:23:42Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-2.1.3

commit 1e7e692bd4ce0fe2e092117190b59382840317a7
Author: Alexey Goncharuk 
Date:   2017-07-14T09:25:08Z

Merge branch 'ignite-2.1.3' of https://github.com/gridgain/apache-ignite 
into ignite-2.1.3

commit 9fa78849c1ecc45fa56f518ad229e76725c27790
Author: Andrey V. Mashenkov 
Date:   2017-07-14T11:12:29Z

IGNITE-4831: Add an option to disable MBeans. This closes #2265.

(cherry picked from commit 7283edb)

commit d5cc82cb09cf37da783c9bcfbf6743b8910ceb30
Author: Sergey Chugunov 
Date:   2017-07-14T11:52:09Z

GridCacheAbstractNodeRestartSelfTest stopping all grids after each test to 
prevent subsequent test failures when one test fails or hangs

commit 8f1d732fc8065e59a29bb538456194d7f4edd3e9
Author: Sergey Chugunov 
Date:   2017-07-14T11:52:17Z

Merge branch 'ignite-2.1.3' of https://github.com/gridgain/apache-ignite 
into ignite-2.1.3

commit 1d75560f9f418628da7d212207267482a1ea16aa
Author: devozerov 
Date:   2017-07-14T13:07:49Z

Merge branch 'master' into ignite-2.1.3

commit a9c90d63a055252c5f1fdf3eda92c9f309227b68
Author: Sergey Chugunov 
Date:   2017-07-14T14:04:51Z

check fix finishes on TC




---
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-5758) CPP: Add pointer semantics for primitive types

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-5758:
---

 Summary: CPP: Add pointer semantics for primitive types
 Key: IGNITE-5758
 URL: https://issues.apache.org/jira/browse/IGNITE-5758
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.0
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.2


Currently, we can write any user object using two types of semantics:
{code}
// Basic
writer.WriteObject(obj);
// Pointer-based
writer.WriteObject();
{code}

However, this does not work for primitive types:
{code}
// Basic. Works just fine
writer.WriteObject(str);
// Pointer-based. Compilation error.
writer.WriteObject();
{code}

Need to add support of the pointer semantics for the primitive types as well.



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

[GitHub] ignite pull request #2280: ignite-5722 Cache entries stay in onheap after sc...

[agura]

Github user agura closed the pull request at:

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


---
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 #2281: ignite-5722 Cache entries stay in onheap after sc...

[agura]

Github user agura closed the pull request at:

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


---
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: delete upsource review

[ALEKSEY KUZNETSOV]

if request is pollutted by comments, and i just want to get rid of them.

пт, 14 июл. 2017 г. в 16:40, Igor Sapego :

> Why would you like to delete it?
>
> You can close it if it's not actual.
>
> Best Regards,
> Igor
>
> On Fri, Jul 14, 2017 at 11:52 AM, ALEKSEY KUZNETSOV <
> alkuznetsov...@gmail.com> wrote:
>
> > Igntrs! Do smbd know how to delete upsource review ?
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
> >
>
-- 

*Best Regards,*

*Kuznetsov Aleksey*

[GitHub] ignite pull request #2217: IGNITE-5444 Fix serialization of SingletonList to...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-5757) RENT partition state is set before exchange is completed

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5757:


 Summary: RENT partition state is set before exchange is completed
 Key: IGNITE-5757
 URL: https://issues.apache.org/jira/browse/IGNITE-5757
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.1
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.2


I observe the following error on TC during 
GridCachePartitionedGetAndTransformStoreSelfTest run:
{code}
[2017-07-14 
16:26:49,857][ERROR][sys-stripe-3-#4%near.GridCachePartitionedGetAndTransformStoreSelfTest%][IgniteTxHandler]
 Failed to prepare DHT transaction: GridDhtTxLocal 
[nearNodeId=8a4cdb3f-85be-4286-a63d-728a6c81, 
nearFutId=a8ef7414d51-e91dff67-b46c-4762-b7b9-9bcf382a82a0, nearMiniId=1, 
nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
[topVer=111518810, order=1500038810278, nodeOrder=3], 
super=GridDhtTxLocalAdapter [nearOnOriginatingNode=true, nearNodes=[], 
dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
[completedBase=null, sndTransformedVals=false, depEnabled=false, 
txState=IgniteTxImplicitSingleStateImpl [init=true, recovery=false], 
super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=111518810, 
order=1500038810305, nodeOrder=1], writeVer=null, implicit=true, loc=true, 
threadId=239, startTime=1500038809744, 
nodeId=322e96c3-eb1c-4aea-b9fd-3a3dae368d31, startVer=GridCacheVersion 
[topVer=111518810, order=1500038810305, nodeOrder=1], endVer=null, 
isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0, 
sysInvalidate=false, sys=false, plc=2, commitVer=GridCacheVersion 
[topVer=111518810, order=1500038810305, nodeOrder=1], finalizing=NONE, 
invalidParts=null, state=ROLLED_BACK, timedOut=false, 
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], duration=107ms, 
onePhaseCommit=false], size=0]]]
class org.apache.ignite.internal.transactions.IgniteTxRollbackCheckedException: 
Failed to prepare transaction: GridDhtTxLocal 
[nearNodeId=8a4cdb3f-85be-4286-a63d-728a6c81, 
nearFutId=a8ef7414d51-e91dff67-b46c-4762-b7b9-9bcf382a82a0, nearMiniId=1, 
nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
[topVer=111518810, order=1500038810278, nodeOrder=3], 
super=GridDhtTxLocalAdapter [nearOnOriginatingNode=true, nearNodes=[], 
dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
[completedBase=null, sndTransformedVals=false, depEnabled=false, 
txState=IgniteTxImplicitSingleStateImpl [init=true, recovery=false], 
super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=111518810, 
order=1500038810305, nodeOrder=1], writeVer=null, implicit=true, loc=true, 
threadId=239, startTime=1500038809744, 
nodeId=322e96c3-eb1c-4aea-b9fd-3a3dae368d31, startVer=GridCacheVersion 
[topVer=111518810, order=1500038810305, nodeOrder=1], endVer=null, 
isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0, 
sysInvalidate=false, sys=false, plc=2, commitVer=null, finalizing=NONE, 
invalidParts=null, state=MARKED_ROLLBACK, timedOut=false, 
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], duration=97ms, 
onePhaseCommit=false], size=0]]]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:418)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:459)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:121)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$000(IgniteTxHandler.java:95)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:141)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:139)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1042)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:561)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 

xml config can not be used in jdbs and user code simultaneously

[Mikhail Cherkasov]

Hi all,

when user uses the same xml config for jdbc driver and for his own ignite
instance there can be :
java.sql.SQLException: Failed to start Ignite node.
Caused by: class org.apache.ignite.IgniteCheckedException: Ignite instance
with this name has already been started: CustomeIgniteName

because JDBC creates separate ignite instance, while user already has one
with the same name.

Of course that can be easily workarounded, user can support two configs or
create jdbc connect first and then use Ignition.getOrStart().

However it's inconvenient for user and should be treated as usability issue.
I see 2 solutions:
1) jdbc driver should use Ignition.getOrStart()
2) jdbc driver should connection string as ignite name.

Thoughts?

-- 
Thanks,
Mikhail.

[GitHub] ignite pull request #2287: ignite-5489 Fixed possible connection leaks when ...

[agura]

Github user agura closed the pull request at:

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


---
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 #2288: ignite-5489 Fixed possible connection leaks when ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2302: IGNITE-5712 Context switching between threads for...

[voipp]

GitHub user voipp opened a pull request:

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

IGNITE-5712 Context switching between threads for optimistic transact…

…ions

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

$ git pull https://github.com/voipp/ignite IGNITE-5712-2

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

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


commit 7acf6b173df1cfc763dea72360fd9d7b13c20dfc
Author: voipp 
Date:   2017-06-30T15:06:53Z

IGNITE-5712 Context switching between threads for optimistic transactions




---
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 #2301: Ignite 5712

[voipp]

Github user voipp closed the pull request at:

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


---
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 #2255: for testing

[mcherkasov]

Github user mcherkasov closed the pull request at:

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


---
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 #2230: IGNITE-5554 ServiceProcessor may process failed r...

[mcherkasov]

Github user mcherkasov closed the pull request at:

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


---
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 #2265: IGNITE-4831: Option to disable MBeans.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-5756) Ignite with spark fails with class not found

[Rajesh (JIRA)]

Rajesh created IGNITE-5756:
--

 Summary: Ignite with spark fails with class not found
 Key: IGNITE-5756
 URL: https://issues.apache.org/jira/browse/IGNITE-5756
 Project: Ignite
  Issue Type: Bug
  Components: spark
Affects Versions: 1.9
 Environment: Apache ignite 1.9 with CDH 5.9 and spark 1.6
Reporter: Rajesh
Priority: Minor


I’m using ignite1.9 with CDH5.9. I’m unable to run sampe spark jobs with below 
exception. I have followed the steps mentioned in documentation.

Type :help for more information.
Spark context available as sc (master = yarn-client, app id = 
application_1499940258814_0024).
SQL context available as sqlContext.

scala> import org.apache.ignite.spark._
import org.apache.ignite.spark._

scala> import org.apache.ignite.configuration._
import org.apache.ignite.configuration._

scala> import javax.cache.configuration.MutableConfiguration
import javax.cache.configuration.MutableConfiguration

scala> val ic = new IgniteContext(sc, "config/default-config.xml")
class org.apache.ignite.IgniteCheckedException: Failed to create Ignite 
component (consider adding ignite-spring module to classpath) 
[component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at 
org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
at 
org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
at 
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:637)
at 
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:678)
at 
org.apache.ignite.internal.IgnitionEx.loadConfiguration(IgnitionEx.java:717)
at 
org.apache.ignite.spark.IgniteContext$$anonfun$$lessinit$greater$2.apply(IgniteContext.scala:84)
at 
org.apache.ignite.spark.IgniteContext$$anonfun$$lessinit$greater$2.apply(IgniteContext.scala:84)
at org.apache.ignite.spark.Once.apply(IgniteContext.scala:197)
at org.apache.ignite.spark.IgniteContext.ignite(IgniteContext.scala:137)
at org.apache.ignite.spark.IgniteContext.(IgniteContext.scala:58)
at org.apache.ignite.spark.IgniteContext.(IgniteContext.scala:84)
at 
$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:34)
at 
$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:39)
at 
$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:41)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:43)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:45)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:47)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:49)
at $iwC$$iwC$$iwC$$iwC$$iwC.(:51)
at $iwC$$iwC$$iwC$$iwC.(:53)
at $iwC$$iwC$$iwC.(:55)
at $iwC$$iwC.(:57)
at $iwC.(:59)
at (:61)
at .(:65)
at .()
at .(:7)
at .()
at $print()
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1045)
at 
org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1326)
at 
org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:821)
at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:852)
at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:800)
at 
org.apache.spark.repl.SparkILoop.reallyInterpret$1(SparkILoop.scala:857)
at 
org.apache.spark.repl.SparkILoop.interpretStartingWith(SparkILoop.scala:902)
at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:814)
at org.apache.spark.repl.SparkILoop.processLine$1(SparkILoop.scala:657)
at org.apache.spark.repl.SparkILoop.innerLoop$1(SparkILoop.scala:665)
at 
org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$loop(SparkILoop.scala:670)
at 
org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply$mcZ$sp(SparkILoop.scala:997)
at 
org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
at 
org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
at 
scala.tools.nsc.util.ScalaClassLoader$.savingContextLoader(ScalaClassLoader.scala:135)
at 
org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$process(SparkILoop.scala:945)
at 

Local-specific vs cluster-wide configuration setting for cache groups

[Sergey Chugunov]

Hello folks,

Investigating failing test [1] I found that cache group setting *rebalanceDelay
*was rewritten on joining node by configuration received from the grid when
it supposed to be local-specific.

I fixed this and test resumed passing, but I have a broader question: which
configuration settings of cache group are cluster-wide and which are
local-specific?

In [1] I fixed only *rebalanceDelay *setting, what about *rebalanceOrder*?

Lets compose a list of all local-specific settings in this thread.


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

[jira] [Created] (IGNITE-5755) Wrong msg: calculation of memory policy size

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-5755:


 Summary: Wrong msg: calculation of memory policy size
 Key: IGNITE-5755
 URL: https://issues.apache.org/jira/browse/IGNITE-5755
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.1
Reporter: Alexander Belyak
Priority: Trivial
 Fix For: 2.3


In PageMemoryNoStoreImpl:
{noformat}
throw new IgniteOutOfMemoryException("Not enough memory allocated " 
+
"(consider increasing memory policy size or enabling evictions) 
" +
"[policyName=" + memoryPolicyCfg.getName() +
", size=" + U.readableSize(memoryPolicyCfg.getMaxSize(), true) 
+ "]"
{noformat}
wrong usage of U.readableSize - we should use non "Si" (1024 instead of 1000) 
multiplier. Right code is:
{noformat}
throw new IgniteOutOfMemoryException("Not enough memory allocated " 
+
"(consider increasing memory policy size or enabling evictions) 
" +
"[policyName=" + memoryPolicyCfg.getName() +
", size=" + U.readableSize(memoryPolicyCfg.getMaxSize(), false) 
+ "]"
{noformat}



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

delete upsource review

[ALEKSEY KUZNETSOV]

Igntrs! Do smbd know how to delete upsource review ?
-- 

*Best Regards,*

*Kuznetsov Aleksey*

[GitHub] ignite pull request #2301: Ignite 5712

[voipp]

GitHub user voipp opened a pull request:

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

Ignite 5712



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

$ git pull https://github.com/voipp/ignite IGNITE-5712

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

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


commit 2f5335165940bcf9542ef09577f3c8430d20603a
Author: voipp 
Date:   2017-06-30T15:06:53Z

IGNITE-5712 Context switching between threads for optimistic transactions

commit 8329d03ae61162f89a7d99de9c122da885c2c2c4
Author: voipp 
Date:   2017-07-07T15:24:21Z

IGNITE-5712 Tests for pessimistic transactions added

commit bc8c5680a2b68c2966fd4e16cc0fe2ceba5a2f87
Author: voipp 
Date:   2017-07-10T15:33:06Z

IGNITE-5712 method description fixed, code style fixes

commit 2d7c712813b8b4cbffe226afbcb8e82cdacac48c
Author: voipp 
Date:   2017-07-13T17:49:24Z

IGNITE-5712 fixed serializable transaction's state not changed after 
onError() called

commit 00efd579e3d2606ae5abe90303fb369567eaa791
Author: voipp 
Date:   2017-07-13T18:58:43Z

IGNITE-5712 fixes

commit fe575878968aae2d48fb7fbdb7c8e6aacc0b1318
Author: voipp 
Date:   2017-07-13T19:16:15Z

IGNITE-5712 fixes2




---
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 #2257: IGNITE-5712 Context switching between threads for...

[voipp]

Github user voipp closed the pull request at:

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


---
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 #2300: IGNITE-5153 CPP: Introduced "varint" encoding in ...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-5153 CPP: Introduced "varint" encoding in C++



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

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

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

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


commit 1e1e8432dc936df7c62557575a57c4a159b4bca6
Author: Vyacheslav Daradur 
Date:   2017-05-31T08:41:56Z

ignite-5097: writing arrays length in varint encoding was implemented

commit d162d3e3d9036cddb275b4a3d86b8f5de9795185
Author: daradurvs 
Date:   2017-06-01T18:35:13Z

ignite-5097: doUnsafeWriteUnsignedVarint method was added

commit bfe381b3a7498eb5bebeb25026a43d36656c6041
Author: daradurvs 
Date:   2017-06-04T21:25:48Z

ignite-5097: dotNET - writing arrays length in varint encoding was 
implemented

commit 516fcf41e4e973abf41cdd19acd2c9ea1bfb9445
Author: daradurvs 
Date:   2017-06-04T21:26:00Z

ignite-5097: dotNET - hardcoded hashcode values in the tests were changed 
according to new conditions

commit fb43cbd77e9c83ef1aeb9dced923d9ca094a8be3
Author: Vyacheslav Daradur 
Date:   2017-07-05T20:25:27Z

Merge branch 'master' into ignite-5097_2

commit 398cb205c26c65f369dc3bdc4198f6032a206e87
Author: daradurvs 
Date:   2017-07-06T18:12:09Z

ignite-5097: compatibility property to allow to keep data in old format was 
added in Java part

commit 4105cf073e0e23f44c0c271407ce5415f867a352
Author: daradurvs 
Date:   2017-07-06T18:12:55Z

ignite-5097: dotNET - compatibility property to allow to keep data in old 
format was added

commit 86082a8052ce2e5c818183a18d16eddf54d5e346
Author: Vyacheslav Daradur 
Date:   2017-07-07T14:15:14Z

ignite-5097: compatibility mode test was added

commit 6aadaa985d021d38accedeaa3ada6790eb1981a9
Author: daradurvs 
Date:   2017-07-07T17:46:56Z

ignite-5097: dotNET - compatibility mode tests were added; fix constant 
condition

commit bd24ccf6e8c2b4deb85cd3ad48635be9addaecd3
Author: Vyacheslav Daradur 
Date:   2017-07-10T15:22:01Z

ignite-5097: dotNET - fix compatibility property condition

commit 5f3e1543c8de140a533d0fbdbfca74a2ffd89a36
Author: Vyacheslav Daradur 
Date:   2017-07-10T15:32:44Z

ignite-5097: rename constant of compatibility mode

commit ac59755342093609c2c9505ccde3308ebf1f1ed4
Author: daradurvs 
Date:   2017-07-10T17:42:00Z

ignite-5097: dotNET - fix compatibility mode test

commit 36e7ce2fb39f8426f2438b0b81823309e6434151
Author: Igor Sapego 
Date:   2017-05-04T13:11:11Z

IGNITE-5153: Implemented varint writing and reading

commit 720c9a273102604b371e24cecb807a4b6637
Author: Igor Sapego 
Date:   2017-05-04T15:26:27Z

IGNITE-5153: Added tests

commit 14416c538765990e6c5853b552e4167ccc8b7573
Author: Igor Sapego 
Date:   2017-05-05T12:44:56Z

IGNITE-5153: Refactored Decimal writing reading

commit d5534fde463594df007e5161d2bdd6546bb762d6
Author: Igor Sapego 
Date:   2017-05-05T13:41:03Z

IGNITE-5153: Refactored strings marshalling

commit 3cf8ebf9f978479682329fc18eef6d782ca703a5
Author: Igor Sapego 
Date:   2017-05-05T14:40:58Z

IGNITE-5153: Refactored tests and added tests for Decimal

commit 6c587ad0c4f5370f6c3635065f3d348f855cbb66
Author: Igor Sapego 
Date:   2017-05-05T17:57:06Z

IGNITE-5153: Fixed marshaling of Decimals

commit ffb5a2b9ec1486573c5ed4c50d53a15fb4a48062
Author: Igor Sapego 
Date:   2017-05-10T16:10:29Z

IGNITE-5153: Added tests for string

commit 4c57f878d06541d397381d79294fded5410317fc
Author: Igor Sapego 
Date:   2017-05-10T17:44:02Z

IGNITE-5153: Implemented for Decimals

commit a43aeba23260ff348147b93ce103982be4c8e6ad
Author: Igor Sapego 
Date:   2017-05-10T17:57:19Z

IGNITE-5153: Implemented for strings

commit 1f8ca2ae39dba23d53ef15cdc78bbcda8cc82c11
Author: Igor Sapego 
Date:   2017-05-10T18:58:07Z

IGNITE-5153: Refactored BinaryReaderImpl

commit 57b43296d65d8dfc8a9d9ab1a19e80f865bac9cd
Author: Igor Sapego 
Date:   2017-05-10T19:14:12Z

IGNITE-5153: Implemented for arrays

commit a01cd862591c2220371e31444bf3105340e111bc
Author: Igor Sapego 
Date:   2017-05-12T12:36:07Z

IGNITE-5153: ReaderImpl refactored.

commit bb25355f712de2d53a7d1504c79fb875c89e04c9
Author: Igor Sapego