[jira] [Commented] (IGNITE-9228) Spark SQL Table Schema Specification

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on IGNITE-9228:
----------------------------------------

GitHub user stuartmacd opened a pull request:

    https://github.com/apache/ignite/pull/4551

    IGNITE-9228 Spark SQL Table Schema Specification

    

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

    $ git pull https://github.com/stuartmacd/ignite ignite-9228

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

    https://github.com/apache/ignite/pull/4551.patch

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

    This closes #4551
    
----
commit 9123bfc059dc83d038f1b4a4d06cef735833389b
Author: Stuart Macdonald <29...@...>
Date:   2018-08-13T15:05:53Z

    Fix cloneSession on IgniteSparkSession

commit ff6d47f1c5f202f221010e5be0c5f7a31e9d44fe
Author: Stuart Macdonald <29...@...>
Date:   2018-08-15T16:51:31Z

    Schema name specification for Spark dataframe loading

----


> Spark SQL Table Schema Specification
> ------------------------------------
>
>                 Key: IGNITE-9228
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9228
>             Project: Ignite
>          Issue Type: Improvement
>          Components: spark
>    Affects Versions: 2.6
>            Reporter: Stuart Macdonald
>            Priority: Major
>             Fix For: 2.7
>
>
> The Ignite Spark SQL interface currently takes just “table name” as a
> parameter which it uses to supply a Spark dataset with data from the
> underlying Ignite SQL table with that name.
> To do this it loops through each cache and finds the first one with the
> given table name [1]. This causes issues if there are multiple tables
> registered in different schema with the same table name as you can only
> access one of those from Spark. We could either:
> 1. Pass an extra parameter through the Ignite Spark data source which
> optionally specifies the schema name.
> 2. Support namespacing in the existing table name parameter, ie
> “schemaName.tableName”
> [1 ]https://github.com/apache/ignite/blob/ca973ad99c6112160a305df05be9458e29f88307/modules/spark/src/main/scala/org/apache/ignite/spark/impl/package.scala#L119



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