[
https://issues.apache.org/jira/browse/SPARK-16407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504303#comment-15504303
]
Michael Armbrust commented on SPARK-16407:
------------------------------------------
You are taking an experimental interface, which among other problems exposes
both deprecated APIs (SQLContext) and internal APIs
(org.apache.spark.sql.execution.streaming.Sink), and elevating it into the
primary user facing datasource API (DataStreamWriter). I think this is
premature and counter to the compatibility practices that we usually follow in
Spark.
> Allow users to supply custom StreamSinkProviders
> ------------------------------------------------
>
> Key: SPARK-16407
> URL: https://issues.apache.org/jira/browse/SPARK-16407
> Project: Spark
> Issue Type: Improvement
> Components: Streaming
> Reporter: holdenk
>
> The current DataStreamWriter allows users to specify a class name as format,
> however it could be easier for people to directly pass in a specific provider
> instance - e.g. for user equivalent of ForeachSink or other sink with
> non-string parameters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
