Re: Should we take care of Java 9 in Ignite 2.0 scope?

[Denis Magda]

> For using internal classes that not exported by default, we will need to
> add new args(--add-exports) when compiling (javac) *and* when running (java
> ).
> Is it ok?

Anton, are you fine with this approach?

—
Denis

> On Mar 21, 2017, at 11:05 AM, Evgenii Zhuravlev  
> wrote:
> 
> Denis,
> 
> I've found that some internal classes like sun.misc.SharedSecrets,
> sun.misc.URLClassPath, sun.misc.PerfCounter, sun.misc.Cleaner changed their
> packages. I can create wrapper for this classes with 2 modules, that can be
> enabled by profiles for java9 and java7-8.
> For using internal classes that not exported by default, we will need to
> add new args(--add-exports) when compiling (javac) *and* when running (java
> ).
> Is it ok?
> 
> 
> Also, there are a two different Unsafe classes in java 9 -  sun.misc.Unsafe
> & jdk.internal.misc.Unsafe, but both of them doesn't have monitorEnter &
> monitorExit methods, that we use in
> org.apache.ignite.internal.util.GridUnsafe. What should I do with this case?
> 
> 
> 
> 2017-03-21 11:21 GMT+03:00 Евгений Журавлев  >:
> 
>> Denis,
>> 
>> I found some recommendations on openjdk wiki:
>> https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool 
>> 
>> 
>> 2017-03-20 20:44 GMT+03:00 Denis Magda > >:
>> 
>>> Referring to your report only the following API was removed completely.
>>> The rest is still deprecated and stowed in special JDK 9 modules.
>>> 
>>> 
>>>   "org.apache.ignite.internal.processors.hadoop.HadoopClassLoader" ->
>>> "sun.misc.PerfCounter (JDK internal API (JDK removed internal API))”;
>>> 
>>> 
>>>   "org.apache.ignite.internal.processors.platform.memory.PlatformMemoryPool"
>>> -> "sun.misc.Cleaner (JDK internal API (JDK removed internal API))”;
>>> 
>>>   
>>> "org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker"
>>> -> "sun.misc.Cleaner (JDK internal API (JDK removed internal API))";
>>> 
>>> 
>>> "org.apache.ignite.internal.processors.rest.protocols.GridRestProtocolAdapter"
>>> -> "sun.misc.BASE64Encoder (JDK internal API (JDK removed internal API))”;
>>> 
>>> "org.apache.ignite.internal.util.IgniteUtils"  ->
>>> "sun.misc.JavaNetAccess (JDK internal API (JDK removed internal API))”;
>>> 
>>> 
>>>   "org.apache.ignite.internal.util.IgniteUtils"  ->
>>> "sun.misc.SharedSecrets (JDK internal API (JDK removed internal API))”;
>>> 
>>> 
>>>   "org.apache.ignite.internal.util.IgniteUtils"  ->
>>> "sun.misc.URLClassPath (JDK internal API (JDK removed internal API))”;
>>> 
>>> 
>>> 
>>> *Evgeniy*, does Oracle officially suggest replacements for deleted APIs?
>>> Probably it’s a matter of day to do a switch.
>>> 
>>> 
>>> —
>>> Denis
>>> 
 On Mar 20, 2017, at 9:57 AM, Евгений Журавлев 
>>> wrote:
 
 Igniters,
 
 There are a few JDK internal APIs removed in JDK 9, that we use in
>>> ignite. We need to decide what to do with these dependencies. Here is a
>>> list of dependencies after using jdeps
 
 2017-01-26 12:07 GMT+03:00 Anton Vinogradov >> >>:
 Denis,
 
 I've created issue  <
>>> https://issues.apache.org/jira/browse/IGNITE-4615 
>>> >> related
 to discussion.
 We have a lot of legacy code inside pom.xml files. One of legacy issues
>>> is
 a tools.jar usage.
 So, it will be nice to fix this as well.
 
 On Thu, Jan 26, 2017 at 2:54 AM, Denis Magda 
>>> >> wrote:
 
> Well, the build fails almost immediately on the latest JDK 9.
> 
> This is the reason (https://issues.jenkins-ci.org 
> 
>>> /browse/JENKINS-25993 >> 
 ).
> 
> [ERROR] Failed to execute goal on project ignite-tools: Could not
>>> resolve
> dependencies for project org.apache.ignite:ignite-tools
>>> :jar:2.0.0-SNAPSHOT:
> Could not find artifact com.sun:tools:jar:9-ea at specified path
> /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/..
>>> /lib/tools.jar
> -> [Help 1]
> 
> 
> If to tweak pom files cleaning out references to tools.jar then other
> exceptions arise.
> 
> *Anton V*, could try to build the master on your side applying all the
> required changes to pom files? I don’t think I’ll do everything
>>> correctly.
> If the build goes through at least with minor modifications 

Re: Should we take care of Java 9 in Ignite 2.0 scope?

[Vladimir Ozerov]

IMO:
1) sun.misc.PerfCounter usages must be removed
2) sun.misc.Cleaner - either remove, try to switch to DirectByteBuffer or
Unsafe.allocateMemory() if possible, or create a wrapper delegating to
official Cleaner from Java9.
3) sun.misc.URLClassPath and sun.misc.SharedSecrets - used only in one
method, try remove of refactor it if possible.
4) monitorEnter and monitorExit are used only in one place in ATOMIC cache.
This place should be refactored.

On Tue, Mar 21, 2017 at 9:05 PM, Evgenii Zhuravlev  wrote:

