guixiaowen opened a new pull request, #45931:
URL: https://github.com/apache/spark/pull/45931

   
   
   ### What changes were proposed in this pull request?
   Show the offset value in TakeOrderedAndProjectExec.
   
    
   
   For example:
   
    
   `
   explain select * from test_limit_offset order by a  limit 2  offset 1;
   
   plan
   
   == Physical Plan ==
   
   TakeOrderedAndProject(limit=3, orderBy=[a#171 ASC NULLS 
FIRST](https://issues.apache.org/jira/browse/SPARK-47767#171%20ASC%20NULLS%20FIRST),
 output=[a#171](https://issues.apache.org/jira/browse/SPARK-47767#171))
   
   +- Scan hive spark_catalog.bigdata_qa.test_limit_offset 
[a#171](https://issues.apache.org/jira/browse/SPARK-47767#171), 
HiveTableRelation [`spark_catalog`.`test`.`test_limit_offset`, 
org.apache.hadoop.hive.ql.io.orc.OrcSerde, Data Cols: 
[a#171](https://issues.apache.org/jira/browse/SPARK-47767#171), Partition Cols: 
[]]
   `
   
   
   
   No offset is displayed. If it is displayed, it will be more user-friendly
   
   
   ### Why are the changes needed?
   No offset is displayed. If it is displayed, it will be more user-friendly
   
   
   
   ### Does this PR introduce _any_ user-facing change?
   
   After this pr, the offset in TakeOrderedAndProjectExec will  be displayed.
   
   `
   explain select * from test_limit_offset order by a  limit 2  offset 1;
   
   plan
   
   == Physical Plan ==
   
   TakeOrderedAndProject(limit=3,  offset=1, orderBy=[a#171 ASC NULLS 
FIRST](https://issues.apache.org/jira/browse/SPARK-47767#171%20ASC%20NULLS%20FIRST),
 output=[a#171](https://issues.apache.org/jira/browse/SPARK-47767#171))
   
   +- Scan hive spark_catalog.bigdata_qa.test_limit_offset 
[a#171](https://issues.apache.org/jira/browse/SPARK-47767#171), 
HiveTableRelation [`spark_catalog`.`test`.`test_limit_offset`, 
org.apache.hadoop.hive.ql.io.orc.OrcSerde, Data Cols: 
[a#171](https://issues.apache.org/jira/browse/SPARK-47767#171), Partition Cols: 
[]]
   `
   
   
   ### How was this patch tested?
   ut
   
   
   ### Was this patch authored or co-authored using generative AI tooling?
   <!--
   If generative AI tooling has been used in the process of authoring this 
patch, please include the
   phrase: 'Generated-by: ' followed by the name of the tool and its version.
   If no, write 'No'.
   Please refer to the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

Reply via email to