Re: Ignite stops working suddenly during dev

2019-06-13 Thread Denis Magda
Alright, the ticket is ready for contribution: https://issues.apache.org/jira/browse/IGNITE-11919 -- Denis Magda On Thu, Jun 13, 2019 at 2:50 PM Denis Magda wrote: > Those are details and I can't think of a generic and crystal clear message > that covers them. Plus, don't think we should do th

[jira] [Created] (IGNITE-11919) Change message format for incompatible fields' types changes

2019-06-13 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-11919: Summary: Change message format for incompatible fields' types changes Key: IGNITE-11919 URL: https://issues.apache.org/jira/browse/IGNITE-11919 Project: Ignite

Re: Ignite stops working suddenly during dev

2019-06-13 Thread Denis Magda
Those are details and I can't think of a generic and crystal clear message that covers them. Plus, don't think we should do this as long as the generic solution will solve the problem. - Denis On Thu, Jun 13, 2019 at 10:48 AM Mikhail Cherkasov wrote: > *"ERROR: Type 'Person' has a different/in

[jira] [Created] (IGNITE-11918) extend test coverage for KILL QUERY

2019-06-13 Thread Pavel Kuznetsov (JIRA)
Pavel Kuznetsov created IGNITE-11918: Summary: extend test coverage for KILL QUERY Key: IGNITE-11918 URL: https://issues.apache.org/jira/browse/IGNITE-11918 Project: Ignite Issue Type: Te

Re: Ignite stops working suddenly during dev

2019-06-13 Thread Mikhail Cherkasov
*"ERROR: Type 'Person' has a different/incorrect type for field 'salary'. Expected 'double' but 'string' was provided. Field type's modification is unsupported, clean {root_path}/marshaller directory if the type change is required."* it still sounds like a hack and it's not clear if it should be d

[jira] [Created] (IGNITE-11917) Row count [select count(*) from table] not matching with the actual row count present in the table

2019-06-13 Thread shivakumar (JIRA)
shivakumar created IGNITE-11917: --- Summary: Row count [select count(*) from table] not matching with the actual row count present in the table Key: IGNITE-11917 URL: https://issues.apache.org/jira/browse/IGNITE-1191

Re: [Code Style Check] TC issues in master

2019-06-13 Thread Maxim Muzafarov
Folks, Thank you for not being indifferent to the topic of coding style. I've temporary excluded `scala` related modules from the [Check Code Style] suite configuration (checkstyle is not working for the `scala` source code) until we come to an agreement to a way to solve the problem mentioned ab

[jira] [Created] (IGNITE-11916) reorder fields for GridQueryKillResponse and GridQueryKillRequest

2019-06-13 Thread Pavel Kuznetsov (JIRA)
Pavel Kuznetsov created IGNITE-11916: Summary: reorder fields for GridQueryKillResponse and GridQueryKillRequest Key: IGNITE-11916 URL: https://issues.apache.org/jira/browse/IGNITE-11916 Project:

[jira] [Created] (IGNITE-11915) Document all ways to download Ignite in YARN

2019-06-13 Thread Ilya Kasnacheev (JIRA)
Ilya Kasnacheev created IGNITE-11915: Summary: Document all ways to download Ignite in YARN Key: IGNITE-11915 URL: https://issues.apache.org/jira/browse/IGNITE-11915 Project: Ignite Issue

Re: [Code Style Check] TC issues in master

2019-06-13 Thread Павлухин Иван
Petr, Nikolay, Running some kind of smoke test might be a good idea. But I think it should be discussed separately in another thread. чт, 13 июн. 2019 г. в 11:43, Petr Ivanov : > > I do not know, some basic tests (running single instance of Ignite, > activation, simple cluster topology, etc.) >

[jira] [Created] (IGNITE-11914) Failures to deserialize discovery data should be handled by a failure handler

2019-06-13 Thread Denis Mekhanikov (JIRA)
Denis Mekhanikov created IGNITE-11914: - Summary: Failures to deserialize discovery data should be handled by a failure handler Key: IGNITE-11914 URL: https://issues.apache.org/jira/browse/IGNITE-11914

[jira] [Created] (IGNITE-11913) Incorrect formatting of idle_verify output

2019-06-13 Thread Denis Chudov (JIRA)
Denis Chudov created IGNITE-11913: - Summary: Incorrect formatting of idle_verify output Key: IGNITE-11913 URL: https://issues.apache.org/jira/browse/IGNITE-11913 Project: Ignite Issue Type: B

Re: Signing off Ignite for export beyond the U.S.

2019-06-13 Thread Igor Sapego
Denis, C++ thin client and ODBC use OpenSSL to establish secure connection with the cluster and do not contain any crypto algorithms in their own code. Best Regards, Igor On Thu, Jun 13, 2019 at 12:56 AM Alexey Kosenchuk < alexey.kosenc...@nobitlost.com> wrote: > Hi Denis, > > Info about Pytho

[jira] [Created] (IGNITE-11912) [IEP-35] Research possibility to optimize MetricRegistry

2019-06-13 Thread Nikolay Izhikov (JIRA)
Nikolay Izhikov created IGNITE-11912: Summary: [IEP-35] Research possibility to optimize MetricRegistry Key: IGNITE-11912 URL: https://issues.apache.org/jira/browse/IGNITE-11912 Project: Ignite

Re: [Code Style Check] TC issues in master

2019-06-13 Thread Petr Ivanov
I do not know, some basic tests (running single instance of Ignite, activation, simple cluster topology, etc.) It seems that it is more critical than stylecheck, that can be fixed in several lines of code, but will steal a day (night) of tests. > On 13 Jun 2019, at 11:42, Nikolay Izhikov wrote

Re: [Code Style Check] TC issues in master

2019-06-13 Thread Nikolay Izhikov
Hello, Petr. I think we should be specific here. For me: "code style" fail should be equal to "compilation fail". Can you clarify, what fundamental tests you are written about? В Чт, 13/06/2019 в 11:26 +0300, Petr Ivanov пишет: > How about including basic set of tests (sanity checks) into ~Build

Re: [Code Style Check] TC issues in master

2019-06-13 Thread Petr Ivanov
How about including basic set of tests (sanity checks) into ~Build Apache Ignite~? Or may be we can go even further and use cascade system of tests — run them group by group, stopping the whole run if more fundamental tests are failing? > On 12 Jun 2019, at 21:54, Nikolay Izhikov wrote: > > +