zclllyybb commented on issue #3828:
URL: https://github.com/apache/doris-website/issues/3828#issuecomment-4562302169
Breakwater-GitHub-Analysis-Slot: slot_e48c70cda997
Initial analysis:
This looks like a Doris FE/Nereids planner consistency bug, not a DBeaver
issue and not an Elasticsearch data-read failure. The important part of the
error is:
```text
Input slot(s) not in child's output: yjsj#18
child output is: [..., yjsj#27]
LogicalProject projects=[yjsj#18 AS `yjsj`#9]
+--LogicalEsScan output=[..., yjsj#27]
```
So the column name exists in the ES scan output, but the `LogicalProject`
above the scan is still holding an older `ExprId`. That means the query fails
during FE plan validation before it reaches BE/ES execution.
The pattern is consistent with CTE inline/deep-copy remapping of a catalog
relation: the CTE body projects one ES column, then the copied scan has
regenerated output slots, but the upper project is not aligned with the copied
child output. In the current upstream master, this exact `LogicalEsScan` path
has already been removed/refactored by the ES catalog plugin-driven migration,
so the report needs the exact Doris version/branch to confirm whether it is on
an older ES scan path. On branch-4.0, there is also a very recent related fix,
`Preserve operative slots when deep copying logical relations` (#63315,
backported as #63708), which fixes incorrect remapping when the operative
column is not in the first output position. In this case `yjsj` is the last
column in the reported scan output, so that fix is highly relevant.
Suggested next steps:
1. Please provide the exact Doris version/build hash and branch. This is
required because upstream master no longer uses the `LogicalEsScan` class shown
in the error.
2. If the environment is branch-4.0 or a build before the fix above, please
retest with a build containing #63708 or cherry-pick that fix.
3. Please also test the direct query on the same column, not only `fssj`:
```sql
SELECT yjsj FROM es_.default_db.theme_jzxxb LIMIT 10;
```
4. If the issue still reproduces after the fix, please attach a minimal
redacted ES catalog/table definition, the ES mapping for this index, the full
Doris FE version output, relevant session variables for the planner, and the FE
log around the failing query.
This issue is currently filed in `apache/doris-website`, but the symptom is
a Doris planner/runtime issue. It should probably be transferred or recreated
in `apache/doris` once the version information is available.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
