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

Dongjoon Hyun commented on SPARK-35624:
---------------------------------------

Thank you for filing JIRA, [~allendang]. There is some community guideline I 
want to introduce to you.
- https://spark.apache.org/contributing.html

1. First of all, 3.1.2 is already released. Why do you set `3.1.2` to the `Fix 
Version`? There is no way to update the already release version, isn't it?
2. Second, you should not set `Target Version`. It's reserved to the Apache 
Spark committer in general. In addition, Target Version 3.1.2 is also wrong 
because it's already released.
3. For `Improvement` JIRA, you can set only `Affects Versions` to the version 
of master branch which is currently 3.2.0.

I'll fix the wrong information here for now. Please consider the above next 
time. Thank you in advance!

> Support reading inputbytes and inputrecords of the stage int spark context 
> interface 
> -------------------------------------------------------------------------------------
>
>                 Key: SPARK-35624
>                 URL: https://issues.apache.org/jira/browse/SPARK-35624
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 3.1.2
>            Reporter: allendang
>            Priority: Major
>             Fix For: 3.1.2
>
>
> One of our projects needs to count the amount of data scanned and the number 
> of scanned data rows during the execution of sparksql statements, but the 
> current version of spark does not provide an interface to view these data, so 
> I want to obtain this type of data through the spark context interface



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to