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] NESTED Function Fails in non-SELECT Clauses #1548

Closed
forestmvey opened this issue Apr 18, 2023 · 2 comments
Closed

[BUG] NESTED Function Fails in non-SELECT Clauses #1548

forestmvey opened this issue Apr 18, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@forestmvey
Copy link
Collaborator

forestmvey commented Apr 18, 2023

What is the bug?
The nested function fails query execution when used in WHERE, GROUP BY, ORDER BY, and HAVING clauses.

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Execute query: select * from nested_objects GROUP BY nested(message.info);
  2. See error message:
{
  "error": {
    "reason": "There was internal problem at backend",
    "details": "Failed to serialize expression: FunctionExpression(functionName=nested, arguments=[message.info])",
    "type": "IllegalStateException"
  },
  "status": 503
}
  1. Execute Query: SELECT * FROM nested_objects WHERE nested(message.info) = 'a';
  2. See error:
{
  "error": {
    "reason": "There was internal problem at backend",
    "details": "Failed to serialize expression: =(FunctionExpression(functionName=nested, arguments=[message.info]), \"a\")",
    "type": "IllegalStateException"
  },
  "status": 503
}

What is the expected behavior?
Nested function query should succeed when used in WHERE clause, and in GROUP BY with json format.

What is your host/environment?

@dai-chen
Copy link
Collaborator

Do we want to close this now?

@forestmvey forestmvey changed the title [BUG] NESTED Function Fails in WHERE and GROUP BY Clauses [BUG] NESTED Function Fails in non-SELECT Clauses Apr 20, 2023
@forestmvey
Copy link
Collaborator Author

Do we want to close this now?

@dai-chen Yes we are good to close this now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants