ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6406) SQL: CREATE INDEX should fill index from multiple threads
Date Fri, 10 Nov 2017 12:52:00 GMT

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

ASF GitHub Bot commented on IGNITE-6406:

GitHub user dolphin1414 opened a pull request:


    IGNITE-6406: SQL: CREATE INDEX should fill index from multiple threads.

    A parallel index creation and an SQL keyword PARALLEL parsing implemented.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-6406

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3014
commit 97069d5af3b54a008bd32db01064bfdd90c3f5bd
Author: rkondakov <rkondakov@gridgain.com>
Date:   2017-11-10T12:13:29Z

    IGNITE-6406: Parallel index creation implementated
    (cherry picked from commit d34f16f0ecd35ea55efb0b2e5f94734c56c9cca3)


> SQL: CREATE INDEX should fill index from multiple threads
> ---------------------------------------------------------
>                 Key: IGNITE-6406
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6406
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>            Assignee: Roman Kondakov
>              Labels: iep-1, performance
> Currently when {{CREATE INDEX}} command is executed, we fill new index from a single
thread. Low CPU, long create time. We can trade off CPU vs time by adding more threads. 
> Probably number of threads should be specified in {{CREATE INDEX}} command as a hint.

This message was sent by Atlassian JIRA

View raw message