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 2018/12/27 10:16:00 UTC

[jira] [Resolved] (SPARK-26191) Control number of truncated fields

     [ https://issues.apache.org/jira/browse/SPARK-26191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herman van Hovell resolved SPARK-26191.
---------------------------------------
       Resolution: Fixed
         Assignee: Maxim Gekk
    Fix Version/s: 3.0.0

> 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
>            Assignee: Maxim Gekk
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> 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