[
https://issues.apache.org/jira/browse/KUDU-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035009#comment-17035009
]
ASF subversion and git services commented on KUDU-3049:
-------------------------------------------------------
Commit 759f04c7ec868bb1cec4a196e47cf988af8875fd in kudu's branch
refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=759f04c ]
KUDU-3049: [spark] Automatic handling of schema drift
This patch adds a new write option `kudu.handleSchemaDrift`.
If set to true, when new fields are encountered the Kudu table
will be altered to include new columns for those fields.
Change-Id: Ib1edebb293d6ae79c26a0ecb9ce7755308f667f4
Reviewed-on: http://gerrit.cloudera.org:8080/15176
Reviewed-by: Adar Dembo <[email protected]>
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <[email protected]>
> [spark] Support automatic handling of schema drift
> ---------------------------------------------------
>
> Key: KUDU-3049
> URL: https://issues.apache.org/jira/browse/KUDU-3049
> Project: Kudu
> Issue Type: Improvement
> Components: spark
> Affects Versions: 1.11.0
> Reporter: Grant Henke
> Assignee: Grant Henke
> Priority: Minor
>
> When ingesting data via Spark often there are new fields that are not in the
> Kudu table. For example this could happen as a result of ingesting json into
> Kudu.
> This jira tracks adding an option to automatically alter a kudu table adding
> new columns when they are encountered.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
