ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11756) SQL: implement a table row count statistics for the local queries
Date Wed, 22 May 2019 09:18:01 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845698#comment-16845698

Ignite TC Bot commented on IGNITE-11756:

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3904395&amp;buildTypeId=IgniteTests24Java8_RunAll]

> SQL: implement a table row count statistics for the local queries
> -----------------------------------------------------------------
>                 Key: IGNITE-11756
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11756
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Roman Kondakov
>            Assignee: Roman Kondakov
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
> Row count statistics should help the H2 optimizer to select the better query execution
plan. Currently the row count supplied to H2 engine is hardcoded value == 10000 (see {{org.h2.index.Index#getRowCountApproximation}}). 
As a first step we can provide an actual table size in the case of local query. To prevent
counting size on each invocation we can cache row count value and invalidate it in some cases:
>  * Rebalancing
>  * Multiple updates (after the initial loading)
>  * On timeout (i.e. 1 minute)

This message was sent by Atlassian JIRA

View raw message