Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Maxim, Could you merge master to your PR? I failed to review Web Console files due to conflicts. Thanks. On Fri, Mar 10, 2017 at 3:06 PM, Kozlov Maxim wrote: > Andrey, Alexey, please review > PR - https://github.com/apache/ignite/pull/1521 < >

Incorrect link on LinkedIn page

Igniters, The LinkedIn page for Ignite[1] still points to the incubator link[2]. Can someone (whoever owns the account) please fix it? [1] https://www.linkedin.com/company/apache-ignite [2] http://ignite.incubator.apache.org/ -Prachi

Presenting Apache Ignite SQL Grid at Big Data Bootcamp

Igniters, If you live not to far from Santa Clara, CA, USA then I’ll encourage you attending my presentation at Big Data Bootcamp on March 28. https://blogs.apache.org/ignite/entry/presenting-apache-ignite-sql-grid Let’s

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

Hi Val, I will work on it in my spare time.. Take Care, Rishi > On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko > wrote: > > Hi Rishi, > > Can you please assign the ticket to yourself and create a pull request as > described in [1]? > > Let's follow the

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Well, looks like only committers can edit the pages. Could you prepare the content and paste it here? I’ll update the migration guide for you. — Denis > On Mar 13, 2017, at 9:59 AM, Kozlov Maxim wrote: > > No, I can not edit other pages. > > Screenshots menu: >

Re: About thread problem of service execution in Ignite Service Grid

Why would you use a thread local in a service? What design you think is reasonable? -Val On Mon, Mar 13, 2017 at 2:03 PM, 李玉珏@163 <18624049...@163.com> wrote: > Hi， > > When in service grid service execution, if the local node deployment > services, will directly call the local deployment

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

No, I can not edit other pages. Screenshots menu: https://www.dropbox.com/s/hbhuk3tci7k77qr/%D0%A1%D0%BA%D1%80%D0%B8%D0%BD%D1%88%D0%BE%D1%82%202017-03-13%2019.51.30.png?dl=0 https://www.dropbox.com/s/43nr384icfb6xwp/%D0%A1%D0%BA%D1%80%D0%B8%D0%BD%D1%88%D0%BE%D1%82%202017-03-13%2019.50.24.png?dl=0

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Weird, can you edit any other page? I can’t find any configuration parameters that should prevent you from editing. — Denis > On Mar 13, 2017, at 9:14 AM, Kozlov Maxim wrote: > > Denis, I can not edit this page. > > confluence username: dreamx > >> 13 марта 2017 г., в

Re: More SEO and API doc cleanup

> 2. Add the following tag to all .html files: > href="https://ignite.apache.org/releases/latest/LANGUAGE-DIR/FILENAME.html > " /> > > Bear in mind to change the url accordingly. For example, for java index > version would

Re: distributed transaction of non-single coordinator

It sounds a little scary to me that we are passing transaction objects around. Such object may contain all sorts of Ignite context. If some data needs to be passed across, we should create a special transfer object in this case. D. On Mon, Mar 13, 2017 at 9:10 AM, ALEKSEY KUZNETSOV

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Denis, I can not edit this page. confluence username: dreamx > 13 марта 2017 г., в 19:01, Kozlov Maxim написал(а): > > Denis, > > ok > >> 13 марта 2017 г., в 18:59, Denis Magda > > написал(а): >> >> Maxim, >> >> Please

Re: distributed transaction of non-single coordinator

well, there a couple of issues preventing transaction proceeding. At first, After transaction serialization and deserialization on the remote server, there is no txState. So im going to put it in writeExternal()\readExternal() The last one is Deserialized transaction lacks of shared cache context

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Denis, ok > 13 марта 2017 г., в 18:59, Denis Magda написал(а): > > Maxim, > > Please update Apache Ignite 2.0 migration guide: > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide > >

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Maxim, Please update Apache Ignite 2.0 migration guide: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide You need to say that the parameter has been discontinued and the

Re: IgniteConfiguration.gridName is very confusing

Alexander, May I ask you to update Apache Ignite 2.0 migration guide? https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide There you need to say that

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

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 wrote: > Hi

Re: More SEO and API doc cleanup

Hi Denis, Thanks for taking care of the marge! About the latest doc reference, when a new version is released it would be necessary to do 2 things:1. Update the new version number on the .htaccess file: RewriteRule ^releases/latest/(.*)$ /releases/1.9.0/$1 [L]2. Add the following tag to all .html

Re: starting grids in tests

startGrids() method starts nodes sequentially, whille startGridsMultiThread() does it in parallel. Moreover, startGridsMultiThreaded() waits for finishing of partition map exchange. On Mon, Mar 13, 2017 at 4:43 PM, ALEKSEY KUZNETSOV wrote: > Hi All! > When would you

Re: Suggestion for remove ComputeJobContinuationAdapter

This class can't be removed as it's part of public API. It's a convenience adapter that users can extend when using continuations. -Val On Mon, Mar 13, 2017 at 3:28 PM, Александр Меньшиков wrote: > The abstract class "ComputeJobContinuationAdapter" is unused. There aren't

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Thanks! пн, 13 мар. 2017 г. в 17:24, Alexey Goncharuk : > Aleksey, > > Thanks, I merged your changes to master. Please resolve the ticket. > > 2017-03-13 12:33 GMT+03:00 ALEKSEY KUZNETSOV : > > > I've fixed all your remarks. Plz, review them

