We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What is the bug? When querying using PPL but there is an alias field in the filter clause. The query fails.
How can one reproduce the bug? Steps to reproduce the behavior:
What is the expected behavior? A clear and concise description of what you expected to happen.
What is your host/environment?
Do you have any screenshots? If applicable, add screenshots to help explain your problem.
Do you have any additional context? Add any other context about the problem.
The text was updated successfully, but these errors were encountered:
could u add more context? sample query and sample data to reporduce the issue.
Sorry, something went wrong.
I can provide a sample
PUT /try { "mappings":{ "properties": { "time1": { "type": "date" }, "time2": { "type": "alias", "path": "time1" } } } }
POST /_plugins/_ppl/ { "query": "source=try | fields `time2`" }
It shows
{ "error": { "reason": "Invalid Query", "details": "can't resolve Symbol(namespace=FIELD_NAME, name=time2) in type env", "type": "SemanticCheckException" }, "status": 400 }
No branches or pull requests
What is the bug?
When querying using PPL but there is an alias field in the filter clause. The query fails.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: