Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Return Columns Mismatch with the Query Given Order #4360

Closed
shirly121 opened this issue Dec 12, 2024 · 0 comments · Fixed by #4364
Closed

[BUG] Return Columns Mismatch with the Query Given Order #4360

shirly121 opened this issue Dec 12, 2024 · 0 comments · Fixed by #4364
Assignees

Comments

@shirly121
Copy link
Collaborator

shirly121 commented Dec 12, 2024

Describe the bug

For Query

Match (n) Return count(n), n;

it returns the columns in the order of n, count(n), should be count(n), n;

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • GraphScope version: [e.g., v0.1, v0.2.2, master]
  • OS: [e.g. macOS, Linux]
  • Version [e.g. 10.15]
  • Kubernetes Version [e.g., 1.19]

Additional context
Add any other context about the problem here.

@shirly121 shirly121 self-assigned this Dec 12, 2024
shirly121 added a commit that referenced this issue Jan 2, 2025
<!--
Thanks for your contribution! please review
https://github.com/alibaba/GraphScope/blob/main/CONTRIBUTING.md before
opening an issue.
-->

## What do these changes do?
as titled.

<!-- Please give a short brief about these changes. -->

## Related issue number

<!-- Are there any issues opened that will be resolved by merging this
change? -->

Fixes #4360

---------

Co-authored-by: BingqingLyu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant