On further look, this looks interesting and I am happy to dive into the
spring framework.
Please help me in getting started
On Mon, 29 Mar 2021, 11:49 Atri Sharma, wrote:
> Thanks Sam and Ivan.
>
> I am happy to look into that but it looks like most of the work is done
> there?
>
> Also, is
But what if I need to have exactly one callback synchronous, and all other can
be asynchronous?
I would separate two cases: an existing user who wants their old behavior back,
and a new user that wants to fine tune their app.
The existing user needs a global "make it all synchronous" switch.
Stan,
Unfortunately, annotations have a few drawbacks:
* Can't configure it globally ("I already use sync callbacks, give me back
the old behavior in one line")
* Can't configure in Spring
* Useless in C++ & .NET
* You can already specify executor in IgniteFuture#listenAsync, so there
seems to be
Thought about this some more.
I agree that we need to be able to switch to synchronous listeners when it's
critical for performance.
However, I don't like to introduce an Executor property for that. In fact, the
only value
we really expect the user to set in that property is Runnable::run -
Maksim Timonin created IGNITE-14440:
---
Summary: Run external tests in ducktape
Key: IGNITE-14440
URL: https://issues.apache.org/jira/browse/IGNITE-14440
Project: Ignite
Issue Type: New
Pavel Vinokurov created IGNITE-14439:
Summary: NPE when accessing clustername before first exchange
finished
Key: IGNITE-14439
URL: https://issues.apache.org/jira/browse/IGNITE-14439
Project:
Hello!
I have left some more comments after trying this change on a real Azure
cluster.
Regards,
--
Ilya Kasnacheev
вт, 23 мар. 2021 г. в 18:32, Atri Sharma :
> Thank you!
>
> I have updated the PR. Please see and let me know.
>
> On Tue, Mar 23, 2021 at 4:27 PM Ilya Kasnacheev
> wrote:
> >
Kirill Gusakov created IGNITE-14438:
---
Summary: Add README.md files to cli and cli-common modules
Key: IGNITE-14438
URL: https://issues.apache.org/jira/browse/IGNITE-14438
Project: Ignite
Hello,
Please pass all known server node addresses to
ClientConfiguration.setAddresses.
E.g. if everything is on one machine, for 3 servers it'll be
setAddresses("127.0.0.1:10800", "127.0.0.1:10801", "127.0.0.1:10802")
On Mon, Mar 29, 2021 at 3:23 PM Максим Плотников
wrote:
> Hello!
>
>
>
>
Vladimir Steshin created IGNITE-14437:
-
Summary: Adjust test params: exclude input net failures with
disabled connRecovery
Key: IGNITE-14437
URL: https://issues.apache.org/jira/browse/IGNITE-14437
Stan,
I'm ok with using public pool by default, but we need a way to restore the
old behavior, do you agree?
I think we should keep the new IgniteConfiguration property.
On Fri, Mar 26, 2021 at 2:12 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> Pavel,
>
> Dedicated pool looks
Thibaud Faurie created IGNITE-14436:
---
Summary: Scala documentation
Key: IGNITE-14436
URL: https://issues.apache.org/jira/browse/IGNITE-14436
Project: Ignite
Issue Type: Bug
Nikolay Izhikov created IGNITE-14435:
Summary: Refactor PdsConsistentIdProcessor for reusage
Key: IGNITE-14435
URL: https://issues.apache.org/jira/browse/IGNITE-14435
Project: Ignite
Thanks Sam and Ivan.
I am happy to look into that but it looks like most of the work is done
there?
Also, is there something in core that I can pickup as well?
On Mon, 29 Mar 2021, 03:20 Ivan Pavlukhin, wrote:
> Gmail treated last message as spam. Bumping.
>
> 2021-03-28 16:05 GMT+03:00,
Val,
There were enough hype around Reactive programming past years. I
remind a lot of talks about RxJava. And I suppose it worth to consider
it. But it requires some time to study modern trends to make a choice.
So far I am not ready to facilitate Reactive API for Ignite 3.
Regarding
15 matches
Mail list logo
