Re: How to find primary keys column of a table in ignite using sys tables?

Hi, There is the ticket [1] for the issue. While the ticket is not resolved try to use PRAGMA table_info(table-name); as explained in the SQLite PRAGMA documentation [2]. [1] https://issues.apache.org/jira/browse/IGNITE-16667 [2] http://www.sqlite.org/pragma.html#pragma_table_info пн, 30 мая

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

[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: [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

Re: Slow select distinct query on primary key

ine size 60? > I'd think 55 should be enough to inline Account_ID. 55 = 1 /* byte, type > code */ + 4 /* int, array lenght */ + 50 /* data size for ANSI chars */ > > On Fri, Nov 30, 2018 at 1:25 PM Юрий wrote: > >> Please provide explain plan of the query to check that index i

Re: Slow select distinct query on primary key

Please provide explain plan of the query to check that index is use. *EXPLAIN {your select statement}* Also I noticed ACCOUNT_ID have length 50. Need to increase of inline index size for the index. Try create index with the follow command *CREATE INDEX PERF_POSITIONS_IDX ON PERF_POSITIONS

Re: Slow select distinct query on primary key

Hi, There is some issue to use indexes for complex PK, which is already fixed and will be included into 2.8. https://issues.apache.org/jira/browse/IGNITE-8386 As of now to fix your performance issue you can create separate index for ACCOUNT_ID column. чт, 29 нояб. 2018 г. в 02:24, yongjec : >

Re: Performance of SQL query by partial primary key

Hi Ray, You are right, currently complex PK can't be used as index and performance for your query are bad due to full scan. After IGNITE-8386 will be merged the same query start use PK index. вт, 18 сент. 2018 г. в 8:16, Ray : > To answer my