[GitHub] ignite pull request #1677: ignite-4869 remove unnecessary benchmarks for leg...

[ezhuravl]

GitHub user ezhuravl opened a pull request:

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

ignite-4869 remove unnecessary benchmarks for legacy binary identity



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

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

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

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






---
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.
---

New blog post: LINQ vs SQL in Ignite.NET: Performance

[Pavel Tupitsyn]

Enjoy: https://ptupitsyn.github.io/LINQ-vs-SQL-in-Ignite/

Re: Ignite-4795 - ready for review

[Denis Magda]

Hello Dmitriy, thanks! Someone will have a look at your changes soon. Sorry for 
the delay.

—
Denis

> On Mar 27, 2017, at 3:24 AM, Дмитрий Рябов  wrote:
> 
> Hello, can anyone review this issue?
> 
> 2017-03-20 16:33 GMT+03:00 Дмитрий Рябов :
> 
>> Done.
>> 
>> 2017-03-20 16:30 GMT+03:00 Антон Чураев :
>> 
>>> Dmitry, thank you!
>>> 
>>> Could you please also change issue status to "Patch available".
>>> 
>>> 2017-03-20 16:01 GMT+03:00 Дмитрий Рябов :
>>> 
 Hello, community. Please, review and/or suggest something about
>>> javadocs of
 transactions.
 
 PR: https://github.com/apache/ignite/pull/1630/files
 
 JIRA: https://issues.apache.org/jira/browse/IGNITE-4795
 
>>> 
>>> 
>>> 
>>> --
>>> С уважением,
>>> Чураев Антон
>>> 
>> 
>> 

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

[Valentin Kulichenko]

Hi Rishi,

What is your username in Jira? I will add you as a contributor.

Also please go through [1] and [2] for all the details about our process.

[1] https://ignite.apache.org/community/contribute.html#contribute
[2] https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

-Val

On Sun, Mar 26, 2017 at 5:56 PM, Rishi Yagnik  wrote:

