Removal of "default" cache from REST APIs

Hi guys, Most of the cache APIs are trying to use "default" cache when cacheName is not provided. This is pointless, because we don't have such cache by default. I would like to change that and just return "Failed to find mandatory parameter in request" error if name is absent. Please tell if

Re: Choosing historical rebalance heuristics

Ivan, I agree with a combined approach: threshold for small partitions and count of update for partition that outgrew it. This helps to avoid partitions that update not frequently. Reading of a big WAL piece (more than 100Gb) it can happen, when a client configured it intentionally. There are no

Re: Continuous Queries with several remote filter on the same cache

Hi Roman, Apologize for the late reply. Could you please clarify why it's useful to the threads count parameter? How are you planning to use it? - Denis On Tue, Jul 7, 2020 at 5:25 AM wrote: > Hi Denis, > > What do you think about some improvements in @IgniteAsyncCallback > regarding

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

Ivan, Looks like master is broken after IGNITE-13246 (but everything is ok in 2.9 branch) ср, 15 июл. 2020 г. в 18:54, Alex Plehanov : > Zhenya, Ivan, > > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch. > Thank you. > > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov : > >>

Re: [RESULT][VOTE] Stop Maintenance of Ignite Web Console

Hello! I think that we indeed should version this change, i.e., only remove mentions of Web Console in the version where it's already in the attic. Regards, -- Ilya Kasnacheev ср, 15 июл. 2020 г. в 17:17, Denis Magda : > We should remove the docs and all the mentioning from the website once

Re: [RESULT][VOTE] Stop Maintenance of Ignite Web Console

We should remove the docs and all the mentioning from the website once this ticket is complete: https://issues.apache.org/jira/plugins/servlet/mobile#issue/IGNITE-13038 Alex Kuznetsov, are you planning to finish the task in Ignite 2.9 timeframe? Denis On Wednesday, July 15, 2020, Ilya

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

Zhenya, Ivan, I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch. Thank you. ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov : > Guys, > > can you please backport https://issues.apache.org/jira/browse/IGNITE-13246 > to ignite-2.9? Me and Alexey Kuznetsov really want these new

A few small pull requests

Hi, I have a few small quality-of-life pull requests languishing in the backlog. Can anyone take a look or suggest what else I need to do to progress them? IGNITE-12192 Allow ignitevisorcmd to quit when pressing ^D IGNITE-12182 ExecutorService

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

Guys, can you please backport https://issues.apache.org/jira/browse/IGNITE-13246 to ignite-2.9? Me and Alexey Kuznetsov really want these new events in release. This time I prepared PR with resolved conflicts: https://github.com/apache/ignite/pull/8042 Thank you! вт, 14 июл. 2020 г. в 19:39,

Re: [RESULT][VOTE] Stop Maintenance of Ignite Web Console

Hello! Well, why? I think we can keep Web Console docs for now, just add some note that it is discontinued. We can also put deprecation notice here. Regards, -- Ilya Kasnacheev пн, 13 июл. 2020 г. в 19:46, Dmitriy Pavlov : > Hi Folks, > > I've just found our doc still point and recommend

Re: [DISCUSSION] Ignite integration testing framework.

Anton, Nikolay, I want to share some more findings about ducktests I've stubmled upon during porting them to Tiden. First problem was that GridGain Tiden-based tests by default use real production-like configuration for Ignite nodes, notably: - persitence enabled - ~120 caches in ~40

Re: Choosing historical rebalance heuristics

Hi Vladislav, Thanks for raising this topic. Currently present IGNITE_PDS_WAL_REBALANCE_THRESHOLD (default is 500_000) is controversial. Assuming that the default number of partitions is 1024, cache should contain a really huge amount of data in order to make WAL delta rebalancing possible. In

Re: [DISCUSSION] Ignite integration testing framework.

Anton, I've prepared a PoC of running Tiden in dockerized environment. The code is in fork of your repo at https://github.com/mshonichev/ignite.git, branch 'ignite-ducktape', module 'integration-tests. Steps to run PoC are as follows: ``` $ mkdir -p $HOME/tiden_poc $ cd $HOME/tiden_poc $

[jira] [Created] (IGNITE-13261) Using transactions or continuous queries inside the ignite sandbox can throw an AccessControlException

Denis Garus created IGNITE-13261: Summary: Using transactions or continuous queries inside the ignite sandbox can throw an AccessControlException Key: IGNITE-13261 URL:

Re: IEP-50 Thin Client Continuous Queries

Alex, You are correct, OP_RESOURCE_CLOSE is enough. Removed the extra op. > If client closes CQ it doesn't want to receive any new events. Why can't we > just ignore events for this CQ after that moment? I don't think that our protocol should involve ignoring messages. If the client stops the

New component: control.sh

Hello! I have added a new component control.sh to IGNITE project. Kindly ask you to put all of your control.sh tickets under shis new component. Regards, -- Ilya Kasnacheev

[jira] [Created] (IGNITE-13260) Improve javadoc documentation for FilePageStore abstraction.

Sergey Chugunov created IGNITE-13260: Summary: Improve javadoc documentation for FilePageStore abstraction. Key: IGNITE-13260 URL: https://issues.apache.org/jira/browse/IGNITE-13260 Project:

Re: IEP-50 Thin Client Continuous Queries

Pavel, > OP_QUERY_CONTINUOUS_END_NOTIFICATION is another client -> server message I think you mean "server -> client" here. But I still didn't get why do we need it. I've briefly looked to the POC implementation and, as far as I understand, OP_QUERY_CONTINUOUS_END_NOTIFICATION can be sent only

Re: Proposal of new event QUERY_EXECUTION_EVENT

Hi Denis, thanks for the answer! We already checked EVT_CACHE_QUERY_EXECUTED and found that it works only in cases: 1. Scan queries and Select queries (common pattern is access to cache data); 2. This event triggers only if query execution succeeds, in case of failure while execution this event