ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirill Shirokov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-7541) SQL COPY command: implement backend switching option
Date Thu, 25 Jan 2018 16:19:00 GMT
Kirill Shirokov created IGNITE-7541:
---------------------------------------

             Summary: SQL COPY command: implement backend switching option
                 Key: IGNITE-7541
                 URL: https://issues.apache.org/jira/browse/IGNITE-7541
             Project: Ignite
          Issue Type: Improvement
          Components: sql
            Reporter: Kirill Shirokov


When we load data using COPY command we can add key/value pairs to the cache using different
ways:

* Directly calling cache.putAll()
* Loading data via DataStreamer
* etc.

Every backend has its pros and cons. For example, the streamer is fast and asynchronous, although
it cannot replace value and cannot provide any statistics -- such as number of added records.
The direct interface is slow and synchronous, but provides us with an ability to either replace
or skip the records with the same key and respond to the user with full statistics.

There shall be an option in the SQL command to switch to particular backend. For example:

{noformat}
COPY
    FROM 'file'
    ...
    [BACKEND (DIRECT | STREAMER)]

We might have more backends in the future.
{noformat}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message