ISSUE DESCRIPTION [SQL] "expand" projection is always named "value" ignoring "AS"…
- User
ISSUE DESCRIPTION
[SQL] "expand" projection is always named "value" ignoring "AS"
ArcadeDB Server v26.5.1 (build b6d08fee549dd5930303b362223869901aab0fac/1778533954349/main)Running on Linux 6.17.0-29-generic - OpenJDK 64-Bit Server VM 25.0.3-eaUsing
expandin a projection, the result-set contains an property namedvalueinspite an alias of the formAS x:SELECT expand([1,2,3,4]) AS testresults in:
{"result":[{"value":1},{"value":2},{"value":3},{"value":4}]}Interface
No new interfaces are introduced.
ADDITIONAL ADVICE
Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use
git checkout <file>to restore the file to its original state. You can also reset all changes in the repository usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto get the changes that need to be submitted.CHECKLIST
Before submitting your solution, please go over the following checklist and make sure you've done everything:
- If an error was reported in the issue description, I have successfully reproduced it.
- If an error was reported in the issue description, I have confirmed that my fix resolves the error.
- I have thought about edge cases and made sure my fix handles them as well.
- I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
(Current directory: /arcadedb, current file: none) bash-$
Assistant
Now let's fix
getExpandContentin ProjectionItem to preserve the alias:Assistant
No python. I'll use the
replacespecial command instead.Assistant
Same package
com.arcadedb.query.sql.parser, so no import needed. Now let's check the Identifier constructor with String param.Assistant
Good. Now update ExpandStep.java to use the property name instead of hardcoded "value".
Assistant
Now let's add a field
currentPropNameand use it instead of hardcoded "value".Assistant
Now update the setProperty("value"...) line and the propName assignment.
Assistant
Now update line 141 to set
currentPropName = propName;.Assistant
Now let's build and test.
Assistant
Compiles fine. Now let's write a reproduce test script.
Assistant
The fix works:
AS testgives{"test":1}..., and without alias it still defaults to{"value":1}...preserving backward compatibility.Now let's run the existing test suite related to expand.
Assistant
Tests passed (no failures reported). Let's check the surefire reports to confirm.
Assistant
All expand-related tests pass. Let's also run a broader test on SQL select tests to catch regressions related to projections/aliases.
Assistant
All pass. Now let's double check with a broader run including projection tests and aggregate related tests since we touched ProjectionItem.
Assistant
All pass. Let's clean up temp test files and review final diff.
Assistant
Only one call site (
SelectExecutionPlanner.java:701), which is the intended usage. Good, isolated change.Now let's run the full relevant module test suite for
com.arcadedb.query.sqlpackage broadly to catch any other regression.Assistant
Confirmed - this test failure is pre-existing and unrelated to our change (environment-dependent, based on available CPU cores for bucket count). All 2140 other tests in the
com.arcadedb.query.sql.**package pass with our changes. Let's view the final diff once more.Assistant
This looks good. Now let's go through the checklist.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →