Subject: [IoTDB] Request to Work on Issue #17797: SELECT Alias Reuse Hi Apache IoTDB Community,
I would like to work on the following issue: https://github.com/apache/iotdb/issues/17797 The issue is about supporting SELECT output alias reuse in IoTDB table model SQL, including aliases in GROUP BY, aliases in ORDER BY, and lateral column alias references in later SELECT items. I noticed that this issue is currently open and unassigned. If there are no objections from the community, I would like to work on this task and submit a pull request for it. My implementation will follow the scope described in the issue: 1. Support GROUP BY <select_alias>. 2. Support ORDER BY <select_alias>. 3. Support later SELECT items referencing earlier SELECT aliases. 4. Keep existing ordinal references such as GROUP BY 1 and ORDER BY 2 unchanged. 5. Keep WHERE and HAVING alias resolution out of scope. 6. Preserve subquery scope boundaries. 7. Add focused tests for alias resolution, name conflicts, ambiguity cases, aggregate interaction, and regression behavior. I plan to make the changes mainly in the analyzer stage, including name resolution, expression rewriting, Analysis recording, and ensuring planner consistency. I do not plan to introduce parser changes unless further discussion shows they are necessary. Please let me know if there are any concerns, suggestions, or preferred implementation constraints before I start the PR. Best regards, Bryan Yang （杨易达） https://github.com/DaZuiZui
