[
https://issues.apache.org/jira/browse/IGNITE-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712313#comment-16712313
]
ASF GitHub Bot commented on IGNITE-10314:
-----------------------------------------
GitHub user ldzhjn opened a pull request:
https://github.com/apache/ignite/pull/5598
IGNITE-10314 Spark dataframe will get wrong schema if user executes
add/drop column DDL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ldzhjn/ignite IGNITE-10314
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5598.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 #5598
----
commit bcdb69747f9a90fa0f2f9204708c576b72f1de94
Author: rayliu <rayliu@...>
Date: 2018-11-22T06:44:01Z
Fix bug
commit 8dcc21800a8eb7d1e731c362b4a53860274e85bd
Author: rayliu <rayliu@...>
Date: 2018-11-26T06:39:27Z
Add tests
commit 1d58fdf068b14ac9847a825dca3464148f9b7596
Author: rayliu <rayliu@...>
Date: 2018-11-26T06:53:16Z
Optimize imports
commit 336a291dd5a330b5e1e824e807187ef1960bb843
Author: rayliu <rayliu@...>
Date: 2018-11-26T07:01:47Z
Merge remote-tracking branch 'upstream/master' into IGNITE-10314
commit 304695781ac356ec3f81325c5ce3b244b9f01c8b
Author: rayliu <rayliu@...>
Date: 2018-12-06T09:46:28Z
Merge remote-tracking branch 'upstream/master' into IGNITE-10314
----
> Spark dataframe will get wrong schema if user executes add/drop column DDL
> --------------------------------------------------------------------------
>
> Key: IGNITE-10314
> URL: https://issues.apache.org/jira/browse/IGNITE-10314
> Project: Ignite
> Issue Type: Bug
> Components: spark
> Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7
> Reporter: Ray
> Assignee: Ray
> Priority: Critical
> Fix For: 2.8
>
>
> When user performs add/remove column in DDL, Spark will get the old/wrong
> schema.
>
> Analyse
> Currently Spark data frame API relies on QueryEntity to construct schema, but
> QueryEntity in QuerySchema is a local copy of the original QueryEntity, so
> the original QueryEntity is not updated when modification happens.
>
> Solution
> Get the latest schema using JDBC thin driver's column metadata call, then
> update fields in QueryEntity.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
