Re: [Announce] New committer: Iurii Gerzhedovich

Thank you everyone, I'm very pleased! ср, 14 февр. 2024 г. в 17:28, Pavel Pereslegin : > Congratulations, Iurii! > > ср, 14 февр. 2024 г. в 09:29, Pavel Tupitsyn : > > > > Congratulations Iurii! > > > > On Wed, Feb 14, 2024 at 8:17 AM Roman Puchkovskiy < > > roman.puchkovs...@gmail.com> wrote: >

Re: [VOTE] Release Apache Ignite 3.0.0-beta1 RC2

+1 вт, 15 нояб. 2022 г. в 21:11, Vladislav Pyatkov : > +1 > > On Tue, Nov 15, 2022 at 3:35 PM Denis C wrote: > > > > +1 > > > > вт, 15 нояб. 2022 г. в 13:33, Alexander Lapin : > > > > > +1 > > > > > > вт, 15 нояб. 2022 г. в 08:48, Pavel Tupitsyn : > > > > > > > +1 (binding) > > > > > > > > On Mo

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

Hi Igniters, I would like to add last one bugfix to the beta1: https://issues.apache.org/jira/browse/IGNITE-18090 It will be ready in a few hours. чт, 3 нояб. 2022 г. в 19:28, Alexander Lapin : > Hi Igniters, > > I would like to ask you to add one more bugfix to the beta1: > https://issues.apac

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

; чт, 20 окт. 2022 г. в 08:36, Aleksandr Pakhomov : > > >> > > > >> >> Hi, Igniters. > > >> >> > > >> >> I would like to ask you to add a couple of tickets that are > required > > >> for > > >> >> packaging: > &

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

scope. ср, 19 окт. 2022 г. в 15:53, Вячеслав Коптилин : > Hi Yuriy, > > I agree, let's add them to the scope. > > Thanks, > S. > > > ср, 19 окт. 2022 г. в 15:20, Юрий : > > > Dear Release managers and Igniters, > > > > I would like to add the f

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

Dear Release managers and Igniters, I would like to add the following tickets to Ignite 3.0.0 beta1: https://issues.apache.org/jira/browse/IGNITE-17820 - improvement SQL and required for the next ticket https://issues.apache.org/jira/browse/IGNITE-17748 - related to support of indexes https://iss

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

Seems SQL API: Add batched DML queries support [1] will be moved to next alpha, so pleas don't waiting for it. In the same time SQL API: Examples [2] already done and merged to alpha 5 branch. [1] https://issues.apache.org/jira/browse/IGNITE-16963 [2] https://issues.apache.org/jira/browse/IGNITE

Re: Apache Ignite 3.0.0 alpha 5 RELEASE [Time, Scope, Manager]

Hi Andrey, It's good news, thanks for take RM role and provide list of changes for the alpha. Proposed dates looks good to me as well as the scope of the release пн, 23 мая 2022 г. в 16:05, Andrey Gura : > Hi Igniters, > > Four months have passed already since the Ignite 3 alpha 4 release. At >

Re: [VOTE] Create separate Jira project and Confluence space for Ignite 3

+1 вт, 5 окт. 2021 г. в 02:52, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Hello Community, > > As discussed in [1], I would like to propose the creation of a separate > Jira project and Confluence space for Ignite 3. > > Ignite 2 and Ignite 3 are developed in parallel in separate rep

Re: [DISCUSS] Confuse default inspections.

I totally agree. Let's get rid of them. вт, 20 июл. 2021 г. в 18:11, Konstantin Orlov : > + for both > > -- > Regards, > Konstantin Orlov > > > > On 20 Jul 2021, at 16:32, Pavel Tupitsyn wrote: > > > > Agree with for both points > > > > On Tue, Jul 20, 2021 at 3:14 PM Alexander Polovtcev < > ale

Re: Stop sending IGNITE Created e-mails to dev@

