Pavel Tupitsyn created IGNITE-13470:
---
Summary: .NET: Add async counterparts to all applicable thin
client APIs
Key: IGNITE-13470
URL: https://issues.apache.org/jira/browse/IGNITE-13470
Project:
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
TcpDiscoverySpiFailureTimeoutSelfTest.testConnectionCheckMessage
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master Cache 7
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache7?branch=%3Cdefault%3E
No changes in the build
- Here's a
My vote is to just call ignite "IgniteDB". That's it. No other additional
explanation is required as no amount of additional verbiage will help.
Every DB is different: from MongoDB, to RedisDB, to CockroachDB, to Oracle
- they all look & act completely different, and they don't go around trying
to
Kirill Tkalenko created IGNITE-13469:
Summary: Adaptation control.sh to picocli framework
Key: IGNITE-13469
URL: https://issues.apache.org/jira/browse/IGNITE-13469
Project: Ignite
Issue
Sergey,
> From the code complexity perspective I'm trying to design the feature in
> such a way that all maintenance code is as encapsulated as possible and
> avoids massive interventions into main workflows of components.
Could please briefly tell what means do you use to achieve
Pavel Tupitsyn wrote
>> result of a remote execution is a CompletionStage
>
> Can you give an example? What is a remote execution? Is this about Compute
> and/or Services?
This is about Compute.
Let's say I'm doing affinityCallAsync for IgniteCallable where R
implements CompletableStage or R is
Stephen Darlington created IGNITE-13468:
---
Summary: Destroying a caches doesn't clean up cache directory
Key: IGNITE-13468
URL: https://issues.apache.org/jira/browse/IGNITE-13468
Project: Ignite
> result of a remote execution is a CompletionStage
Can you give an example? What is a remote execution? Is this about Compute
and/or Services?
On Mon, Sep 21, 2020 at 5:11 PM mnk wrote:
> So one question I have here (and this maybe out of scope) - but what about
> the cases where the result
So one question I have here (and this maybe out of scope) - but what about
the cases where the result of a remote execution is a CompletionStage? In
this case, I would want to have a local CompletionStage which "represents"
the remote one. In other words when the remote one is completed, the value
So one question I have here (and this maybe out of scope) - but what about
the cases where the result of a remote execution is a CompletionStage? In
this case, I would want to have a local CompletionStage which "represents"
the remote one. In other words when the remote one is completed, the value
Maxim Muzafarov created IGNITE-13467:
Summary: Add events for snapshot operation
Key: IGNITE-13467
URL: https://issues.apache.org/jira/browse/IGNITE-13467
Project: Ignite
Issue Type:
Hello, Sergey.
> At the moment I'm aware about two use cases for this feature: corrupted PDS
> cleanup and defragmentation.
AFAIKU There is third use-case for this mode.
Change encryption master key in case node was down during cluster master key
change.
In this case, node can’t join to the
Aleksey Plekhanov created IGNITE-13465:
--
Summary: Ignite cluster falls apart if two nodes segmented
sequentially
Key: IGNITE-13465
URL: https://issues.apache.org/jira/browse/IGNITE-13465
Ivan,
Sorry for some confusion, MM indeed is not a normal mode. What I was trying
to say is that when in MM node still starts and allows the user to perform
actions with it like sending commands via control utility/JMX APIs or
reading metrics.
This is the key point: although the node is not in
https://issues.apache.org/jira/browse/IGNITE-13464
> On 21 Sep 2020, at 11:02, Ilya Kasnacheev wrote:
>
> Hello!
>
> Good catch! I think you should file a critical level ticket about it.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 21 сент. 2020 г. в 12:56, Stephen Darlington
>
Stephen Darlington created IGNITE-13464:
---
Summary: Ignite-rest-http includes vulnerable dependencies
Key: IGNITE-13464
URL: https://issues.apache.org/jira/browse/IGNITE-13464
Project: Ignite
Stanilovsky Evgeny created IGNITE-13463:
---
Summary: Calcite improvements. Rework RootNode rows exchange.
Key: IGNITE-13463
URL: https://issues.apache.org/jira/browse/IGNITE-13463
Project: Ignite
Guys,
During internal testing, we've found a critical bug with discovery (cluster
falls apart if two nodes segmented sequentially). This problem is not
reproduced in 2.8.1. I think we should fix it before release. Under
investigation now. I'll let you know when we get something.
чт, 17 сент.
Pavel Tupitsyn created IGNITE-13462:
---
Summary: .NET: Thin client Dispose hangs when continuous query is
active on .NET Core 3.x
Key: IGNITE-13462
URL: https://issues.apache.org/jira/browse/IGNITE-13462
20 matches
Mail list logo
