Folks,
I have created a new ticket [1] for moving system-region-related-properties
to its own class.
I will be pleased with your feedback on this topic.
1. https://issues.apache.org/jira/browse/IGNITE-15998
On Tue, 2 Nov 2021 at 19:58, Eduard Rakhmankulov
wrote:
> Hi, Andrey!
>
> Thank you
My concern was only that 1.0 is too high for TC overall.
If it is OK for Nightly builds — no problems.
However — ordinary Run All uses 0.1 scale and to use 0.2 in that suite we
should hardcode it inside the suite (or to be more precise — compute based on
input).
> On 25 Nov 2021, at 16:06,
Hello Ivan,
+1, the issue can be cherry-picked to the 2.12.
чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov :
>
> Hello everyone,
>
> is there a chance to add this issue to the release scope? [1]
> Currently, defragmentation of certain types of indexes can corrupt them.
> Fix is straightforward and
Hello everyone,
is there a chance to add this issue to the release scope? [1]
Currently, defragmentation of certain types of indexes can corrupt them.
Fix is straightforward and should not cause any problems.
Thank you!
[1] https://issues.apache.org/jira/browse/IGNITE-15968
вт, 23 нояб. 2021 г.
Petr,
For the RunAll - 0.2
For the RunAll(Nightly) - 1.0 (the 1.0 is better that 0.2 for sure)
On Thu, 25 Nov 2021 at 15:54, Petr Ivanov wrote:
>
> 0.2 or 1.0?
>
> > On 25 Nov 2021, at 14:34, Maxim Muzafarov wrote:
> >
> > Pert,
> >
> > I think for nightly builds this is the only right option
0.2 or 1.0?
> On 25 Nov 2021, at 14:34, Maxim Muzafarov wrote:
>
> Pert,
>
> I think for nightly builds this is the only right option for the
> suites mentioned above.
>
> On Thu, 25 Nov 2021 at 14:33, Petr Ivanov wrote:
>>
>> Hi, Maksim.
>>
>>
>> Run All (Nightly) build will run suites
Thanks!
Nikolay, Andrei,
I've already merged the patch.
чт, 25 нояб. 2021 г. в 14:36, Nikolay Izhikov :
> Hello, Andrei.
>
> I will review your changes shortly.
>
> > 25 нояб. 2021 г., в 14:31, Andrei Demidov
> написал(а):
> >
> > Hi!
> >
> > Could somebody please explain me.
> > Should I do something
Ok, thanks!
Hello, Andrei.
I will review your changes shortly.
> 25 нояб. 2021 г., в 14:31, Andrei Demidov
> написал(а):
>
> Hi!
>
> Could somebody please explain me.
> Should I do something for my changes to be merged?
> In contributing guide it's said that changes will be merged by any committer
>
Pert,
I think for nightly builds this is the only right option for the
suites mentioned above.
On Thu, 25 Nov 2021 at 14:33, Petr Ivanov wrote:
>
> Hi, Maksim.
>
>
> Run All (Nightly) build will run suites with test scale factor 1.0 — will it
> be a problem?
>
> > On 25 Nov 2021, at 14:22,
Hi, Maksim.
Run All (Nightly) build will run suites with test scale factor 1.0 — will it be
a problem?
> On 25 Nov 2021, at 14:22, Maxim Muzafarov wrote:
>
> Folks,
>
> I've merged the PR [1] to the master branch and applied scale factor
> 0.2 to the tests that were moved to dedicated
Hi!
Could somebody please explain me.
Should I do something for my changes to be merged?
In contributing guide it's said that changes will be merged by any committer
after review.
Thanks!
Folks,
I've merged the PR [1] to the master branch and applied scale factor
0.2 to the tests that were moved to dedicated suites.
I've created two suites and added them to the Run.All test suite.
- Snapshots [2]
- SnapshotsWithIndexes [3]
[1] https://github.com/apache/ignite/pull/9584/files
[2]
Igor,
I think it should list all operations, mostly the same as ClientOperation
enum, but without internal things like RESOURCE_CLOSE.
Users should be able to implement policies like "retry k/v operations, but
not SQL".
On Thu, Nov 25, 2021 at 12:27 PM Igor Sapego wrote:
> Pavel,
>
> What is
Pavel,
What is ClientOperationType? Will it list basically all operations or only
types like Idempotent, NonIdempotent?
Best Regards,
Igor
On Wed, Nov 24, 2021 at 5:21 PM Pavel Tupitsyn wrote:
> Igniters,
>
> I've prepared a proposal about thin client retry behavior.
> Please review and let
16 matches
Mail list logo