> Hi Val,
>
> I started working on it but could not assign issue to me, how do I assign
> ticket to my self ?
>
> Do I need contributor access to contribute the fix ?
>
> Please clarify..
>
> Thanks,
>
> On Fri, Mar 24, 2017 at 12:10 AM, Rishi Yagnik 
> wrote:
>
> > Hi Val,
> >
> > Sorry for the delay, I will work on the fix on weekend.
> >
> > Thanks,
> >
> >
> > On Mon, Mar 13, 2017 at 12:08 PM, Rishi Yagnik 
> > wrote:
> >
> >> Hi Val,
> >>
> >> I will work on it in my spare time..
> >>
> >> Take Care,
> >> Rishi
> >>
> >> > On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko <
> >> valentin.kuliche...@gmail.com> wrote:
> >> >
> >> > Hi Rishi,
> >> >
> >> > Can you please assign the ticket to yourself and create a pull request
> >> as
> >> > described in [1]?
> >> >
> >> > Let's follow the process :)
> >> >
> >> > [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+
> >> Contribute
> >> >
> >> > -Val
> >> >
> >> > On Sun, Mar 12, 2017 at 2:04 AM, ignite_dev2017 <
> rishiyag...@gmail.com>
> >> > wrote:
> >> >
> >> >> Hi Val,
> >> >>
> >> >> The fix which we applied as follows with SpringCacheManager -
> >> >>
> >> >> 1) Design was to listen for ignite re connect event
> >> >> 2) And clear the cache on reconnect
> >> >>
> >> >> See the following code below and let us know if this is helpful -
> >> >>
> >> >> In afterPropertiesSet -
> >> >>
> >> >> //Handles the reconnect event, on server crashes OR network failure,
> >> client
> >> >> connects to server and
> >> >>// destroy the cache
> >> >>IgnitePredicate lsnr = iEvt -> {
> >> >>LOGGER.info("Received discovery event [iEvt=" +
> iEvt.name()
> >> +
> >> >> ",
> >> >> discovery=" + iEvt.shortDisplay() + ']');
> >> >>
> >> >>caches.keySet().forEach(key -> {
> >> >>ignite.destroyCache(key);
> >> >>caches.remove(key);
> >> >>} );
> >> >>
> >> >>
> >> >>
> >> >> Let me know if you see any side effects with the fix.
> >> >>
> >> >> Thanks,
> >> >> Rishi
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> View this message in context: http://apache-ignite-
> >> >> developers.2346864.n4.nabble.com/IGNITE-2766-Spring-Cache-
> >> >> Manager-ReConnect-Issue-tp15362.html
> >> >> Sent from the Apache Ignite Developers mailing list archive at
> >> Nabble.com.
> >> >>
> >>
> >
> >
> >
> > --
> > Rishi Yagnik
> >
>
>
>
> --
> Rishi Yagnik
>

[GitHub] ignite pull request #1678: Ignite 1925

[iveselovskiy]

GitHub user iveselovskiy opened a pull request:

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

Ignite 1925



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

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

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

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


commit bfb00b6e61f9709718c30971997aeb0ac79e86b4
Author: Alexandr Kuramshin 
Date:   2016-11-18T20:12:28Z

IgniteTcpCommunicationBigClusterTest added

commit 02dd92e605b9b53f5a16c7ec5f8e7b5698b15ba4
Author: Alexandr Kuramshin 
Date:   2016-11-18T21:55:37Z

IgniteTcpCommunicationBigClusterTest update

commit 6acf193a3d356d1bad4c02a53ac76833ed1008d0
Author: Alexandr Kuramshin 
Date:   2016-11-19T09:55:45Z

Have got TcpCommunicationSpi error

commit 4fd39653d24f62f19f70b4dffba8497185cc46fb
Author: Alexandr Kuramshin 
Date:   2016-11-19T16:39:10Z

Some discovery have been done

commit c2c181922c7c24ea457577e32d2af897c8bec87f
Author: Alexandr Kuramshin 
Date:   2016-11-19T20:11:28Z

Prove that problem is not in the onFirstMessage hang

commit f8076edba097f6077229b2090ee3ff1a3369878c
Author: Alexandr Kuramshin 
Date:   2016-11-19T20:26:37Z

Revert: Prove that problem is not in the onFirstMessage hang

commit 6e1f2dfc2acb3dbb8f24aa51ed67b2ee447b4585
Author: Alexandr Kuramshin 
Date:   2016-11-21T08:55:09Z

Revert: pushing unnecessary changes to the master

commit ed794ca815f6bb1471af15779279d287576b39cc
Author: Alexandr Kuramshin 
Date:   2016-11-21T09:08:00Z

Revert: pushing unnecessary changes to the master

commit 3a57d63668bed239e21eca588134272783472e97
Author: iveselovskiy 
Date:   2016-12-09T14:13:37Z

Merge branch 'master' of https://github.com/apache/ignite

commit 166ad21d560c41c42a6de81cf5910537baa3ac92
Author: iveselovskiy 
Date:   2016-12-12T18:46:44Z

Merge branch 'master' of https://github.com/apache/ignite

commit 1eaba3e91bfe54c2bf6f761ac3f238a3b181a8e0
Author: iveselovskiy 
Date:   2017-03-27T18:41:07Z

Merge branch 'master' of https://github.com/apache/ignite

commit 52536ca623f4dcb7f4b76578cf6d2696116c4817
Author: iveselovskiy 
Date:   2017-03-27T18:52:32Z

IGNITE-1925: base version of the fix, test passes locally.




---
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 #1679: IGNITE-4575: Added enum support to SQL queries

[skalashnikov]

GitHub user skalashnikov opened a pull request:

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

IGNITE-4575: Added enum support to SQL queries



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

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

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

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


commit 60dd521b09d23aeed77acc70adda67c8e19a2db1
Author: skalashnikov 
Date:   2017-03-27T20:01:26Z

IGNITE-4575: Added enum support to SQL queries




---
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: IGNITE-2766 Spring Cache Manager ReConnect Issue

[Rishi Yagnik]

Hi Val,

My user name is ryagnik

Thanks,
Rishi

On Mon, Mar 27, 2017 at 12:14 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> What is your username in Jira? I will add you as a contributor.
>
> Also please go through [1] and [2] for all the details about our process.
>
> [1] https://ignite.apache.org/community/contribute.html#contribute
> [2] https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
>
> -Val
>
> On Sun, Mar 26, 2017 at 5:56 PM, Rishi Yagnik 
> wrote:
>
> > Hi Val,
> >
> > I started working on it but could not assign issue to me, how do I assign
> > ticket to my self ?
> >
> > Do I need contributor access to contribute the fix ?
> >
> > Please clarify..
> >
> > Thanks,
> >
> > On Fri, Mar 24, 2017 at 12:10 AM, Rishi Yagnik 
> > wrote:
> >
> > > Hi Val,
> > >
> > > Sorry for the delay, I will work on the fix on weekend.
> > >
> > > Thanks,
> > >
> > >
> > > On Mon, Mar 13, 2017 at 12:08 PM, Rishi Yagnik 
> > > wrote:
> > >
> > >> Hi Val,
> > >>
> > >> I will work on it in my spare time..
> > >>
> > >> Take Care,
> > >> Rishi
> > >>
> > >> > On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko <
> > >> valentin.kuliche...@gmail.com> wrote:
> > >> >
> > >> > Hi Rishi,
> > >> >
> > >> > Can you please assign the ticket to yourself and create a pull
> request
> > >> as
> > >> > described in [1]?
> > >> >
> > >> > Let's follow the process :)
> > >> >
> > >> > [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+
> > >> Contribute
> > >> >
> > >> > -Val
> > >> >
> > >> > On Sun, Mar 12, 2017 at 2:04 AM, ignite_dev2017 <
> > rishiyag...@gmail.com>
> > >> > wrote:
> > >> >
> > >> >> Hi Val,
> > >> >>
> > >> >> The fix which we applied as follows with SpringCacheManager -
> > >> >>
> > >> >> 1) Design was to listen for ignite re connect event
> > >> >> 2) And clear the cache on reconnect
> > >> >>
> > >> >> See the following code below and let us know if this is helpful -
> > >> >>
> > >> >> In afterPropertiesSet -
> > >> >>
> > >> >> //Handles the reconnect event, on server crashes OR network
> failure,
> > >> client
> > >> >> connects to server and
> > >> >>// destroy the cache
> > >> >>IgnitePredicate lsnr = iEvt -> {
> > >> >>LOGGER.info("Received discovery event [iEvt=" +
> > iEvt.name()
> > >> +
> > >> >> ",
> > >> >> discovery=" + iEvt.shortDisplay() + ']');
> > >> >>
> > >> >>caches.keySet().forEach(key -> {
> > >> >>ignite.destroyCache(key);
> > >> >>caches.remove(key);
> > >> >>} );
> > >> >>
> > >> >>
> > >> >>
> > >> >> Let me know if you see any side effects with the fix.
> > >> >>
> > >> >> Thanks,
> > >> >> Rishi
> > >> >>
> > >> >>
> > >> >>
> > >> >> --
> > >> >> View this message in context: http://apache-ignite-
> > >> >> developers.2346864.n4.nabble.com/IGNITE-2766-Spring-Cache-
> > >> >> Manager-ReConnect-Issue-tp15362.html
> > >> >> Sent from the Apache Ignite Developers mailing list archive at
> > >> Nabble.com.
> > >> >>
> > >>
> > >
> > >
> > >
> > > --
> > > Rishi Yagnik
> > >
> >
> >
> >
> > --
> > Rishi Yagnik
> >
>



-- 
Rishi Yagnik

[jira] [Created] (IGNITE-4870) .NET: QueryEntity.TableName

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4870:
--

 Summary: .NET: QueryEntity.TableName
 Key: IGNITE-4870
 URL: https://issues.apache.org/jira/browse/IGNITE-4870
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Add {{QueryEntity.TableName}} property and propagate to Java configuration.



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

[GitHub] ignite pull request #1501: IGNITE-3579 Change lenght of the message type fro...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/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 #1673: IGNITE-4838 Check task class on null when task na...

[vsisko]

GitHub user vsisko opened a pull request:

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

IGNITE-4838 Check task class on null when task name is invalid.



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

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

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

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


commit 68a67c3bf1a3a8400a25be3175862c32d8626e9e
Author: vsisko 
Date:   2017-03-27T08:47:37Z

IGNITE-4838 Check task class on null when task name is invalid.




---
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 #1674: IGNITE-4534: Implement offheap eviction policies ...

[glukos]

GitHub user glukos opened a pull request:

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

IGNITE-4534: Implement offheap eviction policies based on page memory

Per-page eviction policies are implemented, algorithm (random-LRU or 
random-K-LRU) can be configured in MemoryPolicyConfiguration.

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

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

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

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


commit 60ea031ebf19a7b6b8a205d762ae3b96ef2ed1ba
Author: Ivan Rakov 
Date:   2017-02-28T10:56:40Z

IGNITE-4534: First approach to evict by page index

commit c5d45a4fa575a444537db7a933a8f489574ccf83
Author: Ivan Rakov 
Date:   2017-02-28T11:35:36Z

IGNITE-4534: First approach to evict by page index

commit 27d024048bf6689e59548bfdf67461665b9ee06b
Author: Ivan Rakov 
Date:   2017-03-02T17:34:19Z

IGNITE-4534: Random-LRU implemented

commit 0b7c770e4e12826e45a7716ec408129f68cf6ebb
Author: Ivan Rakov 
Date:   2017-03-03T12:04:00Z

IGNITE-4534: Bugs fixed. Works fine for small objects, found bug with big 
objects (size > pageSize)

commit a8d74454f6e0c67632c5a2f2a10a41e8e2fcbe12
Author: Ivan Rakov 
Date:   2017-03-03T13:02:13Z

IGNITE-4534: Smoke test added

commit f5ff54a9945477768bf74161c8c51d4ce83d4b62
Author: Sergey Chugunov 
Date:   2017-03-02T16:24:20Z

IGNITE-4758 multiple MemoryPolicies were implemented

commit 5479f947f672e28fc39f92e8a489c016f96d10f0
Author: Sergey Chugunov 
Date:   2017-03-09T10:17:45Z

Merge branch 'ignite-3477' into ignite-4758

commit db1087e28f438c494d96afea92de2b454f369c46
Author: Sergey Chugunov 
Date:   2017-03-09T12:13:17Z

IGNITE-4758 added back 'freeList' parameter on RowStore constructor

commit 4cd7cfab87f385fd6633f866d7f63625c010b649
Author: Ivan Rakov 
Date:   2017-03-13T12:17:24Z

IGNITE-4534: Fixed bug with reading fragmented data row

commit 26458a89bef395325232172dfcc20403c8d00eaa
Author: Ivan Rakov 
Date:   2017-03-13T12:39:23Z

Merge branch 'ignite-4758' into ignite-4534

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

commit a0ae590e0411a1d029dfc515edf66fe45eb7635b
Author: Ivan Rakov 
Date:   2017-03-13T15:00:22Z

IGNITE-4578: Refactoring - configuration is now available from policy; 
memory policy map is introduced.

commit df92f49048905a0245cf1daa0499cf96dd3c7238
Author: Ivan Rakov 
Date:   2017-03-13T15:01:13Z

Merge branch 'ignite-4758' into ignite-4534

commit 9a5a4f17940ee902b27cd06998fb235553e4dea9
Author: Ivan Rakov 
Date:   2017-03-13T16:54:14Z

IGNITE-4534: Integrated memory policy changes

commit 9eaa00ef1a0d0124a23b59ef1245fa4e6df25478
Author: Sergey Chugunov 
Date:   2017-03-13T16:20:12Z

IGNITE-4758 Indexing SPI tests fix, CPP tests configs refactoring, 
documentation improvements

commit 89ce9b672223110b7f3b2ab36117772e9ddae06b
Author: Sergey Chugunov 
Date:   2017-03-15T08:40:41Z

IGNITE-4758 some tests were added, code was improved to avoid NPE on client 
nodes, documentation was detailed

commit bf491b3a2fe94d05ff77d812809c02ce908036cf
Author: Sergey Chugunov 
Date:   2017-03-16T11:16:51Z

IGNITE-4758 NPE on metrics gathering on client node was fixed

commit a4cbde0cfe25e9e40ba06882dc97b5d815cb4cf6
Author: Sergey Chugunov 
Date:   2017-03-20T14:27:53Z

IGNITE-4758 bug with initializing default memory pool was fixed

commit 1faea11b1e3f360b592cecd88149d86d8ba30e3a
Author: Ivan Rakov 
Date:   2017-03-20T17:14:53Z

Merge branch 'ignite-4758' into ignite-4534

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

commit df37f1f04d73a70ffd80c4bc6022a395ca7846ce
Author: Ivan Rakov 
Date:   2017-03-20T17:16:52Z

Fixing after merging ignite-4758

commit a418d39aac710c4fa4a4e4801d67ef467a5a9ded
Author: Ivan Rakov 
Date:   2017-03-22T15:04:03Z

IGNITE-4534: Offheap eviction concept implemented, ready for tests

commit 77dd1e32db7be500f3db3f9993747759c05a89fa
Author: Ivan Rakov 

[jira] [Created] (IGNITE-4866) Add lazy value deserialization in GridCacheRawVersionedEntry

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-4866:
---

 Summary: Add lazy value deserialization in 
GridCacheRawVersionedEntry
 Key: IGNITE-4866
 URL: https://issues.apache.org/jira/browse/IGNITE-4866
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitry Karachentsev
Assignee: Dmitry Karachentsev






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

[jira] [Created] (IGNITE-4865) Non-informative error message on using GridClientOptimizedMarshaller with unknown task classes

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-4865:
--

 Summary: Non-informative error message on using 
GridClientOptimizedMarshaller with unknown task classes
 Key: IGNITE-4865
 URL: https://issues.apache.org/jira/browse/IGNITE-4865
 Project: Ignite
  Issue Type: Improvement
  Components: rest
Affects Versions: 2.0
Reporter: Alexandr Kuramshin
Assignee: Alexandr Kuramshin


Upon {{GridClientCompute.execute()}} I get non-informative error if a task 
class is not present in {{classnames.properties}}. It occurs when 
{{GridClient}} was configured to use {{GridClientOptimizedMarshaller}}.

{noformat}
Closing NIO session because of unhandled exception [cls=class 
o.a.i.i.util.nio.GridNioException, msg=class o.a.i.IgniteCheckedException: 
Failed to deserialize object with given class loader: null]
{noformat}

There is two problems:
* Actual problem was hidden
{noformat}
Caused by: java.lang.UnsupportedOperationException
at 
org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller$ClientMarshallerContext.className(GridClientOptimizedMarshaller.java:137)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:266)
at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:318)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:367)
{noformat}
* Even reading the cause we don't understand what is wrong

What to do:
* Log stacktrace every time
* Throw UnsupportedOperationException with informative message.



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

question about peeking entry from cache

[ALEKSEY KUZNETSOV]

Hi all! There is method that peek cache entry from a cache
org.apache.ignite.internal.processors.cache.GridCacheAdapter#peekEx(java.lang.Object)

And there is another method:

org.apache.ignite.internal.processors.cache.GridCacheMapEntry#peek(boolean,
boolean, boolean,
org.apache.ignite.internal.processors.cache.IgniteCacheExpiryPolicy)

What is the difference between them?
-- 

*Best Regards,*

*Kuznetsov Aleksey*

[GitHub] ignite pull request #1675: IGNITE-4865 Verbose logging, informative messages

[akuramshingg]

GitHub user akuramshingg opened a pull request:

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

IGNITE-4865 Verbose logging, informative messages



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

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

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

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


commit c66889a45ae2b38d03fd06e3f437b551bd7906ab
Author: Alexandr Kuramshin 
Date:   2017-03-27T10:16:22Z

IGNITE-4865 Verbose logging, informative messages




---
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.
---

IgniteFuture adapters

[Sergei Egorov]

Hi!

Would be nice if igniteFuture would provide a small but very usable method:

public  R to(Function transformer)

it will allow to chain it like:

compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()

Where rx() is just a static function with something like:

   public static  Function rx()


WDYT?

[jira] [Created] (IGNITE-4864) .NET: Support arrays in SQL

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4864:
--

 Summary: .NET: Support arrays in SQL
 Key: IGNITE-4864
 URL: https://issues.apache.org/jira/browse/IGNITE-4864
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Ignite SQL supports arrays, for example, string array can be configured via 
{{QueryEntity.ValueTypeName = "L[java.lang.String;";}} and then queried with 
{{WHERE array_contains(ABC, ?);}}.

* Update {{JavaTypes}} with array mappings
* Add tests to make sure results and arguments are passed properly
* Add support in LINQ (separate ticket?)



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

Re: Ignite-4795 - ready for review

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

Hello, can anyone review this issue?

2017-03-20 16:33 GMT+03:00 Дмитрий Рябов :

> Done.
>
> 2017-03-20 16:30 GMT+03:00 Антон Чураев :
>
>> Dmitry, thank you!
>>
>> Could you please also change issue status to "Patch available".
>>
>> 2017-03-20 16:01 GMT+03:00 Дмитрий Рябов :
>>
>> > Hello, community. Please, review and/or suggest something about
>> javadocs of
>> > transactions.
>> >
>> > PR: https://github.com/apache/ignite/pull/1630/files
>> >
>> > JIRA: https://issues.apache.org/jira/browse/IGNITE-4795
>> >
>>
>>
>>
>> --
>> С уважением,
>> Чураев Антон
>>
>
>

Re: Make async API great again

[Vladimir Ozerov]

Igniters,

I am glad to announce that old async-style is finally deprecated and now
all asynchronous methods are defined explicitly! Woohoo! Thanks to Taras
for this important contribution.

On Mon, Jan 23, 2017 at 6:12 PM, Taras Ledkov  wrote:

> Each compute method produces task. For 'run', 'call' etc. methods the
> classes of tasks are internal.
> There are tests checking the task session by ComputeTaskFuture for these
> methods.
> I think we have to leave real class of future is
> ComputeTaskInternalFuture#ComputeFuture to compatibility.
>
> The class of the future at the public API may be changed.
>
>
>
> On 20.01.2017 17:54, Vladimir Ozerov wrote:
>
>> IgniteCompute was designed this way initially. See IgniteCompute.future()
>> override. May be it makes sense to leave this type only for execute(...)
>> methods.
>>
>> On Fri, Jan 20, 2017 at 5:45 PM, Semyon Boikov 
>> wrote:
>>
>> Hi Taras,
>>>
>>> Why 'async' methods return ComputeTaskFuture, not just IgniteFuture? It
>>> seems that ComputeTaskFuture is needed only for tasks?
>>>
>>>
>>>
>>>
>>> On Fri, Jan 20, 2017 at 5:18 PM, Taras Ledkov 
>>> wrote:
>>>
>>> Gents

 I've done changes of the IgniteCompute as a subtask of the whole async

>>> API
>>>
 refactoring (https://issues.apache.org/jira/browse/IGNITE-4580).
 Please check the new version of the public API (
 https://github.com/gridgain/apache-ignite/blob/b81621bf2e8a
 35b20989f95ff52c0f6d91dd75d6/modules/core/src/main/java/
 org/apache/ignite/IgniteCompute.java)

 Please look through the new API and let me know any comments.

 --
 Taras Ledkov
 Mail-To: tled...@gridgain.com



> --
> Taras Ledkov
> Mail-To: tled...@gridgain.com
>
>

[jira] [Created] (IGNITE-4867) CacheMetricsSnapshot ignores 'size' and 'keySize' fields

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-4867:
---

 Summary: CacheMetricsSnapshot ignores 'size' and 'keySize' fields
 Key: IGNITE-4867
 URL: https://issues.apache.org/jira/browse/IGNITE-4867
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitry Karachentsev


'size' and 'keySize' fields in CacheMetricsSnapshot must be serialized and 
properly processed to show correct values in CacheClusterMetricsMXBeanImpl.



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

Re: IgniteFuture adapters

[Sergei Egorov]

It doesn't :)

It returns another IgniteFuture where I want to transform it to completely
different type.

On Mon, Mar 27, 2017 at 1:41 PM Дмитрий Рябов  wrote:

> IgniteFuture have method
>
> public  IgniteFuture chain(IgniteClosure, T>
> doneCb);
>
> which do this.
>
> 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
>
> > Hi!
> >
> > Would be nice if igniteFuture would provide a small but very usable
> method:
> >
> > public  R to(Function transformer)
> >
> > it will allow to chain it like:
> >
> > compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> >
> > Where rx() is just a static function with something like:
> >
> >public static  Function rx()
> >
> >
> > WDYT?
> >
>
>
> 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
>
> > Hi!
> >
> > Would be nice if igniteFuture would provide a small but very usable
> method:
> >
> > public  R to(Function transformer)
> >
> > it will allow to chain it like:
> >
> > compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> >
> > Where rx() is just a static function with something like:
> >
> >public static  Function rx()
> >
> >
> > WDYT?
> >
>

[GitHub] ignite pull request #1654: IGNITE-4827 Remove deprecated code related to bac...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: IgniteFuture adapters

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

IgniteFuture have method

public  IgniteFuture chain(IgniteClosure, T>
doneCb);

which do this.

2017-03-27 13:30 GMT+03:00 Sergei Egorov :

> Hi!
>
> Would be nice if igniteFuture would provide a small but very usable method:
>
> public  R to(Function transformer)
>
> it will allow to chain it like:
>
> compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
>
> Where rx() is just a static function with something like:
>
>public static  Function rx()
>
>
> WDYT?
>


2017-03-27 13:30 GMT+03:00 Sergei Egorov :

> Hi!
>
> Would be nice if igniteFuture would provide a small but very usable method:
>
> public  R to(Function transformer)
>
> it will allow to chain it like:
>
> compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
>
> Where rx() is just a static function with something like:
>
>public static  Function rx()
>
>
> WDYT?
>

[GitHub] ignite pull request #1649: Ignite 4558 Use BinaryArrayIdentityResolver by de...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/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 #1668: IGNITE-4351 .NET: Use BinaryArrayIdentityResolver...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Make async API great again

[Sergei Egorov]

Cool!

Please check my neighboring thread about special .to() method on
IgniteFuture to make it even better :)

On Mon, Mar 27, 2017 at 1:32 PM Vladimir Ozerov 
wrote:

