You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Gengliang Wang (JIRA)" <ji...@apache.org> on 2018/02/01 07:30:00 UTC
[jira] [Updated] (SPARK-23202) Add new API in DataSourceWriter:
onDataWriterCommit
[ https://issues.apache.org/jira/browse/SPARK-23202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gengliang Wang updated SPARK-23202:
-----------------------------------
Summary: Add new API in DataSourceWriter: onDataWriterCommit (was: Break down DataSourceV2Writer.commit into two phase)
> Add new API in DataSourceWriter: onDataWriterCommit
> ---------------------------------------------------
>
> Key: SPARK-23202
> URL: https://issues.apache.org/jira/browse/SPARK-23202
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.3.0
> Reporter: Gengliang Wang
> Priority: Major
>
> Currently, the api DataSourceV2Writer#commit(WriterCommitMessage[]) commits a
> writing job with a list of commit messages.
> It makes sense in some scenarios, e.g. MicroBatchExecution.
> However, on receiving commit message, driver can start processing messages(e.g. persist messages into files) before all the messages are collected.
> The proposal is to Break down DataSourceV2Writer.commit into two phase:
> # add(WriterCommitMessage message): Handles a commit message produced by \{@link DataWriter#commit()}.
> # commit(): Commits the writing job.
> This should make the API more flexible, and more reasonable for implementing some datasources.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org