[jira] [Updated] (SPARK-47914) Do not display the splits parameter in Rang
[ https://issues.apache.org/jira/browse/SPARK-47914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-47914: --- Labels: pull-request-available (was: ) > Do not display the splits parameter in Rang > --- > > Key: SPARK-47914 > URL: https://issues.apache.org/jira/browse/SPARK-47914 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.5.1 >Reporter: guihuawen >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0 > > > [SQL] > explain extended select * from range(0, 4); > plan > == Parsed Logical Plan == > 'Project [*] > +- 'UnresolvedTableValuedFunction [range], [0, 4] > > == Analyzed Logical Plan == > id: bigint > Project [id#11L|#11L] > +- Range (0, 4, step=1, splits=None) > > == Optimized Logical Plan == > Range (0, 4, step=1, splits=None) > > == Physical Plan == > *(1) Range (0, 4, step=1, splits=1) > > The splits parameter will only be set during the physical execution phase. > But it is also displayed in the logical execution phase as None, which is not > very user-friendly. Showing the physical execution plan can help users. > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-47914) Do not display the splits parameter in Rang
[ https://issues.apache.org/jira/browse/SPARK-47914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] guihuawen updated SPARK-47914: -- Summary: Do not display the splits parameter in Rang (was: [SPARK-47914][SQL]Do not display the splits parameter in Rang) > Do not display the splits parameter in Rang > --- > > Key: SPARK-47914 > URL: https://issues.apache.org/jira/browse/SPARK-47914 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.5.1 >Reporter: guihuawen >Priority: Major > Fix For: 4.0.0 > > > [SQL] > explain extended select * from range(0, 4); > plan > == Parsed Logical Plan == > 'Project [*] > +- 'UnresolvedTableValuedFunction [range], [0, 4] > > == Analyzed Logical Plan == > id: bigint > Project [id#11L|#11L] > +- Range (0, 4, step=1, splits=None) > > == Optimized Logical Plan == > Range (0, 4, step=1, splits=None) > > == Physical Plan == > *(1) Range (0, 4, step=1, splits=1) > > The splits parameter will only be set during the physical execution phase. > But it is also displayed in the logical execution phase as None, which is not > very user-friendly. Showing the physical execution plan can help users. > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
