[jira] [Created] (IGNITE-14327) Flaky IgniteCacheNearRestartRollbackSelfTest.

Stanilovsky Evgeny created IGNITE-14327: --- Summary: Flaky IgniteCacheNearRestartRollbackSelfTest. Key: IGNITE-14327 URL: https://issues.apache.org/jira/browse/IGNITE-14327 Project: Ignite

Re: [DISCUSSION] IEP-69 The evolutionary release process

Hi Maxim, Thanks for summarizing. +1 for the versioning scheme. -Val On Tue, Mar 16, 2021 at 11:05 AM Maxim Muzafarov wrote: > Folks, > > > Thanks to everyone for participating in the call. Here is the list of > points we've agreed on and the list of actions which should be > discussed in

Re: IEP-70: Async Continuation Executor

Pavel, So what you are saying is submitting a continuation to .NET Thread Pool already respects current SynchronizationContext and ConfigureAwait. In this case the IEP looks complete (for some reason I thought that we should take care about the SynchronizationContext inside the Ignite.NET

Re: IEP-70: Async Continuation Executor

Raymond, > If it is present in memory, then a Sync operation will > be more performant. Is it possible to do a two step operation like this > 'Cache.GetIfInMemory() ?? await Cache.GetAsync()' Ignite already does that - if the key is present locally (primary, backup, near cache, platform cache),

Re: IEP-70: Async Continuation Executor

Alexey, I'm not sure your understanding is entirely correct. The proposal won't break or change anything for UI apps and other apps with SynchronizationContext. The code in Button1_Click works now and will work after the proposal: continuations are routed to SynchronizationContext automatically

Re: IEP-70: Async Continuation Executor

Raymond, The article you referenced is great! It seems to me the article rather proved what I suggested: an async operation implementation: - Uses the async operation thread (Ignite's thread) if ConfigureAwait is false (by default

Re: [DISCUSSION] Documentation feedback button

Nikita, thanks for starting the conversation. I'll just cast my vote for the bugyard.io for its ability to select and comment on a specific problematic point on a documentation page (a paragraph, sentence, picture, code snippet, etc.). It makes it trivial to share feedback and then it's easy to

Access to Ignite Confluence

Hi everyone, Could you please grant me the necessary rights to comment on the confluence articles? My full name: Nikita Safonov Email: vlasovpavel2...@gmail.com Thank you! Regards, Nikita

[DISCUSSION] Documentation feedback button

Hello Igniters, I would like to propose an enhancement that can significantly improve the quality of our documentation. I suggest adding a feedback button (let’s call it a «Documentation feedback» button) to the web site documentation pages so everyone could leave a comment to what is already

Re: IEP-54: Schema-first approach for 3.0

Pavel, good point. Thanks. I've added async methods. On Fri, Mar 12, 2021 at 2:29 PM Pavel Tupitsyn wrote: > Andrey, > > What about corresponding async APIs, do we add them now or later? > > On Thu, Mar 11, 2021 at 8:11 PM Andrey Mashenkov < > andrey.mashen...@gmail.com> > wrote: > > > Hi

Re: IEP-70: Async Continuation Executor

There is a (long) discussion here ( https://devblogs.microsoft.com/dotnet/configureawait-faq/) regarding use of ConfigureAwait(). Putting edge cases aside, there is a general use case for .ConfigureAwait(true) in application UI contexts to ensure the continuation joins a UI thread (for example),

[jira] [Created] (IGNITE-14326) Add CacheEntry#setTtl method

Stephen Darlington created IGNITE-14326: --- Summary: Add CacheEntry#setTtl method Key: IGNITE-14326 URL: https://issues.apache.org/jira/browse/IGNITE-14326 Project: Ignite Issue Type:

Re: [DISCUSSION] IEP-69 The evolutionary release process

Folks, Thanks to everyone for participating in the call. Here is the list of points we've agreed on and the list of actions which should be discussed in more details. = AGREED = == Versioning == grand.major.bugfix[-rc_number] The 'grand' version is fixed while both Ignite architectures

Re: IEP-70: Async Continuation Executor

Pavel, My understanding might be wrong but I think the best practice (or even strongly recommended way) to implement async methods in .NET is to execute continuation on the caller's thread if ConfigureAwait(false) was not specified. Pseudo-code might look like: async Task PutAsync(K k, V v) {

Re: IEP-70: Async Continuation Executor

Pavel, I like the proposal, +1 from me Best Regards, Igor On Tue, Mar 16, 2021 at 6:49 PM Pavel Tupitsyn wrote: > Alexey, > > .NET thick API delegates to Java directly. > > When you do ICache.PutAsync(): > * Future is created on Java side, .listen() is called > * TaskCompletionSource is

[jira] [Created] (IGNITE-14325) SQL COPY command: when conversion fails, the error does not contain information about line number and the failed value

Alexey Goncharuk created IGNITE-14325: - Summary: SQL COPY command: when conversion fails, the error does not contain information about line number and the failed value Key: IGNITE-14325 URL:

Re: IEP-70: Async Continuation Executor

Alexey, .NET thick API delegates to Java directly. When you do ICache.PutAsync(): * Future is created on Java side, .listen() is called * TaskCompletionSource is created on .NET side, its Task is returned to the user * Operation completes, Future listener is called on the Java side * Listener

Review request - allocated RAM is always 0 for non-persistent regions

Hello! Guys, can you please review https://issues.apache.org/jira/browse/IGNITE-13878 ? I could not find a reviewer for this ticket. Regards, -- Ilya Kasnacheev

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Denis, Thank you. I'll prepare a blog post notes for the major 2.10 features. The release hasn't been announced yet, some artefacts still waiting to be published. Hope everything will be ready by the end of this week. > Btw, don't we want to arrange a meetup gathering for Virtual or >

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Hi Maxim, Ideally, a blog post should be published together with the announcement email. So that the readers can learn more details from the article. Anyway, you can post it later for 2.10 as long as the release is already completed. Btw, don't we want to arrange a meetup gathering for Virtual

[jira] [Created] (IGNITE-14324) EVT_CLIENT_NODE_DISCONNECTED is not triggered in k8s

Alexandr Shapkin created IGNITE-14324: - Summary: EVT_CLIENT_NODE_DISCONNECTED is not triggered in k8s Key: IGNITE-14324 URL: https://issues.apache.org/jira/browse/IGNITE-14324 Project: Ignite

[jira] [Created] (IGNITE-14323) Messaging naming unification

Sergey Chugunov created IGNITE-14323: Summary: Messaging naming unification Key: IGNITE-14323 URL: https://issues.apache.org/jira/browse/IGNITE-14323 Project: Ignite Issue Type: Sub-task

Re: IEP-70: Async Continuation Executor

Hi Pavel, Extending Java async API with additional Executor parameters looks OK to me. It is not clear from the IEP how you are going to do that for .NET async API. My understanding is in .NET we do not add any Executors. Instead, the Ignite Async API should use (SynchronizationContext.Current

Re: Hello

Hello! I have added you to Contributors role, you may assign tickets to yourself. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev пн, 15 мар. 2021 г. в 23:44, Marius Filip : > Hi Ilya > > My ID on Apache JIRA is

Re: How to Contribute 2021

So we do have 3 sources for how to contribute: 1. https://ignite.apache.org/community/contribute.html 2. https://github.com/apache/ignite/blob/master/CONTRIBUTING.md 3. https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute+2021 Seems that wiki is more technical, right? But is

Re: How to Contribute 2021

Hello again! Based on the feedback, I have removed ASCII art from the git section, making it shorter and clearer. Regards, -- Ilya Kasnacheev вт, 16 мар. 2021 г. в 11:47, Ilya Kasnacheev : > Hello, Pavel! > > At the very minimum, a newcomer should be able to run tests on TC or MTCGA. > >

[jira] [Created] (IGNITE-14322) False warning about DataRegionConfiguration.maxWalArchiveSize property usage

Aleksandr Polovtcev created IGNITE-14322: Summary: False warning about DataRegionConfiguration.maxWalArchiveSize property usage Key: IGNITE-14322 URL: https://issues.apache.org/jira/browse/IGNITE-14322

Re: How to Contribute 2021

Hello, Pavel! At the very minimum, a newcomer should be able to run tests on TC or MTCGA. Explaining that process takes most of the contribution guide. Even if somebody is ready to run those tests for a newcomer once or twice (already a long shot, it's hard to even get a simple review), they

Re: Long transaction suspended

hi jjimeno, plz check your throughput once more by using  OPTIMISTIC, SERIALIZABLE options, hope it would be more faster than default.   > > >--- Forwarded message --- >From: jjimeno < jjim...@omp.com > >To: u...@ignite.apache.org >Cc: >Subject: Long transaction suspended >Date: Thu, 04

[jira] [Created] (IGNITE-14321) Forced index rebuilding does not work correctly

Kirill Tkalenko created IGNITE-14321: Summary: Forced index rebuilding does not work correctly Key: IGNITE-14321 URL: https://issues.apache.org/jira/browse/IGNITE-14321 Project: Ignite