> Igniters,
>
> I am glad to announce that old async-style is finally deprecated and now
> all asynchronous methods are defined explicitly! Woohoo! Thanks to Taras
> for this important contribution.
>
> On Mon, Jan 23, 2017 at 6:12 PM, Taras Ledkov 
> wrote:
>
> > Each compute method produces task. For 'run', 'call' etc. methods the
> > classes of tasks are internal.
> > There are tests checking the task session by ComputeTaskFuture for these
> > methods.
> > I think we have to leave real class of future is
> > ComputeTaskInternalFuture#ComputeFuture to compatibility.
> >
> > The class of the future at the public API may be changed.
> >
> >
> >
> > On 20.01.2017 17:54, Vladimir Ozerov wrote:
> >
> >> IgniteCompute was designed this way initially. See
> IgniteCompute.future()
> >> override. May be it makes sense to leave this type only for execute(...)
> >> methods.
> >>
> >> On Fri, Jan 20, 2017 at 5:45 PM, Semyon Boikov 
> >> wrote:
> >>
> >> Hi Taras,
> >>>
> >>> Why 'async' methods return ComputeTaskFuture, not just IgniteFuture? It
> >>> seems that ComputeTaskFuture is needed only for tasks?
> >>>
> >>>
> >>>
> >>>
> >>> On Fri, Jan 20, 2017 at 5:18 PM, Taras Ledkov 
> >>> wrote:
> >>>
> >>> Gents
> 
>  I've done changes of the IgniteCompute as a subtask of the whole async
> 
> >>> API
> >>>
>  refactoring (https://issues.apache.org/jira/browse/IGNITE-4580).
>  Please check the new version of the public API (
>  https://github.com/gridgain/apache-ignite/blob/b81621bf2e8a
>  35b20989f95ff52c0f6d91dd75d6/modules/core/src/main/java/
>  org/apache/ignite/IgniteCompute.java)
> 
>  Please look through the new API and let me know any comments.
> 
>  --
>  Taras Ledkov
>  Mail-To: tled...@gridgain.com
> 
> 
> 
> > --
> > Taras Ledkov
> > Mail-To: tled...@gridgain.com
> >
> >
>

Re: IgniteFuture adapters

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

Em... When you get result of your future, closure will produce new future
with completely different type.

2017-03-27 13:43 GMT+03:00 Sergei Egorov :

> It doesn't :)
>
> It returns another IgniteFuture where I want to transform it to completely
> different type.
>
> On Mon, Mar 27, 2017 at 1:41 PM Дмитрий Рябов 
> wrote:
>
> > IgniteFuture have method
> >
> > public  IgniteFuture chain(IgniteClosure,
> T>
> > doneCb);
> >
> > which do this.
> >
> > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> >
> > > Hi!
> > >
> > > Would be nice if igniteFuture would provide a small but very usable
> > method:
> > >
> > > public  R to(Function transformer)
> > >
> > > it will allow to chain it like:
> > >
> > > compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> > >
> > > Where rx() is just a static function with something like:
> > >
> > >public static  Function rx()
> > >
> > >
> > > WDYT?
> > >
> >
> >
> > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> >
> > > Hi!
> > >
> > > Would be nice if igniteFuture would provide a small but very usable
> > method:
> > >
> > > public  R to(Function transformer)
> > >
> > > it will allow to chain it like:
> > >
> > > compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> > >
> > > Where rx() is just a static function with something like:
> > >
> > >public static  Function rx()
> > >
> > >
> > > WDYT?
> > >
> >
>

[jira] [Created] (IGNITE-4868) SQL: Entry can't be removed from index with 'Object.class' key type configured.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-4868:


 Summary: SQL: Entry can't be removed from index with 
'Object.class' key type configured.
 Key: IGNITE-4868
 URL: https://issues.apache.org/jira/browse/IGNITE-4868
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Reporter: Andrew Mashenkov






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

[jira] [Created] (IGNITE-4869) Unnecessary benchmarcs for legacy minary identity

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-4869:
-

 Summary: Unnecessary benchmarcs for legacy minary identity
 Key: IGNITE-4869
 URL: https://issues.apache.org/jira/browse/IGNITE-4869
 Project: Ignite
  Issue Type: Bug
Reporter: Evgenii Zhuravlev
Assignee: Evgenii Zhuravlev
Priority: Critical
 Fix For: 2.0


IgniteLegacyBinaryIdentityPutBenchmark & IgniteLegacyBinaryIdentityGetBenchmark 
isn't needed after removing BinaryObjectBuilder.hashCode(int) method 



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

Re: Make async API great again

[Denis Magda]

Promising beginning of the week! So many talks in the past and finally we came 
to the logical end.

Thanks to both of you Taras and Vovan to making this real ;)

Could any of you update the Migration Guide simplifying the life for those who 
will be migrating from AI 1.x?
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
 


—
Denis

> On Mar 27, 2017, at 3:24 AM, Vladimir Ozerov  wrote:
> 
> Igniters,
> 
> I am glad to announce that old async-style is finally deprecated and now
> all asynchronous methods are defined explicitly! Woohoo! Thanks to Taras
> for this important contribution.
> 
> On Mon, Jan 23, 2017 at 6:12 PM, Taras Ledkov  wrote:
> 
>> Each compute method produces task. For 'run', 'call' etc. methods the
>> classes of tasks are internal.
>> There are tests checking the task session by ComputeTaskFuture for these
>> methods.
>> I think we have to leave real class of future is
>> ComputeTaskInternalFuture#ComputeFuture to compatibility.
>> 
>> The class of the future at the public API may be changed.
>> 
>> 
>> 
>> On 20.01.2017 17:54, Vladimir Ozerov wrote:
>> 
>>> IgniteCompute was designed this way initially. See IgniteCompute.future()
>>> override. May be it makes sense to leave this type only for execute(...)
>>> methods.
>>> 
>>> On Fri, Jan 20, 2017 at 5:45 PM, Semyon Boikov 
>>> wrote:
>>> 
>>> Hi Taras,
 
 Why 'async' methods return ComputeTaskFuture, not just IgniteFuture? It
 seems that ComputeTaskFuture is needed only for tasks?
 
 
 
 
 On Fri, Jan 20, 2017 at 5:18 PM, Taras Ledkov 
 wrote:
 
 Gents
> 
> I've done changes of the IgniteCompute as a subtask of the whole async
> 
 API
 
