You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Herman van Hovell (JIRA)" <ji...@apache.org> on 2016/11/16 14:43:59 UTC
[jira] [Commented] (SPARK-17977) DataFrameReader and
DataStreamReader should have an ancestor class
[ https://issues.apache.org/jira/browse/SPARK-17977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15670578#comment-15670578 ]
Herman van Hovell commented on SPARK-17977:
-------------------------------------------
[~marmbrus] Is there any reason for DataFrameReader and DataFrameReader to be completely separate classes (without a common ancestor)?
> DataFrameReader and DataStreamReader should have an ancestor class
> ------------------------------------------------------------------
>
> Key: SPARK-17977
> URL: https://issues.apache.org/jira/browse/SPARK-17977
> Project: Spark
> Issue Type: Wish
> Components: SQL
> Affects Versions: 2.0.0, 2.0.1
> Reporter: Amit Assudani
> Priority: Critical
>
> There should be an ancestor class of DataFrameReader and DataStreamReader to configure common options / format and use common methods. Most of the methods are exact same having exact same arguments. This will help create utilities / generic code being used for stream / batch applications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org