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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-26191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716757#comment-16716757 ] 

ASF GitHub Bot commented on SPARK-26191:
----------------------------------------

HyukjinKwon commented on issue #23159: [SPARK-26191][SQL] Control truncation of Spark plans via maxFields parameter
URL: https://github.com/apache/spark/pull/23159#issuecomment-446144568
 
 
   Looks okay but let me leave it to @cloud-fan, @gatorsmile and @hvanhovell 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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