[jira] [Created] (IGNITE-11652) Remove usage of cache configuration templates from createCache

Igor Belyakov created IGNITE-11652: -- Summary: Remove usage of cache configuration templates from createCache Key: IGNITE-11652 URL: https://issues.apache.org/jira/browse/IGNITE-11652 Project: Ignite

[jira] [Created] (IGNITE-11651) Add cluster (de)activation events documentation

Igor Belyakov created IGNITE-11651: -- Summary: Add cluster (de)activation events documentation Key: IGNITE-11651 URL: https://issues.apache.org/jira/browse/IGNITE-11651 Project: Ignite Issue

Re: Ignite 2.7.5 Release scope

If the failure handler improvements will lower down a number of false-positive cluster shutdowns then I'm for the fix inclusion to the release. As for Java 12, I would put to the next release that we can make shortly after this one. We don't need to wait for months if there are some urgent fixes.

Re: Ignite 2.7.5 Release scope

Denis, I also +1 for python fix. Today is the planned date of code freeze, so today or tomorrow I'll announce it. Only one thing was suggested is the fix for failure handlers. I don't deeply understand the pros and cons, but I'm sure we should courteous enough for wait experienced folks to come

[jira] [Created] (IGNITE-11650) Commutication worker doesn't kick client node after expired idleConnTimeout

Anton Kalashnikov created IGNITE-11650: -- Summary: Commutication worker doesn't kick client node after expired idleConnTimeout Key: IGNITE-11650 URL: https://issues.apache.org/jira/browse/IGNITE-11650

Re: Ignite 2.7.5 Release scope

Yes, the Python example's fix makes sense - that's a usability issue and doesn't affect the core components. In general, I would suggest us to do a code freeze and push other changes to another release. We can't include everything. - Denis On Thu, Mar 28, 2019 at 3:01 AM Ilya Kasnacheev

Re: Introduction

I think that Ignite can be placed in a list of NewSQL databases even though that's not our strongest use case. Ignite is unique as the whole: - Storage (memory + disk - 3rd party or native) - Key/value for simple querying + SQL for advanced calls - Collocated processing (compute grid,

Re: Introduction

Hello! It's weird that you classify Ignite as NewSQL. Anyway, there's a lot of places where you can help. It depends on your skillset. There are a lot of open issues in Ignite JIRA, and there are whole untouched realms of scope. For example, if you are comfortable with .Net development, there

Re: Lightweight version of partitions map exchange

Hi Nikita, Thank you for your work. This is great improvement. I'll take look on it in next couple of days. Could you please run TC and provide MTCGA bot status about this change? чт, 28 мар. 2019 г. в 14:29, Nikita Amelchev : > Hello, Igniters! > > I have implemented lightweight version of

Re: Thin client: transactions support

Hi, I've added permissions to account plehanov.alex Recently Infra integrated Apache LDAP with confluence, so it is possible to login using Apache credentials. Probably we can ask infra if extra permissions to edit pages should be added for committers. Sincerely, Dmitriy Pavlov ср, 27 мар.

Lightweight version of partitions map exchange

Hello, Igniters! I have implemented lightweight version of partitions map exchange for the case when the baseline node leaves topology. [1] If partitions are assigned according to the baseline topology and server node leaves there's no actual need to perform distributed PME. Every cluster will

[jira] [Created] (IGNITE-11649) Java thin client: ReliableChannel is not so reliable

Aleksey Plekhanov created IGNITE-11649: -- Summary: Java thin client: ReliableChannel is not so reliable Key: IGNITE-11649 URL: https://issues.apache.org/jira/browse/IGNITE-11649 Project: Ignite

Re: Ignite 2.7.5 Release scope

Hello! How about adding https://issues.apache.org/jira/browse/IGNITE-11366 which fixes Python's release directory? I have stumbled on this issue personally. Regards, -- Ilya Kasnacheev чт, 28 мар. 2019 г. в 04:19, Roman Shtykh : > Dmitriy, the probability of having nodes down with these

[jira] [Created] (IGNITE-11648) Document SCHEMAS system view

Vladimir Ozerov created IGNITE-11648: Summary: Document SCHEMAS system view Key: IGNITE-11648 URL: https://issues.apache.org/jira/browse/IGNITE-11648 Project: Ignite Issue Type: Task

Re: [ML][DISCUSSION] The future of Vectorizer

Yep, I definitely agree with you. Moreover, such improvement should reduce parallel hierarchies in trainers and preprocessors, from this point of view preprocessor will be equal to a trainer. In my opinion, this improvement is very important for ml module because it can give a flexible hierarchy

Re: [ML][DISCUSSION] The future of Vectorizer

It's a brilliant idea, I agree! -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-11647) [ML] ML Vectors should work with all Serializable objects besides double

Alexey Platonov created IGNITE-11647: Summary: [ML] ML Vectors should work with all Serializable objects besides double Key: IGNITE-11647 URL: https://issues.apache.org/jira/browse/IGNITE-11647

[ML][DISCUSSION] The future of Vectorizer

Hi, Igniters The new functionality of building Vectors was merged to Apache Ignite in the next commit This new functionality brings to Ignite ML the new approach of building vectors. But in my opinion the

[jira] [Created] (IGNITE-11646) failed H2IndexesSystemViewTest.testIndexesView

Yury Gerzhedovich created IGNITE-11646: -- Summary: failed H2IndexesSystemViewTest.testIndexesView Key: IGNITE-11646 URL: https://issues.apache.org/jira/browse/IGNITE-11646 Project: Ignite

[jira] [Created] (IGNITE-11645) Web console: failing signup e2e test

Ilya Borisov created IGNITE-11645: - Summary: Web console: failing signup e2e test Key: IGNITE-11645 URL: https://issues.apache.org/jira/browse/IGNITE-11645 Project: Ignite Issue Type: Test