Hi Taras,
If there are enough improvements for 2.14.1, I don't mind it. Otherwise -
there's no point
in making a release for this specific bug.
пт, 30 сент. 2022 г. в 14:42, Taras Ledkov :
> Hi, Ivan.
>
> My apologies.
> A blocking performance issue has been fixed [1]. And the release candidate
Hello Igniters,
I know I'm late, but is there a chance to add one more fix to the scope?
It is very local and fixes and issue, brought to us in user-list recently,
where PDS
defragmentation simply doesn't work on Windows, because we don't close file
descriptors properly.
This code will not affect
Hello, Mike.
Ignite provide built-in performance tests - yardstick.
You can read about them in documentation.
As this tests requires some hi-end hardware it executes on the private
infrastructure.
So, yes, results of the tests discussed privately.
You can reproduce this results if you have enou
Hi, Taras.
Granted!
> On 22 Aug 2022, at 15:34, Taras Ledkov wrote:
>
> Hi,
>
> 1. Petr, could you grant me TC permissions to run release builds please?
> 2. Pavel, please cherry pick your patch for IGNITE-17559 [1] to the release
> branch ignite-2.14 [2]. Or we could move the issue to the ne
+1 from my side. Count on my support if somethings need to be done from PMC
This link works for me (without pre-selected issue in URL JIRA displays
more predictable results):
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixV
Dear Ignite Community!
I suggest starting Apache Ignite 2.14 release activities.
We've accumulated a hundred resolved [1] issues with new
features and bug fixes which are waiting for their release date. For
example,
- bunch of Calcite based SQL engine fixes and improvements;
- thin clients improv
