[jira] [Created] (IGNITE-9968) Able to filter backup cache events

Roman Bastanov created IGNITE-9968: -- Summary: Able to filter backup cache events Key: IGNITE-9968 URL: https://issues.apache.org/jira/browse/IGNITE-9968 Project: Ignite Issue Type:

[GitHub] ignite pull request #5045: IGNITE-9960

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/5045 ---

Re: Apache Ignite 2.7. Last Mile

Hello, Igniters. We have 7 tickets mapped to 2.7 today. Igov Seliverstov - IGNITE-9892 - MVCC: Exchange hangs on mvcc coordinator fail Igor Seliverstov - IGNITE-9911 - CacheMvccSelectForUpdateQueryAbstractTest#testSelectForUpdateAfterAbortedTx periodically hangs Roman Kondakov-

Re: Apache Ignite 2.7. Last Mile

Igniters, There are still tickets in the scope as we continue finding new issues during QA. I propose the following plan: if there are still opened issues by Friday, then shift vote date for 1 week, to 2nd November. This is needed to ensure that product quality is sufficient. But if the backlog

Re: [MTCGA]: new failures in builds [2123440] needs to be handled

Hello, Are there any updates? The build constantly fails with `Execution timeout` in the master branch since October 20. The problem commit supposed to be related to the [2] issue and I think the probable `IgniteSqlSplitterSelfTest#testPushDown` test fails with excpetion: class

Re: [MTCGA]: new failures in builds [2123440] needs to be handled

Hi all, We are working on the fix, it should be merged to master asap. вт, 23 окт. 2018 г. в 11:18, Maxim Muzafarov : > Hello, > > Are there any updates? > The build constantly fails with `Execution timeout` in the master branch > since October 20. > > The problem commit supposed to be related

[GitHub] ignite pull request #4911: IGNITE-9719 Extra rebalanceThreadPoolSize check o...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4911 ---

Re: [MTCGA]: new failures in builds [2142325] needs to be handled

This can be ignored. I removed the test because it measured performance and we should run performance tests in a verified environment. вт, 23 окт. 2018 г. в 5:16, : > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your

Re: Abbreviation code-style requirement.

Igniters, I think it's easy to disable the code style abbreviation plugin option by switching off the checkbox on - File | Settings | Inspections | Apache Ignite | Incorrect Java abbreviation usage. +1 to make abbreviation not mandatory, but I'd like to keep it for common variable names like

[GitHub] SomeFire commented on a change in pull request #40: IGNITE-9939 BuildObserver UNKNOWN build state handling added

SomeFire commented on a change in pull request #40: IGNITE-9939 BuildObserver UNKNOWN build state handling added URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r227284241 ## File path:

[GitHub] ignite pull request #5043: IGNITE-9951: thin php: Date data type cut nanos

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5043 ---

[GitHub] ignite pull request #5055: IGNITE-9884 Some tests are incorrectly muted

GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/5055 IGNITE-9884 Some tests are incorrectly muted You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9884

Re: Apache Ignite 2.7. Last Mile

Hello, Dmitriy. I'm OK with including this patch to 2.7. Can you ensure it completely fix the issue? I left comment in ticket. https://issues.apache.org/jira/browse/IGNITE-9854?focusedCommentId=16660516=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16660516 В Вт,

[GitHub] ignite pull request #5018: IGNITE-9663: Data node failure can cause TX hangi...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5018 ---

[GitHub] ignite pull request #5035: IGNITE-9911

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5035 ---

[jira] [Created] (IGNITE-9970) Add ability to set nodeId for VisorIdleVerifyDumpTask executed from ./control.sh --host HOST --cache idle_verify

Pavel Voronkin created IGNITE-9970: -- Summary: Add ability to set nodeId for VisorIdleVerifyDumpTask executed from ./control.sh --host HOST --cache idle_verify Key: IGNITE-9970 URL:

Re: PHP thin client

Thanks, finally fixes are merged I have new question I'm trying to put Enum object and get it back, but catch exception that enum is null code with output - https://gist.github.com/pilshchikov/b89c6e25f29da88ac03caa42231a02bc Also can't find Enum data type test in sources I trying to use Enum

Re: Abbreviation code-style requirement.

Hi Ivan if by conflict we mean arguing and fighting it is definitely should be avoided, it never helps the community. But if we mean different opinions on details (variable namings, method structure, etc), such different views are unavoidable and I find it is perfectly ok that people with

[jira] [Created] (IGNITE-9974) Drop Hadoop assemblies

Peter Ivanov created IGNITE-9974: Summary: Drop Hadoop assemblies Key: IGNITE-9974 URL: https://issues.apache.org/jira/browse/IGNITE-9974 Project: Ignite Issue Type: Improvement Affects

[jira] [Created] (IGNITE-9975) Possible data loss during starting of the nodes with empty pds

Andrey Aleksandrov created IGNITE-9975: -- Summary: Possible data loss during starting of the nodes with empty pds Key: IGNITE-9975 URL: https://issues.apache.org/jira/browse/IGNITE-9975 Project:

[GitHub] ignite pull request #4857: IGNITE-9632 implementation

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4857 ---

[GitHub] ignite pull request #5058: IGNITE-8867

GitHub user artemmalykh opened a pull request: https://github.com/apache/ignite/pull/5058 IGNITE-8867 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8867 Alternatively you can review and apply

Re: NodeJS thin client: full API

Alexey, I'm trying to get Enum from cache which placed by different thin client and find that i can't get it, only exception And more when im trying to get Enum which is placed by nodejs client i also can't do it, have same exception code and output -

[GitHub] SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added

SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added URL: https://github.com/apache/ignite-teamcity-bot/pull/39#discussion_r227305678 ## File path:

[GitHub] SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added

SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added URL: https://github.com/apache/ignite-teamcity-bot/pull/39#discussion_r227300712 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java

[GitHub] SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added

SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added URL: https://github.com/apache/ignite-teamcity-bot/pull/39#discussion_r227304277 ## File path:

[GitHub] SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added

SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added URL: https://github.com/apache/ignite-teamcity-bot/pull/39#discussion_r227302027 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java

[GitHub] SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added

SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added URL: https://github.com/apache/ignite-teamcity-bot/pull/39#discussion_r227305508 ## File path:

[GitHub] SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added

SomeFire commented on a change in pull request #39: IGNITE-9901 Persistent queue for visas added URL: https://github.com/apache/ignite-teamcity-bot/pull/39#discussion_r227298976 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java

[jira] [Created] (IGNITE-9973) MVCC: Tx recovery with continuous query.

Roman Kondakov created IGNITE-9973: -- Summary: MVCC: Tx recovery with continuous query. Key: IGNITE-9973 URL: https://issues.apache.org/jira/browse/IGNITE-9973 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-9976) [Test Failed] BinaryMetadataUpdatesFlowTest.testFlowNoConflicts flaky fails on TC.

Pavel Pereslegin created IGNITE-9976: Summary: [Test Failed] BinaryMetadataUpdatesFlowTest.testFlowNoConflicts flaky fails on TC. Key: IGNITE-9976 URL: https://issues.apache.org/jira/browse/IGNITE-9976

[GitHub] ignite pull request #5056: IGNITE-9976

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/5056 IGNITE-9976 You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-9976 Alternatively you can review and apply these changes as

[GitHub] ignite pull request #5057: IGNITE-9928

GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/5057 IGNITE-9928 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9928 Alternatively you can review and apply

[GitHub] ignite pull request #5036: IGNITE-9884 Some tests are incorrectly muted

Github user oignatenko closed the pull request at: https://github.com/apache/ignite/pull/5036 ---

[jira] [Created] (IGNITE-9971) MLPTrainer example failures

Sergey Kozlov created IGNITE-9971: - Summary: MLPTrainer example failures Key: IGNITE-9971 URL: https://issues.apache.org/jira/browse/IGNITE-9971 Project: Ignite Issue Type: Bug Affects

[GitHub] ignite pull request #4893: IGNITE-8879 Correct restoring of metastorage and ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4893 ---

Re: Apache Ignite 2.7. Last Mile

Nikolay, I have an issue which I want to include in 2.7 release, https://issues.apache.org/jira/browse/IGNITE-9854 It is a very small fix but very important, it protects us from NPE in some race scenario. Changes already in master, but the issue still not resolve, need your approval for

[jira] [Created] (IGNITE-9972) Deleted entries remain in local partition internal map

Anton Kurbanov created IGNITE-9972: -- Summary: Deleted entries remain in local partition internal map Key: IGNITE-9972 URL: https://issues.apache.org/jira/browse/IGNITE-9972 Project: Ignite

Re: PHP thin client

And more, If im use ->setValueType(ObjectType::ENUM) during $cache->get(1); it throwing exception that client can't convert BINARY_ENUM to ENUM вт, 23 окт. 2018 г. в 15:57, Stepan Pilschikov : > Thanks, finally fixes are merged > > I have new question > > I'm trying to put Enum object and get

[jira] [Created] (IGNITE-9978) [ML] Implement Compound Naive Bayes classifier

Alexey Platonov created IGNITE-9978: --- Summary: [ML] Implement Compound Naive Bayes classifier Key: IGNITE-9978 URL: https://issues.apache.org/jira/browse/IGNITE-9978 Project: Ignite Issue

[jira] [Created] (IGNITE-9979) [ML] Implement Naive Bayes classifier over Discrete Disctribution

Alexey Platonov created IGNITE-9979: --- Summary: [ML] Implement Naive Bayes classifier over Discrete Disctribution Key: IGNITE-9979 URL: https://issues.apache.org/jira/browse/IGNITE-9979 Project:

[jira] [Created] (IGNITE-9980) Modify ./control.sh --cache idle_verify --dump to print only persistante cache or add flag --persistentOnly

ARomantsov created IGNITE-9980: -- Summary: Modify ./control.sh --cache idle_verify --dump to print only persistante cache or add flag --persistentOnly Key: IGNITE-9980 URL:

Re: Code inspection

Igniters, I've fixed some issues according to the inspections.xml configuration: - `Missorted modifiers`; - `'size() == 0' replaceable with 'isEmpty()'`; - `Add missing @Override annotation`; These one have `In progress` state: - `Fix unused imports`; - `Remove unnecessary @SuppressWarnings

Re: Code inspection

Hello, Maxim. +1 from me. I vote to enable static inspections for the Ignite codebase. Thank you for that contributions! В Вт, 23/10/2018 в 19:09 +0300, Maxim Muzafarov пишет: > Igniters, > > I've fixed some issues according to the inspections.xml configuration: > - `Missorted modifiers`; >

[jira] [Created] (IGNITE-9981) Web Console: We need to update the counters on the tables.

Vica Abramova created IGNITE-9981: - Summary: Web Console: We need to update the counters on the tables. Key: IGNITE-9981 URL: https://issues.apache.org/jira/browse/IGNITE-9981 Project: Ignite

Re: [MTCGA]: new failures in builds [2123440] needs to be handled

All, We had to revert the commit because the fix appeared to be more complex than we expected. Tests should be ok now. вт, 23 окт. 2018 г. в 11:20, Alexey Goncharuk : > Hi all, > > We are working on the fix, it should be merged to master asap. > > вт, 23 окт. 2018 г. в 11:18, Maxim Muzafarov :

[GitHub] ignite pull request #4869: IGNITE-9282 Add Gaussian Naive Bayes Classifier

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4869 ---

[GitHub] ignite pull request #4521: GG-13254 Snapshots: Only Full snapshot should be ...

Github user a-polyakov closed the pull request at: https://github.com/apache/ignite/pull/4521 ---

Re: [DISCUSSION] TDE. Phase-2. Master key rotation.

Nikolay, I have some comments. 1) Master key setup and removal is a responsibility of system administrator. No matter how he will set a new master key or remove an old. The only need it to have both keys, new and old, installed before starting the rotation process. 2) Master Key rotation is a

[jira] [Created] (IGNITE-9977) Design & implement integration Ignite with SSL/TLS Certification Authority Center

Yuriy Sergeev created IGNITE-9977: - Summary: Design & implement integration Ignite with SSL/TLS Certification Authority Center Key: IGNITE-9977 URL: https://issues.apache.org/jira/browse/IGNITE-9977

Re: [DISCUSSION] TDE. Phase-2. Master key rotation.

Hello, Anton. Thank you for your very usefull feedback! I accept your proposals. Seems it makes this feature more robust and clear. Will update design in confluence in a couple of hours. В Вт, 23/10/2018 в 19:18 +0300, Anton Vinogradov пишет: > Nikolay, > > I have some comments. > > 1)

Pre-touch for Ignite off-heap memory

Hi *Igniters*, Some time ago I've raised a suggestion for product improvement https://issues.apache.org/jira/browse/IGNITE-9112 . It's all about off-heap memory allocation. Current implementation can have some improvements for failure critical

[GitHub] ignite pull request #4735: Cache 2 stab experiment

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4735 ---

Re: [DISCUSSION] Spark Data Frame through Thin Client

Nikolay, Please see my comments below. Actually, I haven't made most of the assumptions that you mentioned, and I generally agree with you. What I don't agree with is that replacing thick client with thin client is a way to fix usability issues. Thin client is not going to be issue-free either,

Re: Continuous query deployment

Guys, Correct me if I am wrong, but to my knowledge peer class loading doesn't *really* work for CQs regardless of autoUnsubscribe flag. The issue is that filter is distributed via discovery messages when new node joins, but discovery uses JDK marshaller that is not aware of p2p loading. So

Re: Pre-touch for Ignite off-heap memory

Alex, Correct me if I'm wrong, but even if an OS runs out of physical memory (X GB in total) an Ignite node process still can request the X GB from virtual memory. Yes, virtual memory can involve swapping and disk to satisfy your request but this shouldn't be a reason of the OOM. Shouldn't OOM

[MTCGA]: new failures in builds [2151099] needs to be handled

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