Folks,
Let's carry on with this discussion. We're about to start a 2.8.1 vote and
it's good to have this discussion settled once that version is released.
What do you think about my last proposal?
-
Denis
On Fri, May 8, 2020 at 2:21 PM Denis Magda wrote:
> Maxim, Folks,
>
> Speaking of
I've created the Ignite ticket for this improvement [1].
[1] https://issues.apache.org/jira/browse/IGNITE-13047
чт, 21 мая 2020 г. в 00:46, Sergey Antonov :
> Hello, Igniters!
>
> I'd like to discuss behaviour of Ignite process exit code if the node was
> stopped by failure handler [1][2]. At
Hi Dmitry,
PersonKey { id: int, passportNo: String }
> Person { passportNo: String, name: String }
What's the primary reason for keeping a copy of "passportNo" field in the
value object? Personally, I treat this as an anti-pattern that should have
been influenced by some of the old Ignite
Sergey Antonov created IGNITE-13047:
---
Summary: Ignite node must return Ignition#KILL_EXIT_CODE exit
code, if node had stopped by StopNodeFailureHandler or
StopNodeOrHaltFailureHandler
Key: IGNITE-13047
URL:
Hello, Igniters!
I'd like to discuss behaviour of Ignite process exit code if the node was
stopped by failure handler [1][2]. At the moment ignite process returns
exit code 0 after the stop in all scenarios, except runtime halt by
StopNodeOrHaltFH [1]. In this case, the exit code will be 130 [3]
Hello, Alexey! Unfortunately, my response was delayed.
Point 2: You can do as you suggested, I think it is still worth specifying how
many partitions were obtained.
[2020-05-06 20:56:37,044][INFO ][...] Completed rebalancing [grp=cache1,
supplier=94a3fcbc-18d5-4c64-b0ab-4313aba1,
Andrey N. Gura created IGNITE-13046:
---
Summary: Flaky test
SqlSystemViewsSelfTest.testTableViewDuringRebuilding
Key: IGNITE-13046
URL: https://issues.apache.org/jira/browse/IGNITE-13046
Project:
Hi, Maxim! Unfortunately, I delayed my answer.
The production environment may not be ideal and problems may occur in it. I
only suggest adding a little logging to understand some of the cases that may
occur during operation. In addition, this functionality can be disabled by the
system
Could you please share a reproducer with us?
-
Denis
On Tue, May 19, 2020 at 8:33 AM Henrique Arroyo
wrote:
> Hi,
>
> I am experiencing an issue related to enum data types in ignite cluster,
> the following message is displayed during object deserialization:
>
> Caused by: class
Maxim Muzafarov created IGNITE-13045:
Summary: SystemWorkersBlockingTest may fail NullPointerException
if MXBean not found
Key: IGNITE-13045
URL: https://issues.apache.org/jira/browse/IGNITE-13045
Stanilovsky Evgeny created IGNITE-13044:
---
Summary: Additional possibility to check for high contending keys
through transactional payload.
Key: IGNITE-13044
URL:
Hi , need your help, or give a link, or give a hint on this deployment,
Ignite Jar deployment case,
Say I have a jar package with the main-class defined, and put it into the
./libs folder, what will the ignite do, ignite how to launch this Jar? Which
is the endpoint for Ignite launch this Jar?
Hello. Sure this feature is of great importance and we'd like to get it asap.
It is very confusing to support the logic of copying values between key and
value classes.
Thanks.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Ivan Daschinskiy created IGNITE-13043:
-
Summary: Fix compilation error in Ignite C++, when boost version
is greater than 1.70
Key: IGNITE-13043
URL: https://issues.apache.org/jira/browse/IGNITE-13043
Ivan Daschinskiy created IGNITE-13042:
-
Summary: Update SSL certificates in C++ test suites to more secure
signature
Key: IGNITE-13042
URL: https://issues.apache.org/jira/browse/IGNITE-13042
Hello, Igniters.
I prepared a PR with release notes.
Please, take a look [1]
[1] https://github.com/apache/ignite/pull/7821
> 20 мая 2020 г., в 13:06, Nikolay Izhikov написал(а):
>
> Hello, Jury.
>
> It seems we reached code freeze step for 2.8.1 release.
> I will prepare rc for it shortly.
Anton Kalashnikov created IGNITE-13041:
--
Summary: PDS (Indexing) is failed with 137 code
Key: IGNITE-13041
URL: https://issues.apache.org/jira/browse/IGNITE-13041
Project: Ignite
Issue
Vladimir Steshin created IGNITE-13040:
-
Summary: Remove unused parameter from
TcpDiscoverySpi.writeToSocket()
Key: IGNITE-13040
URL: https://issues.apache.org/jira/browse/IGNITE-13040
Project:
Igniters,
Currently Ignite Key/Value API allows to have both Key and Value fields with
the same name. Use of SQL DML to update such an entry will update only the
key field, leaving the value field unchanged. Seems that it's a bit
inconvenient for the mixed K/V and SQL API apps.
This is a
Pavel,
I will try to benchmark by myself. Thank you.
ср, 20 мая 2020 г. в 13:54, Pavel Tupitsyn :
> Alex,
>
> Thank you, the IEP looks complete now.
>
> Are you going to do the comparison benchmark of 1-operation vs 2-operation
> modes?
> I can do that too, just want to avoid duplicate work.
>
Stanilovsky Evgeny created IGNITE-13039:
---
Summary: Get rid of possibility to change final static fields
through reflection for test purpose.
Key: IGNITE-13039
URL:
Alex,
Thank you, the IEP looks complete now.
Are you going to do the comparison benchmark of 1-operation vs 2-operation
modes?
I can do that too, just want to avoid duplicate work.
On Wed, May 20, 2020 at 1:17 PM Alex Plehanov
wrote:
> Pavel,
>
> Yes, looks like we can get this information
Pavel,
Yes, looks like we can get this information from ServiceDescriptor. I've
removed 'interface name' from requests in IEP. Thank you!
ср, 20 мая 2020 г. в 12:58, Pavel Tupitsyn :
> Alex,
>
> IEP looks good to me in general.
>
> One question: what is `Interface name` in the request?
> As I
Hello, Jury.
It seems we reached code freeze step for 2.8.1 release.
I will prepare rc for it shortly.
> 14 мая 2020 г., в 11:08, Юрий написал(а):
>
> Nikolay,
>
> Release 2.8.1 are delayed and announced dates [1] at release page is not
> actual. Could you update it to reflect current vision
Alex,
IEP looks good to me in general.
One question: what is `Interface name` in the request?
As I understand, service name is enough to retrieve ServiceDescriptor,
and then we can get serviceClass from there.
On Wed, May 20, 2020 at 12:42 PM Alex Plehanov
wrote:
> Pavel,
>
> I've moved
Pavel,
I've moved proposals from this thread to the IEP [1] and described changes
to protocol, please have a look.
[1] :
https://cwiki.apache.org/confluence/display/IGNITE/IEP-46%3A+Thin+Client+Service+Invocation
пн, 18 мая 2020 г. в 15:09, Pavel Tupitsyn :
> Hi Alex,
>
> Thanks for starting
26 matches
Mail list logo
