[GitHub] ignite pull request #1242: Ignite 4239

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1242 Ignite 4239 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4239 Alternatively you can review and

Geospatial queries example fails in master

Igniters, I’ve just added the documentation about our geospatial queries [1] and wanted to contribute an example [2]. However, the example no longer works in the master branch producing the error you can see in the ticket [2]. The same example works perfectly fine in version 1.7 and earliest.

Re: Apache Ignite 1.8 Release

Roman, That versions will be created after 1.8 gets released. Recently there was a discussion on the dev list [1] regarding the difficulties related to documentation maintenance when several documentation versions co-exist at the same time. It was decided that rather then create a new version

[jira] [Created] (IGNITE-4238) Example for spatial queries

Denis Magda created IGNITE-4238: --- Summary: Example for spatial queries Key: IGNITE-4238 URL: https://issues.apache.org/jira/browse/IGNITE-4238 Project: Ignite Issue Type: Task

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

Andrey, thank you! Dmitriy, I will when we have 1.8.0 version on readme.io. -Roman On Wednesday, November 16, 2016 8:38 PM, Dmitriy Setrakyan wrote: Roman, do you mind contributing the documentation for this feature? On Wed, Nov 16, 2016 at 12:27 PM, Andrey

Re: IgniteCache.loadCache improvement proposal

Alexandr, 'local' prefix in Ignite APIs means that the method is invoked only on the current node, while its regular sibling is invoked in distributed fashion. localLoadCache doesn't imply that only local partitions are loaded. it turns out to work this way right now, but it doesn't mean that

Re: [VOTE] Use Upsource for Code Review

+1 On Wed, Nov 16, 2016 at 8:50 PM, Vladisav Jelisavcic wrote: > +1 (non-binding) > > On Wed, Nov 16, 2016 at 6:15 PM, Denis Magda wrote: > > > +1 > > > > — > > Denis > > > > > On Nov 16, 2016, at 2:08 AM, Pavel Tupitsyn > > wrote:

[GitHub] ignite pull request #1240: ignite-3958

GitHub user ntikhonov opened a pull request: https://github.com/apache/ignite/pull/1240 ignite-3958 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3958 Alternatively you can review and apply these

Re: [VOTE] Use Upsource for Code Review

+1 (non-binding) On Wed, Nov 16, 2016 at 6:15 PM, Denis Magda wrote: > +1 > > — > Denis > > > On Nov 16, 2016, at 2:08 AM, Pavel Tupitsyn > wrote: > > > > Following the discussion on Upsource [1], > > I would like to call a vote on accepting it as our

Re: [VOTE] Use Upsource for Code Review

+1 — Denis > On Nov 16, 2016, at 2:08 AM, Pavel Tupitsyn wrote: > > Following the discussion on Upsource [1], > I would like to call a vote on accepting it as our official code review > tool. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why)

Re: [VOTE] Use Upsource for Code Review

+1 Ok, this makes sense. Sergi 2016-11-16 14:33 GMT+03:00 Dmitriy Setrakyan : > +1 > > I think we should allow this tool, unless it proves counter productive. If > it does, then we will drop it. > > On Wed, Nov 16, 2016 at 11:44 AM, Pavel Tupitsyn

[GitHub] ignite pull request #1239: IGNITE-4234 .NET: Propagate missing CacheMetrics ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1239 --- 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 #1239: IGNITE-4234 .NET: Propagate missing CacheMetrics ...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1239 IGNITE-4234 .NET: Propagate missing CacheMetrics properties You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-4234

Re: IgniteCache.loadCache improvement proposal

On Wed, Nov 16, 2016 at 1:54 PM, Yakov Zhdanov wrote: > > On Wed, Nov 16, 2016 at 11:22 AM, Yakov Zhdanov > wrote: > > > > > Yakov, I agree that such scenario should be avoided. I also think > that > > > > > loadCache(...) method, as it is right now,

[jira] [Created] (IGNITE-4237) Implement interface to local Ignite instance over IPC

Vladimir Ozerov created IGNITE-4237: --- Summary: Implement interface to local Ignite instance over IPC Key: IGNITE-4237 URL: https://issues.apache.org/jira/browse/IGNITE-4237 Project: Ignite

Re: IgniteCache.loadCache improvement proposal

> On Wed, Nov 16, 2016 at 11:22 AM, Yakov Zhdanov wrote: > > > Yakov, I agree that such scenario should be avoided. I also think that > > > loadCache(...) method, as it is right now, provides a way to avoid it. > > > > No, it does not. > > > Yes it does :) No it

[jira] [Created] (IGNITE-4236) .NET: ICache.LocalMetrics and overloads

Pavel Tupitsyn created IGNITE-4236: -- Summary: .NET: ICache.LocalMetrics and overloads Key: IGNITE-4236 URL: https://issues.apache.org/jira/browse/IGNITE-4236 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4235) Can't get user exception if was on remote service

Dmitriy Govorukhin created IGNITE-4235: -- Summary: Can't get user exception if was on remote service Key: IGNITE-4235 URL: https://issues.apache.org/jira/browse/IGNITE-4235 Project: Ignite

[GitHub] ignite pull request #1238: Ignite 4231 Fix hangs on compute result serializa...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1238 Ignite 4231 Fix hangs on compute result serialization error You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-4234) .NET: Propagate missing CacheMetrics properties

Pavel Tupitsyn created IGNITE-4234: -- Summary: .NET: Propagate missing CacheMetrics properties Key: IGNITE-4234 URL: https://issues.apache.org/jira/browse/IGNITE-4234 Project: Ignite Issue

Re: IgniteCache.loadCache improvement proposal