> refactoring (https://issues.apache.org/jira/browse/IGNITE-4580).
> Please check the new version of the public API (
> https://github.com/gridgain/apache-ignite/blob/b81621bf2e8a
> 35b20989f95ff52c0f6d91dd75d6/modules/core/src/main/java/
> org/apache/ignite/IgniteCompute.java)
> 
> Please look through the new API and let me know any comments.
> 
> --
> Taras Ledkov
> Mail-To: tled...@gridgain.com
> 
> 
> 
>> --
>> Taras Ledkov
>> Mail-To: tled...@gridgain.com
>> 
>> 

[GitHub] ignite pull request #1670: IGNITE-4102 .NET: Generify ICacheStore

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: IgniteFuture adapters

[Alexey Goncharuk]

Sergei,

Why should this method be a part of the future API? The only implementation
will do "return func(this);"

I can achieve the same result the following way:
rx(compute.runAsync(runnable)).timeout(5_000).subscribe();



2017-03-27 15:54 GMT+03:00 Sergei Egorov :

> Take a look at my initial code.
>
> public  IgniteFuture chain(IgniteClosure IgniteFuture, T> doneCb);
>
> vs
>
> public  R to(IgniteClosure, R> transformer);
>
>
> The result of "chain" is IgniteFuture.
>
> The result of "to" is the object returned from transformer. It would
> be CompletableFuture, Rx's Observable, Reactor's Mono, etc...
>
>
> On Mon, Mar 27, 2017 at 3:18 PM Дмитрий Рябов 
> wrote:
>
> > Em... When you get result of your future, closure will produce new future
> > with completely different type.
> >
> > 2017-03-27 13:43 GMT+03:00 Sergei Egorov :
> >
> > > It doesn't :)
> > >
> > > It returns another IgniteFuture where I want to transform it to
> > completely
> > > different type.
> > >
> > > On Mon, Mar 27, 2017 at 1:41 PM Дмитрий Рябов 
> > > wrote:
> > >
> > > > IgniteFuture have method
> > > >
> > > > public  IgniteFuture chain(IgniteClosure IgniteFuture,
> > > T>
> > > > doneCb);
> > > >
> > > > which do this.
> > > >
> > > > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> > > >
> > > > > Hi!
> > > > >
> > > > > Would be nice if igniteFuture would provide a small but very usable
> > > > method:
> > > > >
> > > > > public  R to(Function transformer)
> > > > >
> > > > > it will allow to chain it like:
> > > > >
> > > > > compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> > > > >
> > > > > Where rx() is just a static function with something like:
> > > > >
> > > > >public static  Function rx()
> > > > >
> > > > >
> > > > > WDYT?
> > > > >
> > > >
> > > >
> > > > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> > > >
> > > > > Hi!
> > > > >
> > > > > Would be nice if igniteFuture would provide a small but very usable
> > > > method:
> > > > >
> > > > > public  R to(Function transformer)
> > > > >
> > > > > it will allow to chain it like:
> > > > >
> > > > > compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> > > > >
> > > > > Where rx() is just a static function with something like:
> > > > >
> > > > >public static  Function rx()
> > > > >
> > > > >
> > > > > WDYT?
> > > > >
> > > >
> > >
> >
>

Re: IgniteFuture adapters

[Sergei Egorov]

True, I just prefer functional style over static methods.

Regarding "why should this method be a part of the future API" - why not?
It helps to chain such calls instead of call nesting.

Of course, if Java had extension methods it wouldn't be needed, but we
don't have them.

On Mon, Mar 27, 2017 at 4:06 PM Alexey Goncharuk 
wrote:

> Sergei,
>
> Why should this method be a part of the future API? The only implementation
> will do "return func(this);"
>
> I can achieve the same result the following way:
> rx(compute.runAsync(runnable)).timeout(5_000).subscribe();
>
>
>
> 2017-03-27 15:54 GMT+03:00 Sergei Egorov :
>
> > Take a look at my initial code.
> >
> > public  IgniteFuture chain(IgniteClosure > IgniteFuture, T> doneCb);
> >
> > vs
> >
> > public  R to(IgniteClosure, R> transformer);
> >
> >
> > The result of "chain" is IgniteFuture.
> >
> > The result of "to" is the object returned from transformer. It would
> > be CompletableFuture, Rx's Observable, Reactor's Mono, etc...
> >
> >
> > On Mon, Mar 27, 2017 at 3:18 PM Дмитрий Рябов 
> > wrote:
> >
> > > Em... When you get result of your future, closure will produce new
> future
> > > with completely different type.
> > >
> > > 2017-03-27 13:43 GMT+03:00 Sergei Egorov :
> > >
> > > > It doesn't :)
> > > >
> > > > It returns another IgniteFuture where I want to transform it to
> > > completely
> > > > different type.
> > > >
> > > > On Mon, Mar 27, 2017 at 1:41 PM Дмитрий Рябов  >
> > > > wrote:
> > > >
> > > > > IgniteFuture have method
> > > > >
> > > > > public  IgniteFuture chain(IgniteClosure > IgniteFuture,
> > > > T>
> > > > > doneCb);
> > > > >
> > > > > which do this.
> > > > >
> > > > > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> > > > >
> > > > > > Hi!
> > > > > >
> > > > > > Would be nice if igniteFuture would provide a small but very
> usable
> > > > > method:
> > > > > >
> > > > > > public  R to(Function transformer)
> > > > > >
> > > > > > it will allow to chain it like:
> > > > > >
> > > > > >
>  compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> > > > > >
> > > > > > Where rx() is just a static function with something like:
> > > > > >
> > > > > >public static  Function
> rx()
> > > > > >
> > > > > >
> > > > > > WDYT?
> > > > > >
> > > > >
> > > > >
> > > > > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> > > > >
> > > > > > Hi!
> > > > > >
> > > > > > Would be nice if igniteFuture would provide a small but very
> usable
> > > > > method:
> > > > > >
> > > > > > public  R to(Function transformer)
> > > > > >
> > > > > > it will allow to chain it like:
> > > > > >
> > > > > >
>  compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> > > > > >
> > > > > > Where rx() is just a static function with something like:
> > > > > >
> > > > > >public static  Function
> rx()
> > > > > >
> > > > > >
> > > > > > WDYT?
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: IgniteFuture adapters

[Sergei Egorov]

Take a look at my initial code.

public  IgniteFuture chain(IgniteClosure, T> doneCb);

vs

public  R to(IgniteClosure, R> transformer);


The result of "chain" is IgniteFuture.

The result of "to" is the object returned from transformer. It would
be CompletableFuture, Rx's Observable, Reactor's Mono, etc...


On Mon, Mar 27, 2017 at 3:18 PM Дмитрий Рябов  wrote:

> Em... When you get result of your future, closure will produce new future
> with completely different type.
>
> 2017-03-27 13:43 GMT+03:00 Sergei Egorov :
>
> > It doesn't :)
> >
> > It returns another IgniteFuture where I want to transform it to
> completely
> > different type.
> >
> > On Mon, Mar 27, 2017 at 1:41 PM Дмитрий Рябов 
> > wrote:
> >
> > > IgniteFuture have method
> > >
> > > public  IgniteFuture chain(IgniteClosure,
> > T>
> > > doneCb);
> > >
> > > which do this.
> > >
> > > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> > >
> > > > Hi!
> > > >
> > > > Would be nice if igniteFuture would provide a small but very usable
> > > method:
> > > >
> > > > public  R to(Function transformer)
> > > >
> > > > it will allow to chain it like:
> > > >
> > > > compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> > > >
> > > > Where rx() is just a static function with something like:
> > > >
> > > >public static  Function rx()
> > > >
> > > >
> > > > WDYT?
> > > >
> > >
> > >
> > > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> > >
> > > > Hi!
> > > >
> > > > Would be nice if igniteFuture would provide a small but very usable
> > > method:
> > > >
> > > > public  R to(Function transformer)
> > > >
> > > > it will allow to chain it like:
> > > >
> > > > compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
> > > >
> > > > Where rx() is just a static function with something like:
> > > >
> > > >public static  Function rx()
> > > >
> > > >
> > > > WDYT?
> > > >
> > >
> >
>

Re: IgniteFuture adapters

[Vladimir Ozerov]

+1 to Alex, this is something external to IgniteFuture.

Should Ignite was implemented in .NET, we could have add proposed feature
it using extension methods. But (un)fortunately Ignite is Java-based :-)

On Mon, Mar 27, 2017 at 4:06 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Sergei,
>
> Why should this method be a part of the future API? The only implementation
> will do "return func(this);"
>
> I can achieve the same result the following way:
> rx(compute.runAsync(runnable)).timeout(5_000).subscribe();
>
>
>
> 2017-03-27 15:54 GMT+03:00 Sergei Egorov :
>
> > Take a look at my initial code.
> >
> > public  IgniteFuture chain(IgniteClosure > IgniteFuture, T> doneCb);
> >
> > vs
> >
> > public  R to(IgniteClosure, R> transformer);
> >
> >
> > The result of "chain" is IgniteFuture.
> >
> > The result of "to" is the object returned from transformer. It would
> > be CompletableFuture, Rx's Observable, Reactor's Mono, etc...
> >
> >
> > On Mon, Mar 27, 2017 at 3:18 PM Дмитрий Рябов 
> > wrote:
> >
> > > Em... When you get result of your future, closure will produce new
> future
> > > with completely different type.
> > >
> > > 2017-03-27 13:43 GMT+03:00 Sergei Egorov :
> > >
> > > > It doesn't :)
> > > >
> > > > It returns another IgniteFuture where I want to transform it to
> > > completely
> > > > different type.
> > > >
> > > > On Mon, Mar 27, 2017 at 1:41 PM Дмитрий Рябов  >
> > > > wrote:
> > > >
> > > > > IgniteFuture have method
> > > > >
> > > > > public  IgniteFuture chain(IgniteClosure > IgniteFuture,
> > > > T>
> > > > > doneCb);
> > > > >
> > > > > which do this.
> > > > >
> > > > > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> > > > >
> > > > > > Hi!
> > > > > >
> > > > > > Would be nice if igniteFuture would provide a small but very
> usable
> > > > > method:
> > > > > >
> > > > > > public  R to(Function transformer)
> > > > > >
> > > > > > it will allow to chain it like:
> > > > > >
> > > > > > compute.runAsync(runnable).to(rx()).timeout(5_000).
> subscribe()
> > > > > >
> > > > > > Where rx() is just a static function with something like:
> > > > > >
> > > > > >public static  Function
> rx()
> > > > > >
> > > > > >
> > > > > > WDYT?
> > > > > >
> > > > >
> > > > >
> > > > > 2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> > > > >
> > > > > > Hi!
> > > > > >
> > > > > > Would be nice if igniteFuture would provide a small but very
> usable
> > > > > method:
> > > > > >
> > > > > > public  R to(Function transformer)
> > > > > >
> > > > > > it will allow to chain it like:
> > > > > >
> > > > > > compute.runAsync(runnable).to(rx()).timeout(5_000).
> subscribe()
> > > > > >
> > > > > > Where rx() is just a static function with something like:
> > > > > >
> > > > > >public static  Function
> rx()
> > > > > >
> > > > > >
> > > > > > WDYT?
> > > > > >
> > > > >
> > > >
> > >
> >
>

