You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Valentin Kulichenko (JIRA)" <ji...@apache.org> on 2018/02/01 00:18:00 UTC

[jira] [Commented] (IGNITE-7337) Spark Data Frames: support saving a data frame in Ignite

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

Valentin Kulichenko commented on IGNITE-7337:
---------------------------------------------

[~NIzhikov], let's do this renamings:
 * {{OPTION_CREATE_TABLE_OPTIONS}} -> {{OPTION_CREATE_TABLE_PARAMETERS}}
 * {{OPTION_PRIMARY_KEY_FIELDS}} -> {{OPTION_CREATE_TABLE_PRIMARY_KEY_FIELDS}}

{{OPTION_CACHE_FOR_DDL}} should go away. Our JDBC drivers and Web Console do not require to have a dummy cache, I believe they go though internal API to achieve this. Please investigate and propose a solution.

What is {{OPTION_WRITE_PARTITIONS_NUM}}?

> Spark Data Frames: support saving a data frame in Ignite
> --------------------------------------------------------
>
>                 Key: IGNITE-7337
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7337
>             Project: Ignite
>          Issue Type: New Feature
>          Components: spark
>    Affects Versions: 2.3
>            Reporter: Valentin Kulichenko
>            Assignee: Nikolay Izhikov
>            Priority: Major
>             Fix For: 2.5
>
>
> Once Ignite data source for Spark is implemented, we need to add an ability to store a data frame in Ignite. Most likely if should be enough to provide implementation for the following traits:
> * {{InsertableRelation}}
> * {{CreatableRelationProvider}}



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