Hi, Ilya, could you please add me to "Contributors 1" too? пн, 26 апр. 2021 г. в 12:29, Ilya Kasnacheev : > Hello! > > I have added you to "Contributors 1" role. Everybody in this role will > still get those "issue created" e-mail. > > Feel free in asking me to enlist. > > Regards, > -- > Ilya Ka

Re: Removing MVCC public API

+1 ср, 9 дек. 2020 г. в 11:25, Maxim Muzafarov : > +1 > > > Also, I want to mention the list of MVCC related opened issues [1] > without any updates for over a year. > > [1] https://s.apache.org/1r5yk > > On Wed, 9 Dec 2020 at 10:22, Alexei Scherbakov > wrote: > > > > +1 > > > > ср, 9 дек. 2020

Re: IEP-54: Schema-first approach for 3.0

A little bit my thoughts about unsigned types: 1. Seems we may support unsign types 2. It requires adding new types to the internal representation, protocol, e.t.c. 3. internal representation should be the same as we keep sign types. So it will not requires more memory 4. User should be aware of s

Re: delete is too slow, sometimes even causes OOM

"Lazy" flag cannot solve the problem of running > too > > slow. > > > > On 2020/11/06 09:50:15, Юрий wrote: > > > Hi Frank! > > > > > > There is an old ticket [1] - We will try to prioritize it to finish > > before > > > t

Re: delete is too slow, sometimes even causes OOM

Hi Frank! There is an old ticket [1] - We will try to prioritize it to finish before the end of the year it should prevent OOM for most cases. [1] https://issues.apache.org/jira/browse/IGNITE-9182 вт, 3 нояб. 2020 г. в 18:53, frank li : > Current code logic for DELETE is as follows: > if WHERE

Re: Proposal of new event QUERY_EXECUTION_EVENT

_QUERY_EXECUTED provides a sql clause without > > > limitations. If we're going to provide some restrictions it will > require > > > additional investigation. I see at least 2 configurations here: > > > 1. Ignite can be configured to hide clase, params only or nothing

Re: Proposal of new event QUERY_EXECUTION_EVENT

In my opinion existing events EVT_CACHE_QUERY_EXECUTION_STARTED should be deprecated and added two new for start and for end of queries which should cover all SQL query types. I have some doubts about provide text of a query even with hidden arguments, probably it should be configured due to it cou

Roadmap of new distributed SQL engine based on Calcite

Dear Igniters, Many of you heard about starting development of new SQL engine based on Calcite. Currently we are only in beginning of the way and it will require many works to achieve the goal. In order to understand where are we and which features already done and which of them could be started b

Re: [CVE-2020-1963] Apache Ignite access to file system disclosure vulnerability

> >> >> Thanks, Could you please confirm when the analysis will be updated here >> for the CVE logged. >> >> https://nvd.nist.gov/vuln/detail/CVE-2020-1963 >> >> >> >> Regards, >> Sriveena >> >> >> >> *From:* Юри

[CVE-2020-1963] Apache Ignite access to file system disclosure vulnerability

Hi All, Apache Ignite 2.8.1 has been released. The release contain fix of critical vulnerability CVE-2020-1963: Apache Ignite access to file system through predefined H2 SQL functions Severity: Critical Vendor: The Apache Software Foundation Versions Affected: All versions of Apache Ignite up

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

Nikolay, Release 2.8.1 are delayed and announced dates [1] at release page is not actual. Could you update it to reflect current vision of release date? [1]. https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 чт, 7 мая 2020 г. в 17:23, Nikolay Izhikov : > Done. > > > > 7 мая

Re: [DISCUSSION] Major changes in Ignite in 2020

Hi Igniters! Major changes that are going to be contributed from our side for IGNITE SQL: - Local runtime statistics which helps to estimate query execution plan. It should help use right join order in most cases. Seems could be done by Q3. - most efforts will be direct to new SQL eng

Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental

-1 Prohibit It looks inconsistent to me deprecate one API without present new stable API as replacement. пн, 10 февр. 2020 г. в 11:02, Alexey Goncharuk : > Dear Apache Ignite community, > > We would like to conduct a formal vote on the subject of whether to allow > or prohibit a joint existence