> Denis,
>
> I've found that some internal classes like sun.misc.SharedSecrets,
> sun.misc.URLClassPath, sun.misc.PerfCounter, sun.misc.Cleaner changed their
> packages. I can create wrapper for this classes with 2 modules, that can be
> enabled by profiles for java9 and java7-8.
> For using internal classes that not exported by default, we will need to
> add new args(--add-exports) when compiling (javac) *and* when running (java
> ).
> Is it ok?
>
>
> Also, there are a two different Unsafe classes in java 9 -  sun.misc.Unsafe
> & jdk.internal.misc.Unsafe, but both of them doesn't have monitorEnter &
> monitorExit methods, that we use in
> org.apache.ignite.internal.util.GridUnsafe. What should I do with this
> case?
>
>
>
> 2017-03-21 11:21 GMT+03:00 Евгений Журавлев :
>
> > Denis,
> >
> > I found some recommendations on openjdk wiki:
> > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
> >
> > 2017-03-20 20:44 GMT+03:00 Denis Magda :
> >
> >> Referring to your report only the following API was removed completely.
> >> The rest is still deprecated and stowed in special JDK 9 modules.
> >>
> >>
> >>"org.apache.ignite.internal.processors.hadoop.HadoopClassLoader" ->
> >> "sun.misc.PerfCounter (JDK internal API (JDK removed internal API))”;
> >>
> >>
> >>"org.apache.ignite.internal.processors.platform.memory.
> PlatformMemoryPool"
> >> -> "sun.misc.Cleaner (JDK internal API (JDK removed internal API))”;
> >>
> >>"org.apache.ignite.internal.util.nio.GridNioServer$
> AbstractNioClientWorker"
> >> -> "sun.misc.Cleaner (JDK internal API (JDK removed internal API))";
> >>
> >>
> >> "org.apache.ignite.internal.processors.rest.protocols.
> GridRestProtocolAdapter"
> >> -> "sun.misc.BASE64Encoder (JDK internal API (JDK removed internal
> API))”;
> >>
> >> "org.apache.ignite.internal.util.IgniteUtils"  ->
> >> "sun.misc.JavaNetAccess (JDK internal API (JDK removed internal API))”;
> >>
> >>
> >>"org.apache.ignite.internal.util.IgniteUtils"  ->
> >> "sun.misc.SharedSecrets (JDK internal API (JDK removed internal API))”;
> >>
> >>
> >>"org.apache.ignite.internal.util.IgniteUtils"  ->
> >> "sun.misc.URLClassPath (JDK internal API (JDK removed internal API))”;
> >>
> >>
> >>
> >> *Evgeniy*, does Oracle officially suggest replacements for deleted APIs?
> >> Probably it’s a matter of day to do a switch.
> >>
> >>
> >> —
> >> Denis
> >>
> >> > On Mar 20, 2017, at 9:57 AM, Евгений Журавлев <
> e.zhuravlev...@gmail.com>
> >> wrote:
> >> >
> >> > Igniters,
> >> >
> >> > There are a few JDK internal APIs removed in JDK 9, that we use in
> >> ignite. We need to decide what to do with these dependencies. Here is a
> >> list of dependencies after using jdeps
> >> >
> >> > 2017-01-26 12:07 GMT+03:00 Anton Vinogradov  >> >:
> >> > Denis,
> >> >
> >> > I've created issue  <
> >> https://issues.apache.org/jira/browse/IGNITE-4615>> related
> >> > to discussion.
> >> > We have a lot of legacy code inside pom.xml files. One of legacy
> issues
> >> is
> >> > a tools.jar usage.
> >> > So, it will be nice to fix this as well.
> >> >
> >> > On Thu, Jan 26, 2017 at 2:54 AM, Denis Magda  >> > wrote:
> >> >
> >> > > Well, the build fails almost immediately on the latest JDK 9.
> >> > >
> >> > > This is the reason (https://issues.jenkins-ci.org
> >> /browse/JENKINS-25993  org/browse/JENKINS-25993
> >> >).
> >> > >
> >> > > [ERROR] Failed to execute goal on project ignite-tools: Could not
> >> resolve
> >> > > dependencies for project org.apache.ignite:ignite-tools
> >> :jar:2.0.0-SNAPSHOT:
> >> > > Could not find artifact com.sun:tools:jar:9-ea at specified path
> >> > > /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/..
> >> /lib/tools.jar
> >> > > -> [Help 1]
> >> > >
> >> > >
> >> > > If to tweak pom files cleaning out references to tools.jar then
> other
> >> > > exceptions arise.
> >> > >
> >> > > *Anton V*, could try to build the master on your side applying all
> the
> >> > > required changes to pom files? I don’t think I’ll do everything
> >> correctly.
> >> > > If the build goes through at least with minor modifications then
> this
> >> would
> >> > > be a good sign.
> >> > >
> >> > > —
> >> > > Denis
> >> > >
> 

[GitHub] ignite pull request #1660: Ignite 4587 tmp

[agura]

GitHub user agura opened a pull request:

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

Ignite 4587 tmp



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

$ git pull https://github.com/agura/incubator-ignite ignite-4587-tmp

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

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


commit f0dcbbdecd10ee9afee3cb0c5a96bb1540d0c06a
Author: Max Kozlov 
Date:   2017-02-13T09:20:51Z

Delete CLOCK mode in CacheAtomicWriteOrderMode.

commit a37ff76168613007d3ca09c06688bc6456e4c330
Author: Max Kozlov 
Date:   2017-02-13T09:27:28Z

Delete use CLOCK for ignite-core.

commit 25d4ea5003773b739baba2c2d5c3e7be2194ba7a
Author: Max Kozlov 
Date:   2017-02-13T09:43:59Z

Fix tests CLOCK change to PRIMARY and delete same test.

commit fcc4d8567b9ec39bb9632cf64da5f4b4390a5928
Author: Max Kozlov 
Date:   2017-02-13T13:14:25Z

Delete CLOCK, and remove check FULL_SYNC.

commit 062d631d6b6968963bcb6ef6431d622366b11706
Author: Max Kozlov 
Date:   2017-02-13T13:15:41Z

Change from CLOCK to PRIMARY in CacheConfigurationTest.cs.

commit 92e11e85cc3490b8544746e2b98336a29316c725
Author: Max Kozlov 
Date:   2017-02-13T17:00:29Z

Fix method fastMap.

commit bc7a9bd88b8d9fc18a291adbb7eb05dd1c2c0862
Author: Max Kozlov 
Date:   2017-02-27T11:33:08Z

Merge branch 'master' into ignite-4587

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicSingleUpdateFuture.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateFuture.java

commit a61e5661d182fec218f7a0ee6a3b8f484e9a7643
Author: Max Kozlov 
Date:   2017-02-27T11:40:22Z

Remove isFastMap method in GridDhtAtomicCache class because always returns 
false.

commit 8a96fdf199bf476bd417192d795fcf4d1135deb8
Author: Max Kozlov 
Date:   2017-02-27T13:25:13Z

Remove field updVer in GridNearAtomicAbstractUpdateFuture. Remove parametr 
updVer in GridNearAtomicSingleUpdateFuture.mapSingleUpdate, 
GridNearAtomicUpdateFuture.mapSingleUpdate and 
GridNearAtomicUpdateFuture.mapUpdate.

commit 72c15e5974fa253b919d001677e98a87ed219991
Author: Max Kozlov 
Date:   2017-03-01T13:01:35Z

Remove CacheAtomicWriteOrderMode.java and refactoring core module.

commit 97fdb0e03492047fe64191059a1725775e335b7b
Author: Max Kozlov 
Date:   2017-03-01T13:04:13Z

Refactoring yardstick module.

commit 82790a862f93378a09a8e8a7b52956bbe77f9085
Author: Max Kozlov 
Date:   2017-03-01T13:05:32Z