Adding Kubernetes IP finder to Web Console IP finders list

[Denis Magda]

Alex,

Presently, if to go to the Clusters configuration in Web Console it won’t be 
possible to set Kubernetes IP finder as a desired one. Would you mind adding it 
to the list?

https://apacheignite-mix.readme.io/docs/kubernetes-discovery 


—
Denis

[jira] [Created] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-4871:
-

 Summary: Web console: Implement possibility to configure 
Kubernetes IP finder
 Key: IGNITE-4871
 URL: https://issues.apache.org/jira/browse/IGNITE-4871
 Project: Ignite
  Issue Type: Task
  Components: wizards
Affects Versions: 1.8
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko






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

Re: Adding Kubernetes IP finder to Web Console IP finders list

[Vasiliy Sisko]

Created issue to add possibility to configure Kubernates IP finder. You can
track it by link: https://issues.apache.org/jira/browse/IGNITE-4871

On Tue, Mar 28, 2017 at 10:18 AM, Denis Magda  wrote:

> Alex,
>
> Presently, if to go to the Clusters configuration in Web Console it won’t
> be possible to set Kubernetes IP finder as a desired one. Would you mind
> adding it to the list?
>
> https://apacheignite-mix.readme.io/docs/kubernetes-discovery <
> https://apacheignite-mix.readme.io/docs/kubernetes-discovery>
>
> —
> Denis




-- 
Vasiliy Sisko
GridGain Systems
www.gridgain.com

Re: Continuations for services

[Valentin Kulichenko]

Vova,

Agree, I already merged IGNITE-4802.

However, I'm still interested why we always switch to another thread when
executing a job locally. Does anyone have an idea why we do this?

-Val

On Sat, Mar 25, 2017 at 7:22 AM, Vladimir Ozerov 
wrote:

> Valya,
>
> I don't think it will resolve all the cases. For example, what if I execute
> remote job from another job? "Remoteness" could be caused by job natire
> (broadcast), specific cluster group, or affinity call/run on remote key.
> Also starvation is possible not only on local node, but between nodes, and
> in this case separate pool is the only reliable solution.
>
> On Sat, Mar 25, 2017 at 1:50 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Folks,
> >
> > I tend to think that a separate pool for services is not right solution.
> >
> > We currently execute any new compute job in a separate thread, even if
> > we're already in the public pool (see code in
> > GridJobProcessor#processJobExecuteRequest). What is the reason for this?
> > When a job synchronously executes another job on the same node, can we
> just
> > execute it in the same thread? This seems to fix all starvation issues
> > discussed in this thread.
> >
> > Am I missing something?
> >
> > -Val
> >
> > On Thu, Mar 9, 2017 at 2:32 AM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > OK, I created it: https://issues.apache.org/jira/browse/IGNITE-4802
> > >
> > > -Val
> > >
> > > On Thu, Mar 9, 2017 at 9:58 AM, Vladimir Ozerov 
> > > wrote:
> > >
> > >> Valya,
> > >>
> > >> Not yet.
> > >>
> > >> On Thu, Mar 9, 2017 at 11:50 AM, Valentin Kulichenko <
> > >> valentin.kuliche...@gmail.com> wrote:
> > >>
> > >> > Vladimir,
> > >> >
> > >> > This makes sense to me. Is there a ticket for separate thread pool
> for
> > >> > services?
> > >> >
> > >> > -Val
> > >> >
> > >> > On Thu, Mar 9, 2017 at 2:52 AM, Dmitriy Setrakyan <
> > >> dsetrak...@apache.org>
> > >> > wrote:
> > >> >
> > >> > > Vladimr, it sounds like what you are suggesting is allowing users
> > >> specify
> > >> > > named executors in configuration and then use them from code,
> > right? I
> > >> > > think I like this idea very much.
> > >> > >
> > >> > > On Wed, Mar 8, 2017 at 1:46 PM, Vladimir Ozerov <
> > voze...@gridgain.com
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > > > Continuations is not very good idea. It is useful if user has
> > simple
> > >> > > logic
> > >> > > > when one job calls another from within the same execute/run/call
> > >> > method.
> > >> > > > But if you have complex logic with OOP abstractions and reusable
> > >> > > > components, nested job call can be located many stack frames
> down
> > >> from
> > >> > > > parent job. In this case continuations are unusable.
> > >> > > >
> > >> > > > More convenient approach is to map separate jobs to separate
> > thread
> > >> > > pools.
> > >> > > > This technique is successfully employed in Hazelcast. You just
> > >> define
> > >> > > > additional executors and say that job A is to be executed one
> > thread
> > >> > > pool,
> > >> > > > and job B on another.
> > >> > > >
> > >> > > > The same technique is applicable for services:
> > >> > > >
> > >> > > > class MyService implements Service {
> > >> > > > @IgniteInstanceResource
> > >> > > > Ignite ignite;
> > >> > > >
> > >> > > > void myMethod() {
> > >> > > >
> > >> > > > ignite.service().withExecutor("myExecutor").service("
> > >> > > > myService").nestedCall();
> > >> > > > }
> > >> > > > }
> > >> > > >
> > >> > > > All in all I would do the following:
> > >> > > > 1) Create separate built-in pool for services to make sure that
> in
> > >> > simple
> > >> > > > cases users are able to call compute jobs from service methods.
> > >> > > > 2) Implement custom executors which will be applicable for both
> > >> compute
> > >> > > [1]
> > >> > > > and service components.
> > >> > > >
> > >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-4699
> > >> > > >
> > >> > > > 08 марта 2017 г. 23:01 пользователь "Dmitriy Setrakyan" <
> > >> > > > dsetrak...@apache.org> написал:
> > >> > > >
> > >> > > > > On Wed, Mar 8, 2017 at 11:58 AM, Valentin Kulichenko <
> > >> > > > > valentin.kuliche...@gmail.com> wrote:
> > >> > > > >
> > >> > > > > > Separate thread pool will not solve the case of calling a
> > >> service
> > >> > > from
> > >> > > > > > another service.
> > >> > > > > >
> > >> > > > >
> > >> > > > > Why not? The caller thread should block.
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>

