Alex,
My congratulations!
ср, 18 нояб. 2020 г. в 05:38, Saikat Maitra :
>
> Congratulations Alex!!!
>
> On Tue, 17 Nov 2020 at 6:26 PM, Denis Magda wrote:
>
> > Igniters,
> >
> > The Project Management Committee (PMC) for Apache Ignite
> > has invited Alex to become a PMC member and we are pleas
Congrats!
> 18 нояб. 2020 г., в 11:00, Nikita Amelchev написал(а):
>
> Alex,
>
> My congratulations!
>
> ср, 18 нояб. 2020 г. в 05:38, Saikat Maitra :
>>
>> Congratulations Alex!!!
>>
>> On Tue, 17 Nov 2020 at 6:26 PM, Denis Magda wrote:
>>
>>> Igniters,
>>>
>>> The Project Management Com
Congratulations Alex!
2020-11-18 11:17 GMT+03:00, Nikolay Izhikov :
> Congrats!
>
>> 18 нояб. 2020 г., в 11:00, Nikita Amelchev
>> написал(а):
>>
>> Alex,
>>
>> My congratulations!
>>
>> ср, 18 нояб. 2020 г. в 05:38, Saikat Maitra :
>>>
>>> Congratulations Alex!!!
>>>
>>> On Tue, 17 Nov 2020 at 6
Hi Ilya! Thank you for up the topic. I will come back with fixes and
comments in a couple of days.
On Tue, Nov 17, 2020 at 4:26 PM Ilya Kasnacheev
wrote:
> Hello!
>
> I have left some comments and there's also more discussion there. Can you
> please look?
>
> Thanks,
> --
> Ilya Kasnacheev
>
>
>
jifwin created IGNITE-13719:
---
Summary: Thin client silently closes channel after inactivity
Key: IGNITE-13719
URL: https://issues.apache.org/jira/browse/IGNITE-13719
Project: Ignite
Issue Type: Bug
Hooray!
Congratulations, Alex! Well deserved achievement!
Thanks,
S.
ср, 18 нояб. 2020 г. в 03:26, Denis Magda :
> Igniters,
>
> The Project Management Committee (PMC) for Apache Ignite
> has invited Alex to become a PMC member and we are pleased to announce that
> he has accepted.
>
> Alex joi
Alex, congrats!
ср, 18 нояб. 2020 г. в 13:39, Вячеслав Коптилин :
> Hooray!
>
> Congratulations, Alex! Well deserved achievement!
>
> Thanks,
> S.
>
> ср, 18 нояб. 2020 г. в 03:26, Denis Magda :
>
> > Igniters,
> >
> > The Project Management Committee (PMC) for Apache Ignite
> > has invited Alex
Anton Kalashnikov created IGNITE-13720:
--
Summary: Defragmentation parallelism implementation
Key: IGNITE-13720
URL: https://issues.apache.org/jira/browse/IGNITE-13720
Project: Ignite
Iss
Hello, Igniters.
Since the migration of Ignite Spring Data modules to extensions, thin
client support for Spring Data integration was implemented. - [1].
To make this feature available for users, I propose to start the release
process of the following modules:
* ignite-spring-data
* ignite-
+1
> 18 нояб. 2020 г., в 14:38, Mikhail Petrov написал(а):
>
> Hello, Igniters.
>
> Since the migration of Ignite Spring Data modules to extensions, thin client
> support for Spring Data integration was implemented. - [1].
>
> To make this feature available for users, I propose to start the r
Stanilovsky Evgeny created IGNITE-13721:
---
Summary: Calcite bug. IndexOutOfBoundsException while executing
NOT IN with nested expression.
Key: IGNITE-13721
URL: https://issues.apache.org/jira/browse/IGNITE-1
Mikhail Petrov created IGNITE-13722:
---
Summary: Ignite Spring Data: Ignite resources are not closed
properly when closing Spring context.
Key: IGNITE-13722
URL: https://issues.apache.org/jira/browse/IGNITE-13722
Maksim Timonin created IGNITE-13723:
---
Summary: Lost & Failed Tests
Key: IGNITE-13723
URL: https://issues.apache.org/jira/browse/IGNITE-13723
Project: Ignite
Issue Type: Bug
Repo
Maxim Muzafarov created IGNITE-13724:
Summary: Checkstyle not check on ignite-examples due to the source
directory swap
Key: IGNITE-13724
URL: https://issues.apache.org/jira/browse/IGNITE-13724
Pr
Maxim Muzafarov created IGNITE-13725:
Summary: Add snapshot check command
Key: IGNITE-13725
URL: https://issues.apache.org/jira/browse/IGNITE-13725
Project: Ignite
Issue Type: Improvement
Folks,
I've found an interesting thing about delays on node failed detection
depending on discovery type.
For example, when we have 33 nodes cluster (33 vms in the cloud in my
case), we have the following failure detection delays:
~ 10 seconds on TcpDiscovery
~ 8.5 seconds on ZookeeperDiscovery
w
Are we keeping the original names of theses Spring modules? In separate
threads I saw that the names of other extensions end with “ext”.
Also, how about making a single release of all the extensions that were
migrated from the main Ignite repo. There are many of them waiting for this
to happen. Sa
Denis,
I omitted "-ext" for simplicity. Currently, this suffix is present in
the name of all Spring Data integration modules [1], [2], [3].
[1] -
https://github.com/apache/ignite-extensions/tree/master/modules/spring-data-2.2-ext
[2] -
https://github.com/apache/ignite-extensions/tree/mast
Aleksey Plekhanov created IGNITE-13726:
--
Summary: Add an ability to view count of hot and cold pages in
page memory
Key: IGNITE-13726
URL: https://issues.apache.org/jira/browse/IGNITE-13726
Proje
Stanilovsky Evgeny created IGNITE-13727:
---
Summary: Calcite bug. Assertion on UNION with DISTINCT.
Key: IGNITE-13727
URL: https://issues.apache.org/jira/browse/IGNITE-13727
Project: Ignite
Maksim Timonin created IGNITE-13728:
---
Summary: Ignored load / benchmark tests
Key: IGNITE-13728
URL: https://issues.apache.org/jira/browse/IGNITE-13728
Project: Ignite
Issue Type: New Featu
My congratulations!
Best Regards,
Mirza Aliev
ср, 18 нояб. 2020 г. в 13:51, Vyacheslav Daradur :
> Alex, congrats!
>
> ср, 18 нояб. 2020 г. в 13:39, Вячеслав Коптилин >:
>
> > Hooray!
> >
> > Congratulations, Alex! Well deserved achievement!
> >
> > Thanks,
> > S.
> >
> > ср, 18 нояб. 2020 г. в
Stanilovsky Evgeny created IGNITE-13729:
---
Summary: Calcite bug. "Not a boolean expression" on nested
expression.
Key: IGNITE-13729
URL: https://issues.apache.org/jira/browse/IGNITE-13729
Project
Thanks, guys!
ср, 18 нояб. 2020 г. в 17:29, Мирза Алиев :
> My congratulations!
>
> Best Regards,
> Mirza Aliev
>
> ср, 18 нояб. 2020 г. в 13:51, Vyacheslav Daradur :
>
>> Alex, congrats!
>>
>> ср, 18 нояб. 2020 г. в 13:39, Вячеслав Коптилин > >:
>>
>> > Hooray!
>> >
>> > Congratulations, Alex! W
Hello, Igniters!
Currently, for page replacement (page rotation between page-memory and
disk) we use Random-LRU algorithm. It has a low maintenance cost and
relatively simple implementation, but it has many disadvantages and affects
performance very much when replacement is started. We even have w
Ilya Kasnacheev created IGNITE-13730:
Summary: Unify fallback properties for SSL settings as per Java
standard
Key: IGNITE-13730
URL: https://issues.apache.org/jira/browse/IGNITE-13730
Project: Ig
Sergey Uttsel created IGNITE-13731:
--
Summary: High contention on
GridCachePartitionExchangeManager.ExchangeFutureSet#values.
Key: IGNITE-13731
URL: https://issues.apache.org/jira/browse/IGNITE-13731
Thanks, guys. It looks like we are much closer to the consensus now. I
totally on board with the plan, but I would also like to address the
short-term needs. As I've already mentioned earlier, there are several
active IEPs, but we still don't have even a preliminary technical process
for working on
Hi,
Mikhail, Can we please rename ignite-spring-data-commons to
ignite-spring-data-commons-ext?
Denis,
We are good to release the following migrated modules as well...
ignite-flink-ext
ignite-flume-ext
ignite-pub-sub-ext
ignite-zeromq-ext
ignite-twitter-ext
ignite-rocketmq-ext
ignite-mqtt-ext
i
Alexey, we already have changes that partially fixes this issue [1]
Easy way:
Looks like we already have converge in page replacement.
If we change 5 times touch iterator from random lru algo into, for example — 7
we will obtain fast improvement from scratch.
» Batch page replacement
This appro
I would object against all together release of these modules if this process
will be done in single release branch / tag.
Despite of the fact that all these extensions are in single repository, we have
to treat them as separate projects with separate release cycle and release each
one of them in
Stanilovsky Evgeny created IGNITE-13732:
---
Summary: Incorrect inline suggestion.
Key: IGNITE-13732
URL: https://issues.apache.org/jira/browse/IGNITE-13732
Project: Ignite
Issue Type: Bug
11+ separate votes is an overkill. We certainly want, and agreed, to be
able to release each extension separately. But I see nothing wrong if
releases of N extensions are passed through a single vote.
On Wednesday, November 18, 2020, Petr Ivanov wrote:
> I would object against all together relea
Hello.
I think it’s up to the release manager to decide what extension he(or she)
wants to release.
Do we have a release manager who wants to release all extensions?
> 19 нояб. 2020 г., в 10:33, Denis Magda написал(а):
>
> 11+ separate votes is an overkill. We certainly want, and agreed, to b
No 11 separate votes, but 11 separate tags is all I am proposing :)
> On 19 Nov 2020, at 10:33, Denis Magda wrote:
>
> 11+ separate votes is an overkill. We certainly want, and agreed, to be
> able to release each extension separately. But I see nothing wrong if
> releases of N extensions are p
35 matches
Mail list logo