Refactoring idexing module.

commit 3d5c1345dc550b622569b0e63e019a4ae92539a8
Author: Max Kozlov 
Date:   2017-03-01T13:27:44Z

Refactoring visor-console module.

commit 5adaa1160190896b653ad4c5ea1035bc6c86048c
Author: Max Kozlov 
Date:   2017-03-01T20:41:21Z

Some loose change.

commit a60841220c1fe20c22e3122090bcfb98fa1f4b18
Author: Max Kozlov 
Date:   2017-03-01T20:41:46Z

Delete PRIMARY in test config.

commit ed3370f2fd750485a11d850b515092e4b26b6940
Author: Max Kozlov 
Date:   2017-03-01T20:42:42Z

Delete support write order mode in web-console.

commit 59af0367fe7b74ebb826c1cb57adc8cacf13ee49
Author: Max Kozlov 
Date:   2017-03-01T20:43:19Z

Delete write order mode in dotnet platform.

commit 32d2308647646027fa5792d05e532a041a974e73
Author: Max Kozlov 
Date:   2017-03-01T20:44:55Z

Delete atomicWriteOrderMode in config cpp platform.

commit 6265f33bf9401bf8c5449bb3da7daeadca086b3b
Author: Max Kozlov 
Date:   2017-03-01T22:21:35Z

Remove and rename tests.

commit 9b02f81f2e9d21ad2c2ad4e5fe4efd52545f59fb
Author: Max Kozlov 
Date:   2017-03-07T11:45:24Z

Remove GridClockSyncProcessor and related code removed.

commit decc8021f7ae5c0073f8cf15c7ca64a57305aa3b
Author: Max Kozlov 
Date:   2017-03-09T11:34:40Z

Remove GridClockSyncProcessor, GridTimeSyncProcessorSelfTest and related.

commit bdc8f2078fe914f4bd85ce0c7dc6ca8689e223e4
Author: Max Kozlov 
Date:   2017-03-09T14:20:44Z

Remove globalTime.

commit 20a87f832e4b3f46c8da511e85e08f1f6203b693
Author: Max Kozlov 
Date:   2017-03-09T15:29:23Z

Remove updateTime.

commit ea3d5de8437df5cafcf8315dde1ac6d113eef6ad
Author: Max Kozlov 
Date:   2017-03-09T15:35:52Z

wip

commit 

Re: Should we take care of Java 9 in Ignite 2.0 scope?

[Evgenii Zhuravlev]

Denis,

I've found that some internal classes like sun.misc.SharedSecrets,
sun.misc.URLClassPath, sun.misc.PerfCounter, sun.misc.Cleaner changed their
packages. I can create wrapper for this classes with 2 modules, that can be
enabled by profiles for java9 and java7-8.
For using internal classes that not exported by default, we will need to
add new args(--add-exports) when compiling (javac) *and* when running (java
).
Is it ok?


Also, there are a two different Unsafe classes in java 9 -  sun.misc.Unsafe
& jdk.internal.misc.Unsafe, but both of them doesn't have monitorEnter &
monitorExit methods, that we use in
org.apache.ignite.internal.util.GridUnsafe. What should I do with this case?



2017-03-21 11:21 GMT+03:00 Евгений Журавлев :

> Denis,
>
> I found some recommendations on openjdk wiki:
> https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
>
> 2017-03-20 20:44 GMT+03:00 Denis Magda :
>
>> Referring to your report only the following API was removed completely.
>> The rest is still deprecated and stowed in special JDK 9 modules.
>>
>>
>>"org.apache.ignite.internal.processors.hadoop.HadoopClassLoader" ->
>> "sun.misc.PerfCounter (JDK internal API (JDK removed internal API))”;
>>
>>
>>"org.apache.ignite.internal.processors.platform.memory.PlatformMemoryPool"
>> -> "sun.misc.Cleaner (JDK internal API (JDK removed internal API))”;
>>
>>
>> "org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker"
>> -> "sun.misc.Cleaner (JDK internal API (JDK removed internal API))";
>>
>>
>> "org.apache.ignite.internal.processors.rest.protocols.GridRestProtocolAdapter"
>> -> "sun.misc.BASE64Encoder (JDK internal API (JDK removed internal API))”;
>>
>> "org.apache.ignite.internal.util.IgniteUtils"  ->
>> "sun.misc.JavaNetAccess (JDK internal API (JDK removed internal API))”;
>>
>>
>>"org.apache.ignite.internal.util.IgniteUtils"  ->
>> "sun.misc.SharedSecrets (JDK internal API (JDK removed internal API))”;
>>
>>
>>"org.apache.ignite.internal.util.IgniteUtils"  ->
>> "sun.misc.URLClassPath (JDK internal API (JDK removed internal API))”;
>>
>>
>>
>> *Evgeniy*, does Oracle officially suggest replacements for deleted APIs?
>> Probably it’s a matter of day to do a switch.
>>
>>
>> —
>> Denis
>>
>> > On Mar 20, 2017, at 9:57 AM, Евгений Журавлев 
>> wrote:
>> >
>> > Igniters,
>> >
>> > There are a few JDK internal APIs removed in JDK 9, that we use in
>> ignite. We need to decide what to do with these dependencies. Here is a
>> list of dependencies after using jdeps
>> >
>> > 2017-01-26 12:07 GMT+03:00 Anton Vinogradov > >:
>> > Denis,
>> >
>> > I've created issue > https://issues.apache.org/jira/browse/IGNITE-4615>> related
>> > to discussion.
>> > We have a lot of legacy code inside pom.xml files. One of legacy issues
>> is
>> > a tools.jar usage.
>> > So, it will be nice to fix this as well.
>> >
>> > On Thu, Jan 26, 2017 at 2:54 AM, Denis Magda > > wrote:
>> >
>> > > Well, the build fails almost immediately on the latest JDK 9.
>> > >
>> > > This is the reason (https://issues.jenkins-ci.org
>> /browse/JENKINS-25993 > >).
>> > >
>> > > [ERROR] Failed to execute goal on project ignite-tools: Could not
>> resolve
>> > > dependencies for project org.apache.ignite:ignite-tools
>> :jar:2.0.0-SNAPSHOT:
>> > > Could not find artifact com.sun:tools:jar:9-ea at specified path
>> > > /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/..
>> /lib/tools.jar
>> > > -> [Help 1]
>> > >
>> > >
>> > > If to tweak pom files cleaning out references to tools.jar then other
>> > > exceptions arise.
>> > >
>> > > *Anton V*, could try to build the master on your side applying all the
>> > > required changes to pom files? I don’t think I’ll do everything
>> correctly.
>> > > If the build goes through at least with minor modifications then this
>> would
>> > > be a good sign.
>> > >
>> > > —
>> > > Denis
>> > >
>> > >
>> > > On Jan 25, 2017, at 3:22 PM, Denis Magda  dma...@apache.org>> wrote:
>> > >
>> > > Vovan,
>> > >
>> > > As far as I understand, under the module they mean new
>> component/feature
>> > > of Java 9 [1]. If you don’t use Java modules then there shouldn’t be
>> any
>> > > issues at all.
>> > >
>> > > In any case, let me try to build the project with JDK 9 that has
>> passed
>> > > feature complete phase.
>> > >
>> > > [1] http://openjdk.java.net/projects/jigsaw/spec/sotms/#defining
>> -modules > g-modules> <
>> > > http://openjdk.java.net/projects/jigsaw/spec/sotms/#defining-modules
>> >
>> > >
>> > > —
>> > > Denis
>> > >
>> > 

