Re: No commits to Ignite website: migration from SVN to Git is in progress

Hi Denis, Thank you, yes I will use the GitHub built-in capabilities. Regards, Saikat On Mon, Apr 20, 2020 at 1:01 PM Denis Magda wrote: > Saikat, now I see your point, thanks for breaking it down. As of now, there > is no need for those scripts, at least, for the website repository. It's >

[jira] [Created] (IGNITE-12930) DistributedProcess fails node if unable to send single message to coordinator

Maxim Muzafarov created IGNITE-12930: Summary: DistributedProcess fails node if unable to send single message to coordinator Key: IGNITE-12930 URL: https://issues.apache.org/jira/browse/IGNITE-12930

[jira] [Created] (IGNITE-12929) Incorrect setClientMode calls instead of startClientGrid

Maxim Muzafarov created IGNITE-12929: Summary: Incorrect setClientMode calls instead of startClientGrid Key: IGNITE-12929 URL: https://issues.apache.org/jira/browse/IGNITE-12929 Project: Ignite

Re: Apache Ignite 2.8.0 spring services configuration null fields

Thank you Vyacheslav, Case closed. It works fine in 2.8.0 if service extended Test class implements Serializable. /Keep up good work "Igniters"/ - Regards Cristian Gheorghe Florescu -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Apache Ignite 2.8.0 spring services configuration null fields

Now I see. Your parent class (called Test in your example) *should implement 'Serializable' interface*, this will help for your case. We changed default marshaller for services in 2.8, because they have to be 'Serializable' according to API. 'JdkMarshaller' is default marshaller for services

Re: Moving python, php and node.js in separate repos and release cycles

-1 - Ignite is a single Apache project, it follows Apache release guidelines, with voting and so on. Not sure how are we going to follow that with a separate repo. - Thin client features are often tied to server-side changes > What about dotnet and cpp thin clients? Those reuse some code with

Re: Apache Ignite 2.8.0 spring services configuration null fields

Thank you Vyacheslav, Still reproduced in 2.8.0 and in 2.7.6 is not. Please take a look carefully at the gist example code. public class TestServiceImpl extends *Test* implements Service,TestService - Regards Cristian Gheorghe Florescu -- Sent from:

[jira] [Created] (IGNITE-12928) CacheMetricsMXBean does not provide proper descriptions for rebalancing attributes

Maria Makedonskaya created IGNITE-12928: --- Summary: CacheMetricsMXBean does not provide proper descriptions for rebalancing attributes Key: IGNITE-12928 URL:

Re: Apache Ignite 2.8.0 spring services configuration null fields

Sorry, wrong link in previous email. Here is an example: https://github.com/apache/ignite/blob/master/modules/spring/src/test/java/org/apache/ignite/spring/injection/spring-bean.xml On Tue, Apr 21, 2020 at 8:02 PM Vyacheslav Daradur wrote: > Hi, I looked through your example and can't

Re: Apache Ignite 2.8.0 spring services configuration null fields

Hi, I looked through your example and can't reproduce it. Properties injection works fine. I suppose that you have run Ignite out of Spring context. Please check your Spring context configuration file once again. Here is an example:

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Hello, Nikolay. This has been fixed by increasing the test timeout in IGNITE-12683 [1][2]. [1] https://issues.apache.org/jira/browse/IGNITE-12683 [2] https://github.com/apache/ignite/commit/bf394a77e1de6432e493eb2818243a82b577f11e вт, 21 апр. 2020 г. в 18:28, Nikolay Izhikov : > > Hello,

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Nikolay, @Peter Ivanov or @Dmitriy Pavlov should be able to help with the TeamCity Bot setup. Let's put all the knowledge on paper once you figure it out. - Denis On Tue, Apr 21, 2020 at 2:53 AM Nikolay Izhikov wrote: > Igniters. > > Can someone from Grid Gain help me with setup TC bot to

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Hello, Igniters. While cherry-picking to 2.8.1 I found flaky test regarding BPlusTree [1], [2] All failures of this tests relates to PR’s based on 2.8. It seems we hav fix in master but doesn’t have it in 2.8 and 2.8.1 Can someone suggest, what commit fixes this tests? [1]

[jira] [Created] (IGNITE-12927) The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky

Amelchev Nikita created IGNITE-12927: Summary: The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky Key: IGNITE-12927 URL: https://issues.apache.org/jira/browse/IGNITE-12927

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Sure, here's PR with 3 cherry-picked commits that I mentioned: https://github.com/apache/ignite/pull/7708 вт, 21 апр. 2020 г. в 17:17, Nikolay Izhikov : > OK then, let’s include it in the 2.8.1 > > Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain > cherry-pick for all

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

OK then, let’s include it in the 2.8.1 Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain cherry-pick for all required commits? > 21 апр. 2020 г., в 17:01, Andrey Gura написал(а): > > Hi > >> IGNITE-12735 - Metric exporter implementation could lead to >>

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Hi > IGNITE-12735 - Metric exporter implementation could lead to > NullPointerException from gauge which invoke communication > IGNITE-12568 - MessageFactory implementations refactoring > Personally, I’m against any refactoring improvements in bug fix release. > So, I propose to exclude

Re: Moving python, php and node.js in separate repos and release cycles

What about dotnet and cpp thin clients? > 21 апр. 2020 г., в 16:19, Dmitriy Pavlov написал(а): > > +1 since > - Simpler release may allow us to release more often > - Often releases - users will get updates faster, more chances to grow and > keep our user base > - Faster updates and easy to get

Re: Moving python, php and node.js in separate repos and release cycles

+1 since - Simpler release may allow us to release more often - Often releases - users will get updates faster, more chances to grow and keep our user base - Faster updates and easy to get next update may have positive effect on community growth. Since newcomer may want to fix a bug and later use

Why OPTIMIZE_REUSE_RESULT is set to 0 explicitly in o.a.i.i.p.query.h2.ConnectionManager#DEFAULT_DB_OPTIONS

Hello folks. Recently I trying to investigate why when the query, i.e. «SELECT * FROM T1 WHERE ID IN (SELECT T1_ID FROM T2), is executed locally, subquery evaluated, even if result is the same. I noticed, that in mentioned in subj (.ConnectionManager#DEFAULT_DB_OPTIONS), parameter

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Taras, Great news! Thank you! Let me know, when you got the visa. > 21 апр. 2020 г., в 14:02, Taras Ledkov написал(а): > > Hi, > > Nikolay, i've created PR [1] that contains the SQL-related tickets to port > into 2.8.1: > - IGNITE-12790 Introduce distributed SQL configuration and ability to

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Hi, Nikolay, i've created PR [1] that contains the SQL-related tickets to port into 2.8.1: - IGNITE-12790 Introduce distributed SQL configuration and ability to disable SQL functions. - IGNITE-12887 Fix handle type mismatch exception on compare values while traversing index tree. -

[jira] [Created] (IGNITE-12926) [ignite-extensions] build failed

Nikolay Izhikov created IGNITE-12926: Summary: [ignite-extensions] build failed Key: IGNITE-12926 URL: https://issues.apache.org/jira/browse/IGNITE-12926 Project: Ignite Issue Type: Test

Re: Moving python, php and node.js in separate repos and release cycles

Agree with these non-JVM languages. Especially for Python:) вт, 21 апр. 2020 г. в 12:58, Igor Sapego : > Guys, > > It was discussed on the dev list a few times that it would be a good > idea to move Python, Node.js and PHP thin clients to separate repos > and separate release cycles. > > In

Re: [jira] [评论] (IGNITE-12852) Comma in field is not supported by COPY command

Hi community, if someone can help to merge this patch into repo(2.8.1)? 在 2020/4/17 下午4:52, Roman Kondakov (Jira) 写道: Message Title Roman Kondakov *在故障 IGNITE-12852

Moving python, php and node.js in separate repos and release cycles

Guys, It was discussed on the dev list a few times that it would be a good idea to move Python, Node.js and PHP thin clients to separate repos and separate release cycles. In short there are several arguments for that: 1. There are no dependencies on the core functionality so there is simply no

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Igniters. Can someone from Grid Gain help me with setup TC bot to monitor ignite-2.8.1 branch? > 21 апр. 2020 г., в 11:11, Nikolay Izhikov написал(а): > >> I've cherry-picked IGNITE-12734 to 2.8.1 branch. > > > Thanks! > >> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI

[jira] [Created] (IGNITE-12925) Flaky test SystemViewSelfTest.testContinuousQuery.

Mikhail Petrov created IGNITE-12925: --- Summary: Flaky test SystemViewSelfTest.testContinuousQuery. Key: IGNITE-12925 URL: https://issues.apache.org/jira/browse/IGNITE-12925 Project: Ignite

[jira] [Created] (IGNITE-12924) [ignite-extensions] Unused import breaks checkstyle

Nikolay Izhikov created IGNITE-12924: Summary: [ignite-extensions] Unused import breaks checkstyle Key: IGNITE-12924 URL: https://issues.apache.org/jira/browse/IGNITE-12924 Project: Ignite

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

> I've cherry-picked IGNITE-12734 to 2.8.1 branch. Thanks! > considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics >> improvement" - it depends >> on https://issues.apache.org/jira/browse/IGNITE-12735 and >> https://issues.apache.org/jira/browse/IGNITE-12568, >> both were

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Nikolay, I've cherry-picked IGNITE-12734 to 2.8.1 branch. вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov : > Hello, Igniters, > > considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics > improvement" - it depends > on https://issues.apache.org/jira/browse/IGNITE-12735 and >

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Hello, Igniters, considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement" - it depends on https://issues.apache.org/jira/browse/IGNITE-12735 and https://issues.apache.org/jira/browse/IGNITE-12568, both were targeted to 2.9, but this has to be changed probably. There

Re: [DISCUSSION] Hot cache backup

Maxim, I've left my comments in the PR. пн, 20 апр. 2020 г. в 12:52, Maxim Muzafarov : > Alex P, > Thank you for the great sophisticated review. > > > Alexey G, > Will you take a look at my changes[1]? > The fresh TC.Bot visa attached. > > > [1]