You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2020/12/24 03:46:00 UTC
[jira] [Resolved] (SPARK-33659) Document the current behavior for
DataStreamWriter.toTable API
[ https://issues.apache.org/jira/browse/SPARK-33659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-33659.
----------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
Issue resolved by pull request 30885
[https://github.com/apache/spark/pull/30885]
> Document the current behavior for DataStreamWriter.toTable API
> --------------------------------------------------------------
>
> Key: SPARK-33659
> URL: https://issues.apache.org/jira/browse/SPARK-33659
> Project: Spark
> Issue Type: Improvement
> Components: Structured Streaming
> Affects Versions: 3.1.0
> Reporter: Yuanjian Li
> Assignee: Yuanjian Li
> Priority: Blocker
> Fix For: 3.1.0
>
>
> Follow up work for SPARK-33577 and need to be done before the 3.1 release. As we didn't have full support for the V2 table created in the API, the following documentation work is needed:
> * figure out the effects when configurations are (provider/partitionBy) conflicting with existing table, and document in javadoc of {{toTable}}. I think you'll need to make a matrix and describe which takes effect (table vs input) - creating table vs table exists, DSv1 vs DSv2 (4 different situations should be all documented).
> * document the lack of functionality on creating v2 table in javadoc of {{toTable}}, and guide that they should ensure table is created in prior to avoid the behavior unintended/insufficient table is being created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org