Re: CacheStore and Transaction

[Valentin Kulichenko]

Even with transactional cache, it's correct that updates are propagated to
CacheWriter methods. It's up to CacheStore implementation to maintain
underlying transaction on persistence store and commit or rollback it
depending on cache transaction status. Usually it's done with the help of
session listeners [1].

[1]
https://ignite.apache.org/releases/1.9.0/javadoc/org/apache/ignite/cache/store/CacheStoreSessionListener.html

-Val

On Mon, Mar 20, 2017 at 8:12 AM, Vladislav Pyatkov 
wrote:

> I mean *CacheConfiguration.setAtomicityMode*[1]
> Because transactions makes a sense only for TRANSACTIONAL cache.
>
> [1]: https://apacheignite.readme.io/docs/transactions#section-
> atomicity-mode
>
> On Sun, Mar 19, 2017 at 11:14 PM, Vladislav Pyatkov 
> wrote:
>
> > Hi
> >
> > Make sure are you using transactional cache.
> >
> > On Mar 19, 2017 10:32 PM, "Alisher Alimov" 
> > wrote:
> >
> >> Hello!
> >>
> >> I found bug when using CacheStore with Transaction or it’s expected
> >> behaviour?
> >>
> >> Example:
> >>
> >> CacheConfiguration cacheConfiguration = new CacheConfiguration("test.no-
> op");
> >> cacheConfiguration.setWriteThrough(true);
> >> cacheConfiguration.setCacheWriterFactory(noOpCacheWriterFactory);
> >> cacheConfiguration.setWriteBehindBatchSize(1);
> >>
> >>
> >> try (Transaction transaction = ignite.transactions().txStart()) {
> >> cache.put(1, 1); // will be flushed here
> >> cache.put(2, 2);
> >>
> >> transaction.rollback();
> >> }
> >>
> >>
> >> Does not matter if transaction was not completed or rollback, dirty
> >> records are flushed through CacheWriter and persistent storage will
> >> contains inconsistent data.
> >>
> >> Expected behaviour: only committed data must be flushed
> >>
> >>
> >> With best regards
> >> Alisher Alimov
> >> alimovalis...@gmail.com
> >>
> >>
> >>
> >>
> >>
>
>
> --
> Vladislav Pyatkov
>

[GitHub] ignite pull request #1659: Ignite 1.8.4-p1

[avinogradovgg]

GitHub user avinogradovgg opened a pull request:

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

Ignite 1.8.4-p1



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

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

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

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


commit 9c6824b4f33fbdead64299d9e0c34365d5d4a570
Author: nikolay_tikhonov 
Date:   2016-11-24T13:27:05Z

IGNITE-3958 Fixed "Client node should not start rest processor".

commit 56998e704e9a67760c70481c10c56e72c0a866bb
Author: Konstantin Dudkov 
Date:   2016-10-28T13:27:34Z

ignite-4088 Added methods to create/destroy multiple caches. This closes 
#1174.

(cherry picked from commit f445e7b)

commit 3e2ccfd30427ba0552eea8667c0129ae5ace9c0b
Author: Igor Sapego 
Date:   2016-11-25T11:26:54Z

IGNITE-4299: Fixes for examples.

commit 6fbaef45af8f40062a95058df7ec0984c99035b9
Author: Konstantin Dudkov 
Date:   2016-11-25T10:58:58Z

IGNITE-4305 marshalling fix in GridNearAtomicSingleUpdateInvokeRequest

commit 1a2de51f5807a91ce0d5dff28f24ed5bf7abebbc
Author: Konstantin Dudkov 
Date:   2016-11-28T09:59:02Z

IGNITE-4305 marshalling fix

commit c06e4017771603df7118974758d3d6b9cadc41b5
Author: Eduard Shangareev 
Date:   2016-11-30T11:34:47Z

ignite-4332 Usage of cache.getEntry inside GridCacheQueryManager.runQuery 
causes to remote operations

commit 066691098797be8c01daa0e8dc2ba94d4ad73561
Author: sboikov 
Date:   2016-12-01T14:16:28Z

ignite-4344 Do not create offheap map on client nodes.

commit e9ace7730773a6d4a1d30b271854f1fe8a7ba632
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:06:41Z

Improved exception handling.

commit 12bdd6a031a33eda004a66e73cee9628f073ed68
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:09:29Z

Updated classnames.properties for running nodes in IDE.

commit 33dda46061aae73e5c138851cfdd5f49a1c254cb
Author: sboikov 
Date:   2016-12-02T09:13:38Z

ignite-4285 For serializable txs allow multiple threads to get read lock 
for the same key

commit cc13d9d155f70e22e08ef203ac64e5cc0aa0a50f
Author: dkarachentsev 
Date:   2016-11-28T08:30:14Z

IGNITE-4026: Fixed BinaryObjectBuilder.build() can fail if one of the 
fields is Externalizable, enum from binary object. This closes #1281. This 
closes #1289.

(cherry picked from commit 0b7c62d)

commit b4aedfd5350b4a318f1608596a171789513835a4
Author: Igor Sapego 
Date:   2016-12-02T17:10:09Z

IGNITE-4347: Fixed NPE.

commit acf20b32d8fb68e42b904b091fb2b943f4558cef
Author: sboikov 
Date:   2016-12-05T11:01:28Z

ignite-4296 Optimize GridDhtPartitionsSingleMessage processing
- optimized processing of GridDhtPartitionsSingleMessage
- minor optimizations for RendezvousAffinityFunction
 - fixed heartbeats sending in tcp discovery

commit 6ba1711a1fa10d8276974227491136070c3ed43a
Author: Anton Vinogradov 
Date:   2016-12-06T09:55:41Z

IGNITE-4242 ExchangeManager should wait for cache rebalancing in async way

commit 3df412e7f25aac8227b68cffe1577593a05d1431
Author: sboikov 
Date:   2016-12-07T09:25:32Z

ignite-2545 Optimization for GridCompoundFuture's futures iteration

commit f3db74f782c68c7f73ef3ef4390e010976493634
Author: Anton Vinogradov 
Date:   2016-12-07T10:15:37Z

IGNITE-4238: Added geospatial queries example (nolgpl examples hotfix)

commit 0d4a1b7381fece47ee480f3a06bff7c51a7fead4
Author: Alexey Kuznetsov 
Date:   2016-12-07T11:02:49Z

Improved exception handling for failed queries.

commit 56efb10c40fd4481d6a9dc00928e7beee1f164c5
Author: Anton Vinogradov 
Date:   2016-12-07T11:25:53Z

IGNITE-4353 Parent Cassandra module deployed on maven repository (hotfix: 
deploy to custom maven repository)

commit ac8602dbdf2bbf5b16a611eaf6d520a0a7b0010b
Author: Sergi Vladykin 
Date:   2016-08-15T13:46:54Z

ignite-3685 - fixed

commit bbaa79af8ef526b5d2684db0e3d71d60a8f1ebe7
Author: agura 
Date:   2016-12-07T16:36:11Z

IGNITE-3770 GridLogThrottle.warn ignores the exception

commit 18598574bb2992aa193eed1d72ca333a1e21ad72
Author: Andrey V. Mashenkov 
Date:   2016-12-08T09:36:07Z

GG-11746: Backport of IGNITE-4379:  Fixed broken local SqlFieldsQuery.

commit 671a77a2d81cac401765dddf25f30fba4e4ab17f
Author: sboikov 
Date:   2016-12-08T09:56:46Z

ignite-4154 

[GitHub] ignite pull request #1658: 1.8.4 p1

[avinogradovgg]

Github user avinogradovgg closed the pull request at:

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


---
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 #1653: IGNITE-4846 .NET: Support complex type dictionari...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1658: 1.8.4 p1

[avinogradovgg]

GitHub user avinogradovgg opened a pull request:

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

1.8.4 p1



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

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

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

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


commit 9c6824b4f33fbdead64299d9e0c34365d5d4a570
Author: nikolay_tikhonov 
Date:   2016-11-24T13:27:05Z

IGNITE-3958 Fixed "Client node should not start rest processor".

commit 56998e704e9a67760c70481c10c56e72c0a866bb
Author: Konstantin Dudkov 
Date:   2016-10-28T13:27:34Z

ignite-4088 Added methods to create/destroy multiple caches. This closes 
#1174.

(cherry picked from commit f445e7b)

commit 3e2ccfd30427ba0552eea8667c0129ae5ace9c0b
Author: Igor Sapego 
Date:   2016-11-25T11:26:54Z

IGNITE-4299: Fixes for examples.

commit 6fbaef45af8f40062a95058df7ec0984c99035b9
Author: Konstantin Dudkov 
Date:   2016-11-25T10:58:58Z

IGNITE-4305 marshalling fix in GridNearAtomicSingleUpdateInvokeRequest

commit 1a2de51f5807a91ce0d5dff28f24ed5bf7abebbc
Author: Konstantin Dudkov 
Date:   2016-11-28T09:59:02Z

IGNITE-4305 marshalling fix

commit c06e4017771603df7118974758d3d6b9cadc41b5
Author: Eduard Shangareev 
Date:   2016-11-30T11:34:47Z

ignite-4332 Usage of cache.getEntry inside GridCacheQueryManager.runQuery 
causes to remote operations

commit 066691098797be8c01daa0e8dc2ba94d4ad73561
Author: sboikov 
Date:   2016-12-01T14:16:28Z

ignite-4344 Do not create offheap map on client nodes.

commit e9ace7730773a6d4a1d30b271854f1fe8a7ba632
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:06:41Z

Improved exception handling.

commit 12bdd6a031a33eda004a66e73cee9628f073ed68
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:09:29Z

Updated classnames.properties for running nodes in IDE.

commit 33dda46061aae73e5c138851cfdd5f49a1c254cb
Author: sboikov 
Date:   2016-12-02T09:13:38Z

ignite-4285 For serializable txs allow multiple threads to get read lock 
for the same key

commit cc13d9d155f70e22e08ef203ac64e5cc0aa0a50f
Author: dkarachentsev 
Date:   2016-11-28T08:30:14Z

IGNITE-4026: Fixed BinaryObjectBuilder.build() can fail if one of the 
fields is Externalizable, enum from binary object. This closes #1281. This 
closes #1289.

(cherry picked from commit 0b7c62d)

commit b4aedfd5350b4a318f1608596a171789513835a4
Author: Igor Sapego 
Date:   2016-12-02T17:10:09Z

IGNITE-4347: Fixed NPE.

commit acf20b32d8fb68e42b904b091fb2b943f4558cef
Author: sboikov 
Date:   2016-12-05T11:01:28Z

ignite-4296 Optimize GridDhtPartitionsSingleMessage processing
- optimized processing of GridDhtPartitionsSingleMessage
- minor optimizations for RendezvousAffinityFunction
 - fixed heartbeats sending in tcp discovery

commit 6ba1711a1fa10d8276974227491136070c3ed43a
Author: Anton Vinogradov 
Date:   2016-12-06T09:55:41Z

IGNITE-4242 ExchangeManager should wait for cache rebalancing in async way

commit 3df412e7f25aac8227b68cffe1577593a05d1431
Author: sboikov 
Date:   2016-12-07T09:25:32Z

ignite-2545 Optimization for GridCompoundFuture's futures iteration

commit f3db74f782c68c7f73ef3ef4390e010976493634
Author: Anton Vinogradov 
Date:   2016-12-07T10:15:37Z

IGNITE-4238: Added geospatial queries example (nolgpl examples hotfix)

commit 0d4a1b7381fece47ee480f3a06bff7c51a7fead4
Author: Alexey Kuznetsov 
Date:   2016-12-07T11:02:49Z

Improved exception handling for failed queries.

commit 56efb10c40fd4481d6a9dc00928e7beee1f164c5
Author: Anton Vinogradov 
Date:   2016-12-07T11:25:53Z

IGNITE-4353 Parent Cassandra module deployed on maven repository (hotfix: 
deploy to custom maven repository)

commit ac8602dbdf2bbf5b16a611eaf6d520a0a7b0010b
Author: Sergi Vladykin 
Date:   2016-08-15T13:46:54Z

ignite-3685 - fixed

commit bbaa79af8ef526b5d2684db0e3d71d60a8f1ebe7
Author: agura 
Date:   2016-12-07T16:36:11Z

IGNITE-3770 GridLogThrottle.warn ignores the exception

commit 18598574bb2992aa193eed1d72ca333a1e21ad72
Author: Andrey V. Mashenkov 
Date:   2016-12-08T09:36:07Z

GG-11746: Backport of IGNITE-4379:  Fixed broken local SqlFieldsQuery.

commit 671a77a2d81cac401765dddf25f30fba4e4ab17f
Author: sboikov 
Date:   2016-12-08T09:56:46Z

ignite-4154 Fixed node 

[GitHub] ignite pull request #728: ignite-db-x

[sboikov]

Github user sboikov closed the pull request at:

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


---
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 #1657: ignite-4844

[kdudkov]

GitHub user kdudkov opened a pull request:

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

ignite-4844



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

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

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

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


commit 9b5416834a543c1789a636424cc656058acd0b3e
Author: Konstantin Dudkov 
Date:   2017-03-21T13:23:43Z

ignite-4844




---
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 #1656: IGNITE-4691: Implemented Time type for ODBC.

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-4691: Implemented Time type for ODBC.



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

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

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

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


commit ed97238cea5f93a68d67bb038c081eed422f0c4f
Author: Igor Sapego 
Date:   2017-03-03T15:59:59Z

IGNITE-4690: Implemented reading and writing of Time. Untested.

commit fb0fea027303a80f338b46251b8c842e9cd7544a
Author: Igor Sapego 
Date:   2017-03-03T16:34:03Z

IGNITE-4690: Added basic tests

commit b42e3b2e1584d67027640bcf07bdee8f81f7c4c4
Author: Igor Sapego 
Date:   2017-03-06T16:01:35Z

IGNITE-4690: Added query test for the Time type.

commit 960673e70f143dde342e65074bcd53fd06e94e28
Author: Igor Sapego 
Date:   2017-03-15T18:30:04Z

IGNITE-4691: implemented Time type for ODBC. Not tested.

commit 0c92c6411d3e1e404d65530cee15b4bb2c458fd5
Author: Igor Sapego 
Date:   2017-03-16T17:01:54Z

IGNITE-4691: Added tests

commit a1bc36b42e6fff4daaacf6ce6aeb9edead25bea4
Author: Igor Sapego 
Date:   2017-03-17T13:27:49Z

IGNITE-4691: Fix for TIME argument

commit 943581baf0fb3b976c209d3328447c67730de40d
Author: Igor Sapego 
Date:   2017-03-21T13:10:55Z

IGNITE-4691: Removed duplicates




---
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 #1655: IGNITE-4302 BinaryMetadata exchange protocol refa...

[sergey-chugunov-1985]

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

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

IGNITE-4302 BinaryMetadata exchange protocol refactored...

... to use **CustomDiscoveryMessage**s instead of system cache

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

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

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

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


commit 18a1aaed449451761d48c9f08bec93e772c8b285
Author: Sergey Chugunov 
Date:   2017-01-19T13:53:34Z

IGNITE-4302 implementation of DiscoveryCustomEvent-based binary metadata 
exchange component

commit e503cf0eae40a79790dd889f54d31759cb4d0d91
Author: Sergey Chugunov 
Date:   2017-02-14T12:16:20Z

IGNITE-4302 merge from ignite-2.0

commit 5eecf2f32b0b538ba2ae34deedcf0e4eb0d1623a
Author: Sergey Chugunov 
Date:   2017-02-15T08:11:15Z

IGNITE-4157 interface for BinaryMetadata updates notifications was added

commit dccbfbe97e4a191f7ab916ac63c63cc1c2fb899e
Author: Sergey Chugunov 
Date:   2017-03-21T11:59:19Z

IGNITE-4302 data race between node stop event and metadata request is fixed

commit 4a2b56cd06c89fbd7e7695a5b6e91d657664e9a3
Author: Sergey Chugunov 
Date:   2017-03-21T13:03:24Z

IGNITE-4302 branch merged with master, conflicts resolved, compilation 
errors fixed




---
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 #1654: IGNITE-4827 Remove deprecated code related to bac...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-4827  Remove deprecated code related to backward compatibility



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

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

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

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


commit 225f9c70dc25aebceaa324ad18c240734c8b504f
Author: tledkov-gridgain 
Date:   2017-03-15T15:47:43Z

IGNITE-4827: remove LATE_AFF_ASSIGN_SINCE

commit f05710883a4fb020a099ca6722355e2468f043eb
Author: tledkov-gridgain 
Date:   2017-03-16T09:48:47Z

IGNITE-4827: LOAD_CACHE_JOB_SINCE and refactoring the class 
GridCacheAdapter.LoadKeysCallable and v2

commit 34414c1c5ddf26853822595f8bf0c18c0f5911a1
Author: tledkov-gridgain 
Date:   2017-03-16T09:52:37Z

IGNITE-4827: remove PartitionSizeLongTask.SINCE_VER

commit 152324f33037e896df59ae2ede0746b551f4e808
Author: tledkov-gridgain 
Date:   2017-03-16T13:00:57Z

IGNITE-4827: VisorCacheConfiguration remove compatibility with older 
versions

commit eb815762fe2003fc69bbbd7938e34cef71cbc851
Author: tledkov-gridgain 
Date:   2017-03-16T13:22:17Z

IGNITE-4827: remove GridDhtPartitionMap and rename GridDhtPartitionMap2

commit bdb63a2ed7cc64d598cbc0cf27124a3574c2599a
Author: tledkov-gridgain 
Date:   2017-03-16T13:26:35Z

IGNITE-4827: remove NEAR_JOB_SINCE

commit cde7ba7de4f60e3bb955f5c071b29582bcc1db28
Author: tledkov-gridgain 
Date:   2017-03-16T13:28:13Z

IGNITE-4827: minors

commit 039c1d334ae7def3fc00d905db2a0b5388199964
Author: tledkov-gridgain 
Date:   2017-03-16T13:33:19Z

IGNITE-4827: remove CUSTOM_MSG_ALLOW_JOINING_FOR_VERIFIED_SINCE

commit 021a22280257fd36392379fe4619ef109c9c7412
Author: tledkov-gridgain 
Date:   2017-03-16T13:52:50Z

IGNITE-4827: remove VisorCache compat

commit dbd2cb88e447261b0618f47f085f4ba0a594bd0d
Author: tledkov-gridgain 
Date:   2017-03-16T13:55:32Z

IGNITE-4827: remove MULTIPLE_CONN_SINCE_VER

commit 2dd6e75901b790c5d8bbd8a740bc94ebe0268483
Author: tledkov-gridgain 
Date:   2017-03-16T14:10:30Z

IGNITE-4827: remove PART_MAP_COMPRESS_SINCE

commit 0f7c4fb1d5a1b4d73d54be6cbbbef2a167df93e5
Author: tledkov-gridgain 
Date:   2017-03-16T14:24:28Z

IGNITE-4827: remove old rebalance API

commit aba09393f552b472434a86ccc6dbe05355a63f09
Author: tledkov-gridgain 
Date:   2017-03-16T14:39:47Z

IGNITE-4827: remove CacheContinuousQueryBatchAck.SINCE_VER

commit e3aeadf2d0bf1d039ea6e081945df9091d13427e
Author: tledkov-gridgain 
Date:   2017-03-16T15:32:24Z

IGNITE-4827: remove services compatibility with older version

commit 20422f1ed74abb6655ac7862e7d11409cd9b1464
Author: tledkov-gridgain 
Date:   2017-03-16T15:41:12Z

IGNITE-4827: remove BINARY_CFG_CHECK_SINCE

commit 663a07cbb9865d342fc3bf5612be1228f537358a
Author: tledkov-gridgain 
Date:   2017-03-16T16:08:11Z

IGNITE-4827: remove services compatibility with older version

commit 572ad53a7adca25b0a6a97712a1aae9e40271836
Author: tledkov-gridgain 
Date:   2017-03-17T07:23:16Z

IGNITE-4827: remove GridQueryRequest

commit 6e0aa1483bce6a0f869a9217f5e077b6913f5a08
Author: Alexey Kuznetsov 
Date:   2017-03-17T07:46:23Z

IGNITE-4827 Cleanup deprecated code.

commit 021068904901254f843553c6f7a2a181e2f29e93
Author: tledkov-gridgain 
Date:   2017-03-17T09:04:06Z

IGNITE-4827: remove SINGLE_GET_MSG_SINCE

commit 8e71cc803e10f25967465d80a5086cba19bf86aa
Author: tledkov-gridgain 
Date:   2017-03-17T09:30:05Z

IGNITE-4827: remove unused

commit 178d520d02022cdb8832f6a69b3c4a9fc4178f58
Author: tledkov-gridgain 
Date:   2017-03-17T09:30:14Z

Merge branch 'ignite-2.0' into ignite-4827

commit 1e3fc2d92bd484d051d27654a2785369a5859593
Author: tledkov-gridgain 
Date:   2017-03-17T09:36:03Z

IGNITE-4827: minors

commit f9d193abbb221f525c4fb3b657c76c583fb95210
Author: tledkov-gridgain 
Date:   2017-03-17T09:38:47Z

IGNITE-4827: remove LOCAL_STORE_KEEPS_PRIMARY_AND_BACKUPS_SINCE

commit 8118fa1be3fca9a3317dd8d9b6e44107bb68dd09
Author: tledkov-gridgain 
Date:   2017-03-17T11:51:35Z

IGNITE-4827: remove compatibility at compute closures

commit ace6e1875e8d1bc5918fffc05ff2afd69104f355
Author: tledkov-gridgain 

[GitHub] ignite pull request #1653: IGNITE-4846 .NET: Support complex type dictionari...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-4846 .NET: Support complex type dictionaries in app.config 
configuration



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

$ git pull https://github.com/ptupitsyn/ignite ignite-4846

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

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


commit 98cd4377cc6806b9049b3d4aa62b28e80e8df204
Author: Pavel Tupitsyn 
Date:   2017-03-21T06:44:18Z

IGNITE-4846 .NET: Support complex type dictionaries in app.config 
configuration

commit 5207e8c9d25d4fad02e0191babafc7f31abf8085
Author: Pavel Tupitsyn 
Date:   2017-03-21T06:51:38Z

wip

commit bf83388a79bdf53d4be98a12008a9332fd50ffdf
Author: Pavel Tupitsyn 
Date:   2017-03-21T09:10:27Z

Fix dictionary writing

commit 6158da2a01d849cc745d07119b58f26b1ae9b008
Author: Pavel Tupitsyn 
Date:   2017-03-21T09:12:12Z

wip

commit bab12a1fd4bf836ff34789383ffb5127d8892cc3
Author: Pavel Tupitsyn 
Date:   2017-03-21T09:56:10Z

wip refactor reading

commit 2879d2e129d2342f2f20ed2df85b37fec30d3b34
Author: Pavel Tupitsyn 
Date:   2017-03-21T10:07:54Z

wip

commit b38b20c627ae79277152986199cb5a4b90ef0f8f
Author: Pavel Tupitsyn 
Date:   2017-03-21T10:12:06Z

wip

commit c87c84a477083ea7938b81eaf785220b8d5539c7
Author: Pavel Tupitsyn 
Date:   2017-03-21T10:17:45Z

Reading fixed

commit a46754fe5a7b11a031cd0d00c18e4c054fc587e0
Author: Pavel Tupitsyn 
Date:   2017-03-21T10:37:09Z

refactor property reading

commit b7ae2f4e25360f5711ef2f1b8bd0ea9cba8134fe
Author: Pavel Tupitsyn 
Date:   2017-03-21T10:57:11Z

Refactor value reading

commit 509fa2e997d936b41bc979034706b9ed421af47d
Author: Pavel Tupitsyn 
Date:   2017-03-21T11:24:27Z

wip

commit 74e41f9b839f85663b971f6e4b303b8a6c8aeaf7
Author: Pavel Tupitsyn 
Date:   2017-03-21T11:39:00Z

wip

commit 108dcd2096a301f3ff9090bdc616893b45d59ea6
Author: Pavel Tupitsyn 
Date:   2017-03-21T11:52:25Z

wip

commit d62b29c32753980507aaf8d13f735fa71b676868
Author: Pavel Tupitsyn 
Date:   2017-03-21T11:52:50Z

wip

commit 79a02dc10e1137895754551ef335a5c0ad384ab5
Author: Pavel Tupitsyn 
Date:   2017-03-21T11:53:16Z

wip

commit 437767f62b8073346aeb31aeb8a328df0fc335fc
Author: Pavel Tupitsyn 
Date:   2017-03-21T12:00:18Z

wip

commit b61863c7e236ec95ee0505e70307555fbca8078e
Author: Pavel Tupitsyn 
Date:   2017-03-21T12:03:43Z

Dictionary reading works

commit a2dabb6e9a3b0a3e319bff31c8a90d218206175f
Author: Pavel Tupitsyn 
Date:   2017-03-21T12:17:21Z

Fix dict reading

commit 6c962ada8426eee8fbc21155f7ced744dbe8ee67
Author: Pavel Tupitsyn 
Date:   2017-03-21T12:19:51Z

wip

commit b8f2d42689f95f3eb5c2c99987d44829d98e80b0
Author: Pavel Tupitsyn 
Date:   2017-03-21T12:26:42Z

Merge branch 'master' into ignite-4846

commit a52f6241620c047e98dc85bbeee06fe576ab0be5
Author: Pavel Tupitsyn 
Date:   2017-03-21T12:29:50Z

cleanup




---
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 #1652: IGNITE-3682

[daradurvs]

GitHub user daradurvs opened a pull request:

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

IGNITE-3682

PR after removing ignite-2.0

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

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

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

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






---
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 #1651: IGNITE-4211

[daradurvs]

GitHub user daradurvs opened a pull request:

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

IGNITE-4211

PR after removing ignite-2.0

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

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

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

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






---
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 #1650: IGNITE-3592

[daradurvs]

GitHub user daradurvs opened a pull request:

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

IGNITE-3592

PR after removing ignite-2.0

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

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

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

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






---
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 #1649: Ignite 4558 Use BinaryArrayIdentityResolver by de...

[ezhuravl]

GitHub user ezhuravl opened a pull request:

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

Ignite 4558 Use BinaryArrayIdentityResolver by default



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

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

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

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






---
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 #1621: 1.8.4

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1648: IGNITE-4475 Simplify async API

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-4475 Simplify async API



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

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

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

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






---
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 #1647: Ignite 3018 fair

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

Ignite 3018 fair



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

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

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

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






---
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 #1603: IGNITE-4211

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1622: IGNITE-3575: CPP: Implemented remote filters for ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1436: IGNITE-4501: Improvement of connection in a clust...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1646: IGNITE-3592

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1598: IGNITE-4690: CPP: Added support for Time type

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1638: IGNITE-3487: Made _key and _val columns hidden

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1592: Ignite 4584

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1591: Ignite 4558

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1614: IGNITE-3682

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1637: IGNITE-3586: CPP: Made QueryArgument internal

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1467: IGNITE-4558 Use BinaryArrayIdentityResolver by de...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1525: IGNITE-4617: Added field-access methods for Binar...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1575: IGNITE-3018: RendezvousAffinityFunction performan...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1534: IGNITE-4650: Scan and SPI queries must go through...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1600: Ignite 3018 fair

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1629: IGNITE-3429: org.hibernate.cache.spi.CacheKey not...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1587: IGNITE-3939 Compact long zero values binary repre...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1588: ignite-4767

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1435: IGNITE-3207: Rename IgniteConfiguration.gridName

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1518: IGNITE-2703 .NET: Dynamic type registration

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1506: IGNITE-4302 binary metadata component refactored ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1633: IGNITE-4827

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1646: IGNITE-3592

[daradurvs]

GitHub user daradurvs opened a pull request:

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

IGNITE-3592



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

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

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

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


commit 6c9a058c71183cd557962b96d17eb43478272f13
Author: Vyacheslav Daradur 
Date:   2017-03-21T10:45:11Z

Merge branch 'ignite-3592-prototype' into ignite-3592; refactoring




---
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 #1579: Ignite 4755

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1507: IGNITE-4663: skip class loading when deserialize ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1512: IGNITE-4673 Object array element type is written ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #972: IGNITE-3625 IGFS: Use common naming for IGFS meta ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1566: IGNITE-824 Remove GridRandomSelfTest

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1513: IGNITE-4511: Set QueryIndexType.SORTED by default...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1346: IGNITE-4399: remove IgfsSecondaryFileSystemV2, im...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1409: Ignite 4219

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1626: IGNITE-4824 Remove: AffinityTask.affinityKey meth...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1252: IGNITE-3961 IGFS: Support direct PROXY mode invoc...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1474: IGNITE-1495 Uppercase index fields in metadata

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1251: IGNITE-2356 IGFS client should be able to failove...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1469: IGNITE-4105 Introduced separate thread pool for S...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1470: ignite-4538

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1173: IGNITE-3875 Create separate thread pool for data ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1362: IGNITE-4441 Define plugin API in .NET

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1645: Ignite 4828

[endian675]

GitHub user endian675 opened a pull request:

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

Ignite 4828

Improve distribution of keys within partitions, for partition counts that 
are a power of 2.  

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

$ git pull https://github.com/endian675/ignite ignite-4828-1

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

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


commit 4a24d452e82054bbd516a87ab1316b72f713cecd
Author: Michael Griggs 
Date:   2017-03-21T08:53:51Z

IGNITE-4828: add a new hashing method to RendezvousAffinityFunction to 
improve distribution of keys within partitions

commit 399e27768e88adbe84ac80c7fc4e99d77d1361eb
Author: Michael Griggs 
Date:   2017-03-21T09:05:10Z

IGNITE-4828: improve explanation on javadoc




---
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 #1642: Ignite-4828

[endian675]

Github user endian675 closed the pull request at:

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


---
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 #1644: IGNITE-4811

[gvvinblade]

GitHub user gvvinblade opened a pull request:

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

IGNITE-4811



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

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

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

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


commit 37543d528b5213acd878ed262f9f419c65e50fc2
Author: Igor Seliverstov 
Date:   2017-03-15T17:34:11Z

GC pressure

commit f7001b2d53938bf4d442000eb941a287e80f7ea6
Author: Igor Seliverstov 
Date:   2017-03-19T15:22:48Z

GC pressure

commit 80750ec1b4fa70821607b36569ba92710739419b
Author: Igor Seliverstov 
Date:   2017-03-20T09:56:01Z

GC pressure

commit 45af9255cdd85797ab917cd965207aa4dbc65f00
Author: Igor Seliverstov 
Date:   2017-03-20T10:29:27Z

Merge branch 'ignite-3477' into ignite-4811

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/freelist/PagesList.java

commit 47268900e48f8453a50a4ead87038ce70a28ab4b
Author: Igor Seliverstov 
Date:   2017-03-20T11:19:31Z

GC pressure

commit 3adcb1d527bea573dc3a7c86ce09bf017c19f6d1
Author: Igor Seliverstov 
Date:   2017-03-20T15:38:59Z

GC pressure

commit 01e2528fc0d15995cdf3351c3291807227082b08
Author: Igor Seliverstov 
Date:   2017-03-20T15:48:29Z

GC pressure

commit f0500da1e56d177ea4ae409addbb041f3a5dc77b
Author: Igor Seliverstov 
Date:   2017-03-21T07:24:34Z

GC pressure




---
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-4846) .NET: Support complex type dictionaries in app.config configuration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4846:
--

 Summary: .NET: Support complex type dictionaries in app.config 
configuration
 Key: IGNITE-4846
 URL: https://issues.apache.org/jira/browse/IGNITE-4846
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.0


Only primitive types are supported currently for things like 
{{IgniteConfiguration.UserAttributes}}, there is no way to specify a user type 
as a value.



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