Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Pavel Pereslegin created IGNITE-13807:
-
Summary: testClientNodeJoinInactiveClusterWithNewStaticCacheConfig
and testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master
Key: IGNITE-13807
URL:
Yaroslav Molochkov created IGNITE-13806:
---
Summary: Merge release notes for 2.9.1 into master
Key: IGNITE-13806
URL: https://issues.apache.org/jira/browse/IGNITE-13806
Project: Ignite
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Pavel Pereslegin created IGNITE-13805:
-
Summary: Add support for cache group restore from a snapshot on
the same topology (inactive cluster)
Key: IGNITE-13805
URL:
Pavel Tupitsyn created IGNITE-13804:
---
Summary: Java thin: avoid buffer copies in synchronous operations
Key: IGNITE-13804
URL: https://issues.apache.org/jira/browse/IGNITE-13804
Project: Ignite
Alexey Zinoviev created IGNITE-13803:
Summary: Scalar test failed due to incorrect Jackson dependency
Key: IGNITE-13803
URL: https://issues.apache.org/jira/browse/IGNITE-13803
Project: Ignite
Ilya, Vladimir hello!
I've added them all.
Nightly run should be triggered on my PR (#8508) instead of 2.9.1 branch,
if it's not added directly, of course.
Guys, I think that's enough issues for a minor release, I will proceed with
the final testing and building the RC.
On Wed, Dec 2, 2020 at
-1 for disabling test without removing the code. Current tests give us at
least "something works" status for the feature available to users, without
these tests, we can smoothly move to "totally unusable" status.
Complete removal of MVCC can be resource-consuming, but if we want to
disable tests
Hi,
I don't think so. It looks like a bug that tests fail if one runs them
within their module (actually, what is the goal of this test?). The check
showed us this problem, there is no need to fix the check.
Currently I see two ways:
1. Find the right module for every misplaced test. There are
Hello!
I think this means that we should abandon the plan of moving tests between
suites, and that your tool has to understand the dependency graph
between modules' tests when assessing what's included and what's not.
Regards,
--
Ilya Kasnacheev
ср, 2 дек. 2020 г. в 15:56, Max Timonin :
>
> Yes, it can be done. However, I don't think that we will get an agreement on
> that
Let’s give it a try and see what happens :)
> 2 дек. 2020 г., в 17:23, Вячеслав Коптилин
> написал(а):
>
>> Can you start the vote?
> Yes, it can be done. However, I don't think that we will get an
> Can you start the vote?
Yes, it can be done. However, I don't think that we will get an agreement
on that (I just recall the previous discussion).
And so, we will not remove the MVCC code; on the other hand, nobody will
support it in the future. We already at this point. This is just my humble
Sounds good!
> On 2 Dec 2020, at 16:21, Maxim Muzafarov wrote:
>
> Pert,
>
> I think we should start with the vote.
> So, the plan can be:
>
> 1. Vote for MVCC removal (if success then next steps)
> 2. Disable MVCC with some patch.
> 3. Turn off tests on TC.
> 4. Create issues with full code
+1
02.12.2020, 16:47, "Nikolay Izhikov" :
>> Why should we waste every contributor's time? IMHO, MVCC suites are useless
>> and everyone just pushes "re-run possible blockers" button and doesn't care
>> about MVCC tests at all.
>
> +1.
>
>> 2 дек. 2020 г., в 16:39, Вячеслав Коптилин
>>
Ivan Bessonov created IGNITE-13802:
--
Summary: GridCacheOffheapManager#addPartitions ignores candidate
pages count for index partition
Key: IGNITE-13802
URL: https://issues.apache.org/jira/browse/IGNITE-13802
Slava,
Can you start the vote?
It's strange turning off here the whole MVCC tests just because
something in the master branch was broken when in the second thread
Community decide to continue MVCC support. Let's start the vote and
see what happens.
On Wed, 2 Dec 2020 at 16:39, Вячеслав Коптилин
> Why should we waste every contributor's time? IMHO, MVCC suites are useless
> and everyone just pushes "re-run possible blockers" button and doesn't care
> about MVCC tests at all.
+1.
> 2 дек. 2020 г., в 16:39, Вячеслав Коптилин
> написал(а):
>
>> It will be even worse if our users will
Igor Sapego created IGNITE-13801:
Summary: ODBC: Check ODBC driver with Ab Initio and fix all issues
Key: IGNITE-13801
URL: https://issues.apache.org/jira/browse/IGNITE-13801
Project: Ignite
Hello everyone!
My name is Aleksey Rostov, I want to contribute to Ignite.NET. I am
currently a senior .net developer in Saint Petersburg. Please, help me to
start contributing.
I have created a jira account - arostov.
> It will be even worse if our users will face NPE or things like that in
the basic MVCC scenarios just because we don’t tests it.
The feature is not production-ready, and I don't think it is used at all.
Moreover, MVCC Cache 7, 8, 8, MVCC PDS 1, 2, 4 are already broken
(execution timeouts, flaky
Alexey Goncharuk created IGNITE-13800:
-
Summary: Provide distributed metastorage interface
Key: IGNITE-13800
URL: https://issues.apache.org/jira/browse/IGNITE-13800
Project: Ignite
Issue
Alexey Goncharuk created IGNITE-13799:
-
Summary: Provide a required storage interface for metastorage and
partitions for replication protocol
Key: IGNITE-13799
URL:
+1 for the plan
> 2 дек. 2020 г., в 16:21, Maxim Muzafarov написал(а):
>
> Pert,
>
> I think we should start with the vote.
> So, the plan can be:
>
> 1. Vote for MVCC removal (if success then next steps)
> 2. Disable MVCC with some patch.
> 3. Turn off tests on TC.
> 4. Create issues with
Pert,
I think we should start with the vote.
So, the plan can be:
1. Vote for MVCC removal (if success then next steps)
2. Disable MVCC with some patch.
3. Turn off tests on TC.
4. Create issues with full code removal.
On Wed, 2 Dec 2020 at 16:03, Petr Ivanov wrote:
>
> How about:
>
>
> 1.
Alexey Goncharuk created IGNITE-13798:
-
Summary: Prototype Raft implementation port to a separate
zero-dependency Ignite module
Key: IGNITE-13798
URL: https://issues.apache.org/jira/browse/IGNITE-13798
Stanilovsky Evgeny created IGNITE-13797:
---
Summary: Calcite bug. CREATE TABLE with WHERE SELECT 1;
Key: IGNITE-13797
URL: https://issues.apache.org/jira/browse/IGNITE-13797
Project: Ignite
Maksim Timonin created IGNITE-13796:
---
Summary: Update docs for the kubernetes module)
Key: IGNITE-13796
URL: https://issues.apache.org/jira/browse/IGNITE-13796
Project: Ignite
Issue Type:
SammyVimes opened a new pull request #2:
URL: https://github.com/apache/ignite-nodejs-thin-client/pull/2
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
How about:
1. Disable MVCC with some patch.
2. Turn off tests.
3. Plan full code removal.
?
> On 2 Dec 2020, at 16:01, Nikolay Izhikov wrote:
>
>> I think test suites can be disabled even today
>
> I’m -1 to disable tests without complete removal.
> It will be even worse if our users will
> I think test suites can be disabled even today
I’m -1 to disable tests without complete removal.
It will be even worse if our users will face NPE or things like that in the
basic MVCC scenarios just because we don’t tests it.
> 2 дек. 2020 г., в 15:50, Вячеслав Коптилин
> написал(а):
>
>
Ivan Bessonov created IGNITE-13795:
--
Summary: java.nio.file.InvalidPathException: Illegal char <:> at
lock page on windows
Key: IGNITE-13795
URL: https://issues.apache.org/jira/browse/IGNITE-13795
Hi, Ilya!
I've checked testsuites. There is an issue. For example
*IgniteBinaryCacheQueryTestSuite* suite is now in 2 modules: ignite-core,
ignite-indexing. On TeamCity it runs by "Query 1" suite. Simplified maven
command for the suite is
mvn -DtestIgniteBinaryCacheQueryTestSuite -am -pl
Semyon Danilov created IGNITE-13794:
---
Summary: Add partition awareness to NodeJS client
Key: IGNITE-13794
URL: https://issues.apache.org/jira/browse/IGNITE-13794
Project: Ignite
Issue
Hi Nikolay,
> Why do we need feature in the project that not even tested regularly?
Fair enough. However, I am not an expert in this area (MVCC and SQL), so I
cannot say how much effort it will take.
I would say that the opinion of the rest of the community is needed here.
Anyway, I think test
Igor Sapego created IGNITE-13793:
Summary: ODBC: Implement SQLRowCount for select queries
Key: IGNITE-13793
URL: https://issues.apache.org/jira/browse/IGNITE-13793
Project: Ignite
Issue
Hello, Slava!
Yes, this topic comes to the top from time to time :)
> . I just want to save the time required for getting TCBot's visa and TC
> resources.
Why do we need feature in the project that not even tested regularly?
> 2 дек. 2020 г., в 15:36, Вячеслав Коптилин
> написал(а):
>
>
Hello Nikolay,
> +1 to vote for complete MVCC removal.
It has already been discussed here [1] and, unfortunately, I have not seen
an agreement on that.
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-td45669.html
Thanks,
S.
ср, 2 дек. 2020 г. в
Hello Maxim,
> I think we should vote for MVCC termination of support.
Honestly, my goal is simple and not so ambitious. I just want to save the
time required for getting TCBot's visa and TC resources.
Thanks,
S.
ср, 2 дек. 2020 г. в 12:54, Maxim Muzafarov :
> Hello Slava,
>
> I think we
Hello once more!
It would also be nice to include
https://issues.apache.org/jira/browse/IGNITE-13770 since it is a nasty
user-visible NPE in public API.
Pls cherry-pick or greenlight me if it's not too late.
Regards.
--
Ilya Kasnacheev
ср, 2 дек. 2020 г. в 14:14, Ilya Kasnacheev :
> Hello
Hello again!
Yaroslav, I have noticed that
https://issues.apache.org/jira/browse/IGNITE-13388 has slipped through the
cracks and was not committed to master properly.
I have committed it to master now, can you please cherry-pick it and add to
scope of 2.9.1 if it's not too late? It's an
Hello!
I have added this account to the Contributors role, you may now assign
tickets to yourself.
Please read
https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
and accustomize with MTCGA bot.
As for the
Hello!
I have scheduled a Run All (Nightly) build for ignite-2.9.1.
I propose to also add https://issues.apache.org/jira/browse/IGNITE-13572 to
scope since it seems to be both impactful and easy to fix.
Regards,
--
Ilya Kasnacheev
ср, 2 дек. 2020 г. в 13:06, Steshin Vladimir :
>
Yaroslav, Hi.
I propose [1] and [2] to pick up into 2.9.1.
[1] is important. It fixes unexpected node failure slipped away from the
Java test. Belatedly found in integration ducktape tests.
[2] just disables soLinger in TcpDiscvoerySPI by default. Suggested in
2.10. But the
+1 to vote for complete MVCC removal.
MVCC is a great feature but we should implement it as a first-class feature and
not «something that pretends to be working»
> 2 дек. 2020 г., в 12:53, Maxim Muzafarov написал(а):
>
> Hello Slava,
>
> I think we should vote for MVCC termination of
Hello Slava,
I think we should vote for MVCC termination of support. If the vote
will be successful than remove it from the source code and disable
MVCC suites.
Only disabling tests from MVCC sounds not good.
On Wed, 2 Dec 2020 at 12:32, Вячеслав Коптилин wrote:
>
> Hello Igniters,
>
> It
Yaroslav,
> can anyone grant me necessary permissions to create a wiki page with release
> info, please?
The edit permissions added to - slava_molochkov
Can you please check?
On Wed, 2 Dec 2020 at 12:19, Yaroslav Molochkov wrote:
>
> Ivan,
>
> thanks, added to the list due to the severity of
Hello Igniters,
It looks like there is no activity related to maintaining or developing the
MVCC feature.
So, I see no reason to waste TeamCity resources. I propose to disable the
corresponding test suites.
This has already been discussed here as well [1].
[1]
Ivan,
thanks, added to the list due to the severity of the issue.
On Wed, Dec 2, 2020 at 12:13 PM Ivan Daschinsky wrote:
> Yaroslav, lets add another bug fix
> https://issues.apache.org/jira/browse/IGNITE-13572
> It's quite small fix, but bug is quite severe.
>
> ср, 2 дек. 2020 г. в 10:48,
Yaroslav, lets add another bug fix
https://issues.apache.org/jira/browse/IGNITE-13572
It's quite small fix, but bug is quite severe.
ср, 2 дек. 2020 г. в 10:48, Yaroslav Molochkov :
> Guys,
>
> can anyone grant me necessary permissions to create a wiki page with
> release info, please?
>
> On
51 matches
Mail list logo