[GitHub] ignite pull request #1676: IGNITE-4501: Improvement of connection in a clust...

[SharplEr]

GitHub user SharplEr opened a pull request:

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

IGNITE-4501: Improvement of connection in a cluster of new node

Reopen that PR: https://github.com/apache/ignite/pull/1436

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

$ git pull https://github.com/SharplEr/ignite ignite-4501

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

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


commit 0e7768224e8ae26797460e2b750d04979c49c92f
Author: Alexander Menshikov 
Date:   2017-01-20T12:35:05Z

Add using CLUSTER_REGION_ID for ordering nodes in ring

commit c43894854a2bdcb5d39d92552f0e105c70a10198
Author: Alexander Menshikov 
Date:   2017-01-20T12:35:53Z

Add tests for RegionNodeComparator

commit 5a7d5e395c00ab7e6eafa03ed29ae4eea754cbc1
Author: Alexander Menshikov 
Date:   2017-01-20T12:44:28Z

Add test to suite

commit cdcda327773b61beb90539e7c11130906d0525dc
Author: Alexander Menshikov 
Date:   2017-01-21T10:57:54Z

A little clean up code

commit 620be443f3ef7bd4730ba755fb4e110d8dcd4918
Author: Alexander Menshikov 
Date:   2017-01-25T12:26:42Z

Change ordering inside nodes field, and add maxNode field to avoid using 
old ordering. Add method variant of serverNodes method which return only 
necessary part of ring. That make complexity of nextNode equals O(log n + k), 
which better then O(n). n is number of nodes, k is number of client nodes.

commit b45bad8b5dcf9d3904805503b1c327d4a6686d60
Author: Alexander Menshikov 
Date:   2017-01-25T13:03:27Z

Add filed to TcpDiscoveryNode for faster getting cluster_region_id

commit d9b68dd3cc4f546d73c475c7adf82ea797d851f2
Author: Alexander Menshikov 
Date:   2017-01-27T15:01:38Z

Fix bug in RegionNodeComparator

commit f36f07da21ca51bf2585fb80b82239541a3a16d6
Author: Alexander Menshikov 
Date:   2017-01-27T15:02:30Z

Cleanup code in RegionNodeComparatorTest

commit 145394cb5c10e5f1127071f1cb7957a3c1307a9d
Author: Alexander Menshikov 
Date:   2017-01-27T15:09:55Z

Add catch NumberFormatException

commit eeaf244788bd957a2b8f1e3b33d00338072edde1
Author: Alexander Menshikov 
Date:   2017-01-27T15:34:37Z

cleanup TcpDiscoveryNodesRing

commit a3431dec0103f815803af744ec3c75b7188c19fb
Author: Alexander Menshikov 
Date:   2017-01-30T10:37:16Z

Code cleanup

commit a41ee660eb275714bd924dfae7bf01c3274300f1
Author: Alexander Menshikov 
Date:   2017-01-30T11:58:26Z

Add @NotNull to RegionNodeComparator.compare

commit 8ebd887797cba7adf3ca08ea8af8ac43e29be221
Author: Alexander Menshikov 
Date:   2017-01-30T12:06:09Z

Add @Nullable to TcpDiscoveryNode.getClusterRegionId

commit fd91a18a421e951638c9f9078c34169916adde5e
Author: Alexander Menshikov 
Date:   2017-01-30T12:07:57Z

cleanup 
modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/internal/TcpDiscoveryNodesRing.java

commit f4652c888d07c1f52945c801be3e220d55895860
Author: Alexander Menshikov 
Date:   2017-01-30T16:31:44Z

Remove using cast to Nubmer

commit 6a3ac2eccd7a01bfde73def424f94d80da0c75c1
Author: Alexander Menshikov 
Date:   2017-01-30T16:37:20Z

restore code format

commit ecb82ffd908cf3de8618c8d557d4077f9341e3cc
Author: Alexander Menshikov 
Date:   2017-01-30T16:45:14Z

restore code format2

commit 2e3ec7797327d722160bdee1b0803508ce9b4058
Author: Alexander Menshikov 
Date:   2017-02-01T17:55:24Z

fix reusing variable

commit 77055549e20248c0f22eefc43e839ba82a3f3ecc
Author: Alexander Menshikov 
Date:   2017-02-01T17:57:55Z

Fix lost regionId after deserialization

commit 30d3cd992d0c4cf76b2b368c7a336863eb3b5e2d
Author: Alexander Menshikov 
Date:   2017-02-01T17:58:57Z

Add test for save sorting

commit 3e204be6d14d356d6cda6c11f2cd8d730348f44d
Author: Alexander Menshikov 
Date:   2017-02-02T11:25:24Z

Add RegionTcpDiscoverySelfTest

commit f1bdd6c936f7feae2535ab3f4dae8dddc9a4cde0
Author: Alexander Menshikov 
Date:   2017-02-02T11:31:08Z

Add license

commit 5e9343b96ecdcf25f0bdabf7468a2bd503ec7773
Author: Alexander Menshikov 
Date:   2017-02-03T11:51:37Z

Add RegionTcpDiscoverySelfTest to suite

commit 907facf0658e7e69c3b70d81bdf340b5ce62b890
Author: Alexander Menshikov 
Date:   2017-02-03T13:31:18Z

Remove maxNode

commit 

Re: IGNITE - 4760 : working in hibernate module

[Вадим Опольский]

Valentin, OK.

To enabled it in my environment I done next:
- built project with command - mvn clean package -DskipTests -Prelease,lgpl
- added folder hibernate to modules in project structure
- added library to dependencies (without it import doesn't working)

After that I have a lot of error, for instance:
- Class 'AccessStrategy' must either be declared abstract or implement
abstract method 'remove(SharedSessionContractImplementor, Object) in
'RegionAccessStrategy'

generateCacheKey
getCacheKeyId
getRegion
insert
afterInsert
update
afterUpdate
insert
afterInsert
update
get
putFromLoad
lockItem
unlockItem
remove

Do anybody know the easier way to resolve this issue?

Also tried to reimport all maven projects and cleansed repository in .m2.

Vadim Opolski

[image: Встроенное изображение 1]







2017-03-25 2:42 GMT+03:00 Valentin Kulichenko :

> Vadim,
>
> ignite-hibernate module is a part of 'lgpl' profile. Apparently it's not
> enabled in your environment.
>
> -Val
>
> On Fri, Mar 24, 2017 at 4:38 PM, Вадим Опольский 
> wrote:
>
> > Hello everybody,
> >
> > I want to resolve issue №4760
> > https://issues.apache.org/jira/browse/IGNITE-4760
> >
> > To find solution I'm going to change method threadLocalForCache and to
> add
> > Junit test.
> >
> > Why folder hibernate is not a module ? Can I added it ?
> >
> > Vadim Opolski
> >
>