[jira] [Created] (IGNITE-13380) Output IgniteSystemProperties via ignite.sh

Amelchev Nikita created IGNITE-13380: Summary: Output IgniteSystemProperties via ignite.sh Key: IGNITE-13380 URL: https://issues.apache.org/jira/browse/IGNITE-13380 Project: Ignite Issue

Re: [DISCUSSION] Output IgniteSystemProperties via ignite.sh

I think this is a helpful feature. I have created the issue: https://issues.apache.org/jira/browse/IGNITE-13380

Re: IEP-51: Java Thin Client Async API

I've changed the IEP and added a new future interface to the POC: interface IgniteClientFuture extends Future, CompletionStage The implementation simply wraps the CompletableFuture. On Fri, Aug 21, 2020 at 11:22 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Pavel, > > Inter

Re: Editing rights

Hi, my cwiki account is evzabotkin, e-mail evzabot...@sberbank.ru. On 2020/08/19 18:20:41, Denis Magda wrote: > Yes, I confused JIRA with wiki in the last response. Ivan, thanks for > catching that. > > - > Denis > > > On Wed, Aug 19, 2020 at 11:08 AM Ivan Pavlukhin wrote: > > > > We'd like

[jira] [Created] (IGNITE-13381) ClusterGroupEmptyException: Cluster group is empty error after client reconnect

Andrey Aleksandrov created IGNITE-13381: --- Summary: ClusterGroupEmptyException: Cluster group is empty error after client reconnect Key: IGNITE-13381 URL: https://issues.apache.org/jira/browse/IGNITE-13381

Re: Stuck in solving class not found exception

Hi Team, Awaiting your reply, can you please have a look. Thanks, Belal khan On Wednesday, August 19, 2020, Belal Ahmed Khan wrote: > Hi Team, > > I am getting an exception when my client tries to connect to the cluster, > i have copied my application jar in the libs folder of the cluster stil

Re: Editing rights

Evgeniy, You're in. Go ahead and do the necessary edits on the page. - Denis On Mon, Aug 24, 2020 at 3:36 AM lonsdalel lonsdalel < eugenezabot...@gmail.com> wrote: > Hi, > my cwiki account is evzabotkin, e-mail evzabot...@sberbank.ru. > > On 2020/08/19 18:20:41, Denis Magda wrote: > > Yes, I

[jira] [Created] (IGNITE-13382) DurableBackgroundTask can abandon incomplete task

Maria Makedonskaya created IGNITE-13382: --- Summary: DurableBackgroundTask can abandon incomplete task Key: IGNITE-13382 URL: https://issues.apache.org/jira/browse/IGNITE-13382 Project: Ignite

Any reason to keep ClientConfiguration final?

@Pavel Tupitsyn , @Igor Sapego , Michael has been integrating Ignite with Micronaut and we hit some limitations related to the configuration. To simplify the configuration of the thin client instances, we need to inherit from the ClientConfiguration class

Re: Any reason to keep ClientConfiguration final?

Denis, No objections to the removal of the "final" modifier from my side. However, the use case sounds a bit weird to me, can you please describe it in more detail? Thanks, Pavel On Mon, Aug 24, 2020 at 10:47 PM Denis Magda wrote: > @Pavel Tupitsyn , @Igor Sapego , > > Michael has been integra

Re: Any reason to keep ClientConfiguration final?

No objections from my side. What is the case? Some kind of new thin client? Best Regards, Igor On Mon, Aug 24, 2020 at 11:40 PM Pavel Tupitsyn wrote: > Denis, > > No objections to the removal of the "final" modifier from my side. > However, the use case sounds a bit weird to me, can you pleas

Re: Ignite thin client in Rust

Hi, Val, I've been working on my implementation for some time, but didn't commit to it lately so it's pretty much abandoned. Maybe we should join our forces here :) Best Regards, Igor On Thu, Jul 2, 2020 at 1:00 AM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Pavel, > > Yes, I

Re: Cpp thin client transactions support ready for review.

Great, I'll take a look. Best Regards, Igor On Mon, Aug 24, 2020 at 8:33 AM Zhenya Stanilovsky wrote: > > > Thanks Ivan Daschinsky for review, does anyone more who could check it ? > > thanks ! > >Igniters, seems i complete with transactions in thin cpp client > >implementation [1], part of ie

Re: [DISCUSSION] Consistency across java thin/thick APIs

Yes, it was an attempt to separate thick and thin clients as much as possible to move them in separate libs in future. Alex, what do you think? What is the right path here from the Java developer viewpoint? Best Regards, Igor On Mon, Aug 24, 2020 at 9:40 AM Alex Plehanov wrote: > Hi Val, > >

Re: Micronaut/Ignite

Michael, Great progress, thanks for your patience. I went ahead and pushed some changes to your working branch. As you'll see, those changes do some minor tweaks in the DefaultIgniteThinClientConfiguration class and add Static with Kubernetes IP finders to the DefaultIgniteConfiguration class. The

First contribute to Ignite ML

Hello, I want to join the Ignite community as a developer. My field of interests is Machine learning, so I can start with extending DistanceMeasure implementations (migrate from scipy). Please, could you give me a contribution permission (username: mrkandreev)? -- Best regards, Mark Andreev

Re: First contribute to Ignite ML

Hi Mark, Welcome to the community! Hope you'll find it delightful to contribute to the Ignite ML component. I've added you to JIRA's contributors' list, so you're good to go. Just in case, @Alexey Zinoviev is our main ML maintainer, but, probably, you already know him. - Denis On Mon, Aug 24

Re: IEP-51: Java Thin Client Async API

Alexey, what do you think? Which Future should be used here? Now, about the "not fully sync" interface - I believe this is acceptable as a first approach. Best Regards, Igor On Mon, Aug 24, 2020 at 12:37 PM Pavel Tupitsyn wrote: > I've changed the IEP and added a new future interface to the P

Re: Micronaut/Ignite

Michael, I was thinking over the idea of splitting the ignite-cache module in two (one for a thick-client based connection and the other for thin client connections), and would try to avoid this route if possible. With the @CacheConfig annotation, Micronaut developers can create a generic impleme

Re: Micronaut/Ignite

yea, I'm not sure about ignite-cache config. splitting it into two modules seems kind of overly complicated, but I also don't really like the random boolean flag. here is the tweaks from the config your provider: https://github.com/pollend/micronaut-ignite/pull/2 kind of strange that there are not

Re: Any reason to keep ClientConfiguration final?

micronaut setups the configuration at compile time. so a lot of the configuration is through annotating classes. There are two main methods for this ConfigurationProperties/ConfigurationBuilder. ConfigurationBuilder maps properties to a factor and ConfigurationProperties maps properties onto a clas