You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/03/27 08:26:00 UTC

[jira] [Assigned] (IGNITE-7884) Ship SQL scripts with same database in Ignite

     [ https://issues.apache.org/jira/browse/IGNITE-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov reassigned IGNITE-7884:
---------------------------------------

    Assignee: Vladimir Ozerov

> Ship SQL scripts with same database in Ignite
> ---------------------------------------------
>
>                 Key: IGNITE-7884
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7884
>             Project: Ignite
>          Issue Type: New Feature
>          Components: examples, sql
>    Affects Versions: 2.5
>            Reporter: Denis Magda
>            Assignee: Vladimir Ozerov
>            Priority: Major
>             Fix For: 2.5
>
>
> As per discussion on @dev list, let's ship two kind of SQL scripts that can be used to create and populate a database quickly:
> [http://apache-ignite-developers.2346864.n4.nabble.com/Shipping-SQL-script-CSV-files-in-Ignite-examples-td27440.html]
>  
> The database below is suggested to be used because it represents real data, allows setting up affinity collocation and demonstrate meaningful SQL queries with joins:
> [https://github.com/dmagda/ignite_world_demo/blob/master/ignite_world.sql]
>  
> First, this script can be used as is and executed in any SQL tool such as SQLline.
> Second, to demonstrate the use of {{COPY}} command we should take the same script, create a file that will store DDL statements and turn INSERTS into a CSV file.
>  



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