Re: Aggregation functions

Hi Pavel, 1. Yes GROUP_CONCAT function works and as for collocated and for non collocated case. There are following tests: org.apache.ignite.internal.processors.query.IgniteSqlGroupConcatNotCollocatedTest org.apache.ignite.internal.processors.query.IgniteSqlGroupConcatCollocatedTest 2. Seems ye

Re: Is Ignite planning to support COMMENT ON statements?

Hi Liyuj, As of now we don't support COMMENT ON statements and don't have such plans or a tickets to add one. But I agree that it should add facilities for users. Feel free to raise the ticket. ср, 10 июл. 2019 г. в 00:48, Dmitriy Pavlov : > Hi, > > I'm not aware of such plans, for now. > > May

Re: [discussion] using custom build of H2 for Ignite

Agree with Ivan. We can start work with H2 fork owned by GG and decide change it later in case it will bring some issues to Ignite community. Currently I don't see any issues here. I'm worried about the issue, with process to synchonize changes H2 fork and Ignite. As possible solution it could be

Re: proposed realization KILL QUERY command

ltiple nodes and a single KILL command with the id > can halt it everywhere. If someone decided to shut all queries on the node, > then it sounds like the node is experiencing big troubles and it might be > better just to shut it down completely. > > - > Denis > > > On

Re: SQL View with list of existing indexes

> IGNITE.TABLES view instead > 4) Inline size is definitely useful metric. Not sure about approximate > inline size > 5) I would add list of columns in plain comma-separated form with ASC/DESC > modifiers > > Thoughts? > > Vladimir. > > On Thu, Jan 24, 2019 at 3:52 PM

Re: SQL View with list of existing indexes

from my initial proposal. чт, 24 янв. 2019 г. в 15:51, Юрий : > Hi Igniters, > > As part of IEP-29: SQL management and monitoring > <https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring> > I'm going to implement SQL view with list o

SQL View with list of existing indexes

Hi Igniters, As part of IEP-29: SQL management and monitoring I'm going to implement SQL view with list of existing indexes. I've investigate how it expose by ORACLE, MySQL and Postgres. ORACLE - https://d

Re: SQL views for IO statistics

T? ср, 16 янв. 2019 г. в 18:44, Denis Magda : > Wouldn't disk_read and memory_read be better naming? > > - > Denis > > > On Wed, Jan 16, 2019 at 7:38 AM Юрий wrote: > > > Denis, > > > > Physical reads is load page from storage to memor

Re: SQL views for IO statistics

> views for SQL table related statistics. It's still hard to explain the user > the relations between caches and tables. Hopefully, this will be fixed in > 3.0 with renaming but as for the statistics can we use anything neutral for > the view names? > > - > Denis > > &g

Re: proposed realization KILL QUERY command

. в 18:35, Vladimir Ozerov : > Hi, > > Concatenation through a letter looks like a good approach to me. As far as > killing all queries on a specific node, I would put it aside for now - this > looks like a separate command with possibly different parameters. > > On Tue, Jan 15,

SQL views for IO statistics

Hi Igniters! As part of IEP-27 we already gathering IO statistics and expose it through JMX. User who use only SQL should have access to the statistics also. So let's discuss about how such SQL view should looks.

Re: proposed realization KILL QUERY command

ul for debugging purposes, e.g. grep over > logs. So ideally query ID should not have any symbols which interfere with > grep syntax. > > > On Mon, Jan 14, 2019 at 3:09 PM Юрий wrote: > > > Hi Igniters, > > > > Earlier we discuss about columns for running queries.

Re: proposed realization KILL QUERY command

; > > > > look like a SQL command. What if we use a SQL approach > > introducing > > > > named > > > > > > > parameters: > > > > > > > > > > > > > > KILL QUERY query_id=10 [AND node_id=5] > > > >

Re: Query history statistics API

