You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@auron.apache.org by "yew1eb (via GitHub)" <gi...@apache.org> on 2025/11/26 15:51:54 UTC
[I] Improve verbose string output for all Native*Exec operators to match Spark explain format [auron]
yew1eb opened a new issue, #1665:
URL: https://github.com/apache/auron/issues/1665
### **Description**
Native\*Exec operators currently lack verboseStringWithOperatorId, causing explain output to differ from Spark and reducing plan readability and diagnosability.
### **Proposed approach**
Override `verboseStringWithOperatorId` in each Native*Exec and mirror the corresponding Spark\*Exec formatting. Keep formatting in the Native\*Exec operator (do not delegate to underlying Spark\*Exec).
### Tasks：
- Implement `verboseStringWithOperatorId` for:
- [ ] NativeProjectBase
- [ ] NativeFilterBase
- [ ] NativeAggBase
- [ ] ...
--
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: commits-unsubscribe@auron.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Improve verbose string output for all Native*Exec operators to match Spark [auron]
Posted by "richox (via GitHub)" <gi...@apache.org>.
richox closed issue #1665: Improve verbose string output for all Native*Exec operators to match Spark
URL: https://github.com/apache/auron/issues/1665
--
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: commits-unsubscribe@auron.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Improve verbose string output for all Native*Exec operators to match Spark [auron]
Posted by "xumingming (via GitHub)" <gi...@apache.org>.
xumingming commented on issue #1665:
URL: https://github.com/apache/auron/issues/1665#issuecomment-3588547538
> causing explain output to differ from Spark and reducing plan readability and diagnosability.
Can you give an example? I try explain, but nothing native in the output:
```
spark-sql> explain extended select * from person;
== Parsed Logical Plan ==
'Project [*]
+- 'UnresolvedRelation [person], [], false
== Analyzed Logical Plan ==
id: int, name: string, address: string
Project [id#0, name#1, address#2]
+- SubqueryAlias spark_catalog.default.person
+- Relation default.person[id#0,name#1,address#2] parquet
== Optimized Logical Plan ==
Relation default.person[id#0,name#1,address#2] parquet
== Physical Plan ==
AdaptiveSparkPlan isFinalPlan=false
+- FileScan parquet default.person[id#0,name#1,address#2] Batched: true, DataFilters: [], Format: Parquet, Location: InMemoryFileIndex(1 paths)PushedFilters: [], ReadSchema: struct<id:int,name:string,address:string>
Time taken: 0.047 seconds, Fetched 1 row(s)
```
--
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: commits-unsubscribe@auron.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org