[jira] [Created] (IGNITE-14448) Failure to connect to node leads to hanging connection future if paired connections are used

Semyon Danilov created IGNITE-14448: --- Summary: Failure to connect to node leads to hanging connection future if paired connections are used Key: IGNITE-14448 URL: https://issues.apache.org/jira/browse/IGNITE-144

Re: Terms clarification and modules splitting logic

Alexei, I had the same opinion regarding the internal package, but we still need to somehow distinguish between public and internal classes in the ignite-util module. If we introduce the internal package in the util, we should follow the same structure in other modules. Thoughts? вт, 30 мар. 202

[jira] [Created] (IGNITE-14449) Add binary meta change event to CDCCosumer

Nikolay Izhikov created IGNITE-14449: Summary: Add binary meta change event to CDCCosumer Key: IGNITE-14449 URL: https://issues.apache.org/jira/browse/IGNITE-14449 Project: Ignite Issue T

[jira] [Created] (IGNITE-14450) Add Maximum CDC directory size configuration parameter

Nikolay Izhikov created IGNITE-14450: Summary: Add Maximum CDC directory size configuration parameter Key: IGNITE-14450 URL: https://issues.apache.org/jira/browse/IGNITE-14450 Project: Ignite

Re: Terms clarification and modules splitting logic

Alexey, I would instead suggest moving the public utility classes to org.apache.ignite.api. package in the util module to separate them from internal classes, if we really need this. Actually, I don't think there is a point in separating public/internal classes in the util module. What are the b

[jira] [Created] (IGNITE-14451) PK becomes corrupted after node restart

Taras Ledkov created IGNITE-14451: - Summary: PK becomes corrupted after node restart Key: IGNITE-14451 URL: https://issues.apache.org/jira/browse/IGNITE-14451 Project: Ignite Issue Type: Bug

Re: Terms clarification and modules splitting logic

This won't work with the Java Jigsaw module system because it prohibits having two identical packages in different modules. I really hope that we will adopt Jigsaw in the near future. Unless you are suggesting moving all utility classes under org.apache.ignite.api.util package, bit this looks reall

[jira] [Created] (IGNITE-14452) Add cehcking of the iptables settings applied.

Vladimir Steshin created IGNITE-14452: - Summary: Add cehcking of the iptables settings applied. Key: IGNITE-14452 URL: https://issues.apache.org/jira/browse/IGNITE-14452 Project: Ignite I

[jira] [Created] (IGNITE-14453) Issue with persistence when using JDK15

Emmanuel Wiesenfeld created IGNITE-14453: Summary: Issue with persistence when using JDK15 Key: IGNITE-14453 URL: https://issues.apache.org/jira/browse/IGNITE-14453 Project: Ignite Is

[jira] [Created] (IGNITE-14454) [Ignite Website] Update for events schedule

Kseniya Romanova created IGNITE-14454: - Summary: [Ignite Website] Update for events schedule Key: IGNITE-14454 URL: https://issues.apache.org/jira/browse/IGNITE-14454 Project: Ignite Issu

Re: [DISCUSSION] IgniteFuture class future in Ignite-3.0.

CompletableFuture cancellation will not work as many users expected. Javadoc says: /* Since (unlike {@link FutureTask}) this class has no direct * control over the computation that causes it to be completed, * cancellation is treated as just another form of exceptional * completion. */ Completion o

Re: Terms clarification and modules splitting logic

Alexey, Can you provide us some details on jygsaw adoption to better understand the benefits ? "We should be free to change them without any compatibility contract" - let's mark such classes with a special annotation like @Internal, will it work for you ? ср, 31 мар. 2021 г. в 15:10, Alexey Go

Re: [DISCUSSION] IgniteFuture class future in Ignite-3.0.

Hi Andrey, Please see below. -Val On Wed, Mar 31, 2021 at 7:55 AM Andrey Mashenkov wrote: > CompletableFuture cancellation will not work as many users expected. > Javadoc says: > /* Since (unlike {@link FutureTask}) this class has no direct > * control over the computation that causes it to be

[jira] [Created] (IGNITE-14455) The directory with logs must contain IgniteConfiguration.xml for ducktests.

Sergei Ryzhov created IGNITE-14455: -- Summary: The directory with logs must contain IgniteConfiguration.xml for ducktests. Key: IGNITE-14455 URL: https://issues.apache.org/jira/browse/IGNITE-14455 Pro

[jira] [Created] (IGNITE-14456) Ignite Extensions: change copyrights to 2021

Amelchev Nikita created IGNITE-14456: Summary: Ignite Extensions: change copyrights to 2021 Key: IGNITE-14456 URL: https://issues.apache.org/jira/browse/IGNITE-14456 Project: Ignite Issue

[jira] [Created] (IGNITE-14457) Update Ignite 3 binary build structure

Valentin Kulichenko created IGNITE-14457: Summary: Update Ignite 3 binary build structure Key: IGNITE-14457 URL: https://issues.apache.org/jira/browse/IGNITE-14457 Project: Ignite Iss

[MTCGA]: new failures in builds [5937164] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master EncryptedCacheExampleSelfTest.testBinaryPutGetExample https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4398970792

Re: [DISCUSSION] IgniteFuture class future in Ignite-3.0.

Folks, Regarding Reactive abstractions. While it might look too complex for simple KV cases it can be quite powerful for queries. Also there are known solutions for cancellation, backpressure and flow control. It can greatly simplify things for users familiar with Reactive programming rather than

[jira] [Created] (IGNITE-14458) Fix flaky IgniteLocalWalSizeTest

Kirill Tkalenko created IGNITE-14458: Summary: Fix flaky IgniteLocalWalSizeTest Key: IGNITE-14458 URL: https://issues.apache.org/jira/browse/IGNITE-14458 Project: Ignite Issue Type: Impro