On Wed, Nov 16, 2016 at 11:22 AM, Yakov Zhdanov wrote: > > Yakov, I agree that such scenario should be avoided. I also think that > > loadCache(...) method, as it is right now, provides a way to avoid it. > > No, it does not. > Yes it does :)

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

Roman, do you mind contributing the documentation for this feature? On Wed, Nov 16, 2016 at 12:27 PM, Andrey Novikov wrote: > Dmitriy, > > At this moment supported command can be found in ticket description: > https://issues.apache.org/jira/browse/IGNITE-3066 > I think we

Re: [VOTE] Use Upsource for Code Review

+1 I think we should allow this tool, unless it proves counter productive. If it does, then we will drop it. On Wed, Nov 16, 2016 at 11:44 AM, Pavel Tupitsyn wrote: > Sergi, > > I don't think we should enforce it. > "Official" means that it will be allowed, linked and

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

Dmitriy, At this moment supported command can be found in ticket description: https://issues.apache.org/jira/browse/IGNITE-3066 I think we shout add section for REDIS support on apacheignite.readme.io like for memcache Create ticket for documentation:

[jira] [Created] (IGNITE-4233) Add documentation for REDIS support

Andrey Novikov created IGNITE-4233: -- Summary: Add documentation for REDIS support Key: IGNITE-4233 URL: https://issues.apache.org/jira/browse/IGNITE-4233 Project: Ignite Issue Type:

Re: [VOTE] Use Upsource for Code Review

+1 On Wed, Nov 16, 2016 at 1:44 PM, Pavel Tupitsyn wrote: > Sergi, > > I don't think we should enforce it. > "Official" means that it will be allowed, linked and described in wiki. > > It is up to contributor and reviewer to use it. > For example, if the changes are

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

Roman, thanks for the contribution! Is there a documentation where I can read about the supported Redis commands? On Wed, Nov 16, 2016 at 12:09 PM, Andrey Novikov wrote: > Roman, > > I reviewed your PR. Changed it a little and merged to master. > Thanks for your

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

Roman, I reviewed your PR. Changed it a little and merged to master. Thanks for your contribution! On Wed, Nov 16, 2016 at 9:39 AM, Roman Shtykh wrote: > Andrey, > Sure, but I couldn't sign up -- "Cannot complete request due to license > limitations."Let's use github

[GitHub] ignite pull request #1212: IGNITE-3066: Set of Redis commands that can be ea...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1212 --- 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: [VOTE] Use Upsource for Code Review

Sergi, I don't think we should enforce it. "Official" means that it will be allowed, linked and described in wiki. It is up to contributor and reviewer to use it. For example, if the changes are small/trivial, creating a review in Upsource is not necessary. If the changes are complex and

[jira] [Created] (IGNITE-4232) "IllegalArgumentException: Cache is not configured: ignite-marshaller-sys-cache" while starting grid

Ksenia Rybakova created IGNITE-4232: --- Summary: "IllegalArgumentException: Cache is not configured: ignite-marshaller-sys-cache" while starting grid Key: IGNITE-4232 URL:

Re: [VOTE] Use Upsource for Code Review

Pavel, I'm not sure I understand the term "official code review tool", can you please elaborate it? We will enforce everyone to register in Upsource and use it or what? Sergi 2016-11-16 13:22 GMT+03:00 Pavel Tupitsyn : > Proper link to the discussion: >

Re: [VOTE] Use Upsource for Code Review

Proper link to the discussion: http://apache-ignite-developers.2346864.n4.nabble.com/ Code-Review-Tool-Proposal-Upsource-td12195.html On Wed, Nov 16, 2016 at 1:16 PM, Anton Vinogradov wrote: > +1 > > On Wed, Nov 16, 2016 at 1:08 PM, Pavel Tupitsyn >

Re: IgniteCache.loadCache improvement proposal

> Yakov, I agree that such scenario should be avoided. I also think that > loadCache(...) method, as it is right now, provides a way to avoid it. No, it does not. --Yakov

Re: Code Review Tool Proposal: Upsource

I've started the vote. Meanwhile, we have reached the user limit in the evaluation version. Some people report that they can't register; we will request proper open-source license as soon as the vote succeeds. On Wed, Nov 16, 2016 at 12:18 AM, Denis Magda wrote: > Pavel, > >

Re: [VOTE] Use Upsource for Code Review

+1 On Wed, Nov 16, 2016 at 1:08 PM, Pavel Tupitsyn wrote: > Following the discussion on Upsource [1], > I would like to call a vote on accepting it as our official code review > tool. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > This

[VOTE] Use Upsource for Code Review

Following the discussion on Upsource [1], I would like to call a vote on accepting it as our official code review tool. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) This vote will go on for 5 days. [1] http://apache-ignite-developers.2346864.n4.nabble.

Re: IgniteCache.loadCache improvement proposal

Hi all, Denis, thank you for the explanation, your understanding of the question is the most closest to mine. The extension of the method IgniteCache.loadCache by adding an IgniteClosure is a handy feature which may be useful in some cases, but not addresses the problem of extensive network

[jira] [Created] (IGNITE-4231) Hangs on compute result serialization error

Dmitry Karachentsev created IGNITE-4231: --- Summary: Hangs on compute result serialization error Key: IGNITE-4231 URL: https://issues.apache.org/jira/browse/IGNITE-4231 Project: Ignite

Re: Service proxy API changes

Valentin, I understand your point and it makes sense to me. To summarize discussion I'll do the following. Leave timeout, use LT for spammed stack traces and file separate ticket for serialization issue in calculations as suggested Semyon. On Wed, Nov 16, 2016 at 1:11 AM, Valentin Kulichenko <