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 <
va
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
Is
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 utili
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.
com/Code-Review-T
+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 will go on for 5 da
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,
>
> Makes sense to me.
> 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
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
> wrote:
>
> > Following the discussion on Upso
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:
> http://apache-ignite-developers.2346864.n
Ksenia Rybakova created IGNITE-4232:
---
Summary: "IllegalArgumentException: Cache is not configured:
ignite-marshaller-sys-cache" while starting grid
Key: IGNITE-4232
URL: https://issues.apache.org/jira/browse/IGN
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 contribu
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 ena
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 for now.
> Thank you for yo
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 contribution!
>
> On Wed, Nov 16,
+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 small/trivial, creating a r
+1
Way to go!
On Wed, Nov 16, 2016 at 2:19 PM, Andrey Gura wrote:
> +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 contr
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: Sub-task
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:
https://issues.apache.org/jira/browse/IGNITE-4
+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 described in wiki.
>
> It
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 shout add section for R
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 :)
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 Ty
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 ignite
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
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: Impr
> 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 doesn't. Load cache should ei
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
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, provides a way to avoid
> it.
>
> > >
>
> > >
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
Alt
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 ena
+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
> wrote:
>
> > Sergi,
> >
> > I don't think we
+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)
>
> This vote will go
+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 official code review
> > tool.
> >
> > [ ]
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
+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:
> > >
> > > Following the discussion on Upsource [1],
> > > I
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 this
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 Novikov
wrote:
> Dmitriy,
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
Repor
Denis,
Any plans to add 1.8.0 in readme.io for new features?
-Roman
On Wednesday, November 16, 2016 6:08 AM, Denis Magda
wrote:
Igor,
It makes sense to wait for me while everything gets merged into 1.8 then.
Please let me know over this discussion when the overall merge happens.
—
Deni
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
GitHub user dmagda opened a pull request:
https://github.com/apache/ignite/pull/1241
Added geospatial example
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-4238
Alternatively you can review and apply these
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. Y
Taras Ledkov created IGNITE-4239:
Summary: Public thread pool starvation is cause of deadlock when
user's jobs calls cache.size()
Key: IGNITE-4239
URL: https://issues.apache.org/jira/browse/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 apply
44 matches
Mail list logo
