You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/11/27 22:53:00 UTC
[jira] [Commented] (SPARK-26191) Control number of truncated fields
[ https://issues.apache.org/jira/browse/SPARK-26191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701139#comment-16701139 ]
Apache Spark commented on SPARK-26191:
--------------------------------------
User 'MaxGekk' has created a pull request for this issue:
https://github.com/apache/spark/pull/23159
> Control number of truncated fields
> ----------------------------------
>
> Key: SPARK-26191
> URL: https://issues.apache.org/jira/browse/SPARK-26191
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 2.4.0
> Reporter: Maxim Gekk
> Priority: Minor
>
> Currently, the threshold for truncated fields converted to string can be controlled via global SQL config. Need to add the maxFields parameter to all functions/methods that potentially could produce truncated string from a sequence of fields.
> One of use cases is toFile. This method aims to output not truncated plans. For now users has to set global config to flush whole plans.
--
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