real queries. What is your opinion? пт, 21 дек. 2018 г. в 19:23, Юрий : > Vladimir, thanks for your expert opinion. > > I have some thoughts about 5 point. > I tried to find how it works for Oracle and PG: > > *PG*: keep by default 1000 (can be configured) statements without

Re: Query history statistics API

oldest entries. But this should be done with care - under some > workloads new queries will be generated very quickly. In this case we > should either fallback to synchronous evicts, or do not log history at all. > > Thoughts? > > Vladimir. > - > > On Fri, Dec 21, 2018 at 11:22 A

Re: Query history statistics API

Alexey, Yes, such property to configuration history size will be added. I think default value should be 0 and history by default shouldn't be gather at all, and can be switched on by property in case when it required. Currently I planned use the same way to evicting old data as for queryMetrics -

Query history statistics API

Hi Igniters, As of now we have query statistics ( *org.apache.ignite.IgniteCache#queryMetrics*) , but it's look a little bit wrong, due to at least few reasons: 1) Duration execution it just time between start execution and return cursor to client and doesn't include all life time of query. 2) It

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

cluster currently out of scope the change and will be described for discussing later. Is there any objections for described proposal? чт, 29 нояб. 2018 г. в 09:03, Юрий : > Hi Alex, > > I've just started implement of the view. Thanks for the your efforts! > > ср, 28 нояб. 2018 г

Re: [VOTE] Apache Ignite 2.7.0 RC1

+1 пт, 30 нояб. 2018 г. в 13:25, Anton Vinogradov : > +1 > > пт, 30 нояб. 2018 г. в 10:05, Seliverstov Igor : > > > +1 > > > > пт, 30 нояб. 2018 г., 9:59 Nikolay Izhikov nizhi...@apache.org: > > > > > Igniters, > > > > > > We've uploaded a 2.7.0 release candidate to > > > > > > https://dist.apach

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

; queries > > > IDs somehow anyway and that name might be resued in the WHERE clause of > > > KILL. > > > > > > Should we discuss the syntax in a separate thread? > > > > > > -- > > > Denis > > > > > > > > > >

Re: [VOTE] Creation dedicated list for github notifiacations

+1 вт, 27 нояб. 2018 г. в 11:22, Andrey Mashenkov : > +1 > > On Tue, Nov 27, 2018 at 10:12 AM Sergey Chugunov < > sergey.chugu...@gmail.com> > wrote: > > > +1 > > > > Plus this dedicated list should be properly documented in wiki, > mentioning > > it in How to Contribute [1] or in Make Teamcity G

Re: proposed realization KILL QUERY command

ginning (how do I look for a query id and node id, etc) then the > things get clearer. > > -- > Denis > > On Tue, Nov 20, 2018 at 1:03 AM Юрий wrote: > > > Hi Vladimir, > > > > Thanks for your suggestion to use MANAGEMENT_POOL for processing > > cancellation

Re: proposed realization KILL QUERY command

mand will be processed properly by all > kinds of SQL queries - SELECT/DML/DDL, non-transactional or transactional, > local queries and distributed queries. Will we be able to support all these > modes? > > Vladimir. > > On Mon, Nov 19, 2018 at 6:37 PM Юрий wrote: > &g

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

t; > Something like this: > KILL QUERY WHERE nodeId=25 and queryId=1234 > > Denis > > пт, 16 нояб. 2018 г. в 14:12, Юрий : > > > I fully agree with last sentences and can start to implement this part. > > > > Guys, thanks for your productive participate a

proposed realization KILL QUERY command

Hi Igniters, Earlier we agreed about syntax KILL QUERY '[node_order].[query_counter]', e.g. KILL QUERY '25.123' for single query or KILL QUERY '25.*' for all queries on the node. Which is part of IEP-29 .

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

ny queries initially we need just send the cancel > request > > to > > > > node who started the query. This mechanism is already in Ignite. > > > > > > > > > Can we locate node_id behind the scenes if the user supplies query_id > > only?

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

this syntax going to work only from thin clients, or if it just > designed for them, but will also be usable from basic SQL API? > > Best Regards, > Igor > > > On Tue, Nov 13, 2018 at 12:15 PM Юрий wrote: > > > Igniters, > > > > Some comment

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

- Please share examples of SELECTs in the IEP that would show how to > find long running queries, queries that cause a lot of I/O troubles. > > -- > Denis > > On Tue, Nov 13, 2018 at 1:15 AM Юрий wrote: > > > Igniters, > > > > Some comments for my origin

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Postgres syntax ( detailed information in IEP-29 <https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring> ). пн, 12 нояб. 2018 г. в 19:28, Юрий : > Igniters, > > Below is a proposed design for thin client SQL management and monitoring > to canc

proposed design for thin client SQL management and monitoring (view running queries and kill it)

Igniters, Below is a proposed design for thin client SQL management and monitoring to cancel a queries. 1) Ignite expose system SQL view with name *running_queries* proposed columns: *node_id, query_id, sql, schema_name, connection_id, duration*. node_id - initial node of request query_id - uniq