Suggestion for remove ComputeJobContinuationAdapter

The abstract class "ComputeJobContinuationAdapter" is unused. There aren't any subclass. Looks we can remove it now.

Re: distributed transaction of non-single coordinator

while starting and continuing transaction in different jvms in run into serialization exception in writeExternalMeta : @Override public void writeExternal(ObjectOutput out) throws IOException { writeExternalMeta(out); some meta is cannot be serialized. пт, 10 мар. 2017 г. в 17:25, Alexey

[GitHub] ignite pull request #1517: IGNITE-1178 fix for NPE in GridCacheProcessor.onK...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1517 --- 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

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Aleksey, Thanks, I merged your changes to master. Please resolve the ticket. 2017-03-13 12:33 GMT+03:00 ALEKSEY KUZNETSOV : > I've fixed all your remarks. Plz, review them > > пн, 13 мар. 2017 г. в 11:17, Alexey Goncharuk >: > > > My

starting grids in tests

Hi All! When would you call startGridsMultiThreaded instead of startGrids. I wonder why would one start grids multithreaded ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

I've fixed all your remarks. Plz, review them пн, 13 мар. 2017 г. в 11:17, Alexey Goncharuk : > My apologies, the comments were not committed to GitHub. They are there > now. > > 2017-03-13 11:13 GMT+03:00 ALEKSEY KUZNETSOV : > > > Hi! This

About thread problem of service execution in Ignite Service Grid

Hi， When in service grid service execution, if the local node deployment services, will directly call the local deployment service, otherwise it will find the service in the grid. The local service, and the caller will use the same thread, in this case, the two threads‘s state is different,

[GitHub] ignite pull request #1614: IGNITE-3682

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1614 IGNITE-3682 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

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

I took a look at .NET and C++ parts. Looks good to me. Best Regards, Igor On Mon, Mar 13, 2017 at 2:35 PM, Alexey Kuznetsov wrote: > I will also take a look for Web Console changes tomorrow. > > On Fri, Mar 10, 2017 at 5:00 PM, Andrey Gura wrote: > >

Re: IgniteConfiguration.gridName is very confusing

Thank you Alexander, I merged these changes. I recommend everybody get latest chages from ignite-2.0. Thanks! On Mon, Mar 13, 2017 at 1:23 PM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > PR updated > > On Mon, Mar 13, 2017 at 1:05 PM, Alexander Fedotov < >

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

I will also take a look for Web Console changes tomorrow. On Fri, Mar 10, 2017 at 5:00 PM, Andrey Gura wrote: > Maxim, > > I'll take a look today. > > 10 марта 2017 г. 11:06 AM пользователь "Kozlov Maxim" < > dreamx@gmail.com> > написал: > > > Andrey, Alexey, please

Re: IgniteConfiguration.gridName is very confusing

PR updated On Mon, Mar 13, 2017 at 1:05 PM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > Okay. Will do it shortly. > > On Mon, Mar 13, 2017 at 1:03 PM, Semyon Boikov > wrote: > >> Alexander, >> >> I see there are conflicts again, could you plase resolve them,

Re: IgniteConfiguration.gridName is very confusing

Alexander, I see there are conflicts again, could you plase resolve them, I'm going to review and merge these changes today. Thanks! On Fri, Mar 10, 2017 at 5:50 PM, Yakov Zhdanov wrote: > Thanks, Alex! > > Sam, can you please also take a look to make sure we catch all

[GitHub] ignite pull request #1612: IGNITE-4814

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1612 --- 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

[GitHub] ignite pull request #1609: Ignite 2.0 merge

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1609 --- 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

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

My apologies, the comments were not committed to GitHub. They are there now. 2017-03-13 11:13 GMT+03:00 ALEKSEY KUZNETSOV : > Hi! This is my PR link : https://github.com/apache/ignite/pull/1517. You > must have mixed it up, for there is *no* comments to address. > > пт,

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Hi! This is my PR link : https://github.com/apache/ignite/pull/1517. You must have mixed it up, for there is *no* comments to address. пт, 10 мар. 2017 г. в 20:10, Alexey Goncharuk : > Yes, but I have added a few more today :) > > 2017-03-10 19:03 GMT+03:00 ALEKSEY

[jira] [Created] (IGNITE-4816) Issue with refresh rate on queries

Pavel Konstantinov created IGNITE-4816: -- Summary: Issue with refresh rate on queries Key: IGNITE-4816 URL: https://issues.apache.org/jira/browse/IGNITE-4816 Project: Ignite Issue Type:

[GitHub] ignite pull request #1545: IGNITE-2552 EvictionPolicies refactored, logic ch...

Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/1545 --- 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

Re: IGNITE-13 (ready for review)

Hi Valentin, OK, thank you. 2017-03-11 20:33 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Hi Vadim, > > According to these results, I don't think it makes sense to make this > change in the product. I closed the ticket. > > -Val > > On Fri, Mar 10, 2017 at 12:28 PM, Вадим