Re: SQL management and monitoring improvements

can I know a total number of SELECTs, or a total number of SELECTs > > happened yesterday for specific data sets. Do believe that it's feasible > > and just not covered. > > > > -- > > Denis > > > > > > > > On Wed, Nov 7, 2018 at 2:01 AM Ю

Re: SQL management and monitoring improvements

ific data sets. Do believe that it's feasible > and just not covered. > > -- > Denis > > > > On Wed, Nov 7, 2018 at 2:01 AM Юрий wrote: > > > Hi Igniters! > > > > I think we can improve Ignite management and monitoring instruments > related >

SQL management and monitoring improvements

Hi Igniters! I think we can improve Ignite management and monitoring instruments related to SQL. I've prepared draft of IEP-29: SQL management and monitoring . What do you think about it? May be do you ha

Re: Page IO statistics for Ignite

ul feedback if see how the metrics will look like from >> the >> > API standpoint. If it's not difficult please create a draft. >> > >> > AS for the interface, in addition to JMX and SQL we need to ensure Visor >> > CMD and Web Console gets updated. *A

Re: ML examples wrap logic in IgniteThread. Why?

Denis, Thanks for this notice, actually this is some kind of atavism. Run this code inside IgniteThread was a requirement when we had a distributed matrices. But now all our algorithms builds over distributed datasets and we don't need it anymore. I created JIRA ticket

[ML] New features and improvement of ML module for 2.7 release

Hello Igniters, I want to make up some overview of all features and major improvement of ML module for this release. So let me start from the one of our main feature for this release: *TensorFlow integration* This integration allows us to use

[ML] TensorFlow intergration module release

Hello, Igniters. For release 2.7 we will introduce integration between TensorFlow and Apache Ignite. This integration contains changes on Apache Ignite side and on TensorFlow side. Apache Ignite part is the command line tool which allows create and maintain TensorFlow clusters over Apache Ignite

Page IO statistics for Ignite

Hi Igniters, I started IGNITE-8580 ticket related to print page read/write metrics and did some investigation what other databases provide for the similar purposes. Based on the investigation I want to propose my raw vision of how to IGNITE can

Re: Apache Ignite 2.7 release

Denis, Nikolay, Igniters, This is a list of planned ML features for Apache Ignite 2.7 release: - Tensor Flow integration ( https://issues.apache.org/jira/browse/IGNITE-8670) - Data preprocessing (https://issues.apache.org/jira/browse/IGNITE-8662) - Model validation (https://issues.apa

[ML] Bugs in GA Grid

Turik, Could you please take a look on those two bugs: https://issues.apache.org/jira/browse/IGNITE-9354 https://issues.apache.org/jira/browse/IGNITE-9359 Thanks, Yury

welcome

Hello, Ignite Community! My name is Iurii. I want to contribute to Apache Ignite. my JIRA user name is jooger. Any help on this will be appreciated. Thanks! -- Live with a smile! :D