You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Furthermore, the eval command is not executed because the parse tree ends in the spath token, which is a valid command in itself. So the spath does print some results, but they are incorrect. Any command afterwards is not executed.
Expected behavior
It can be seen in the grammar that it always requires the "path=" prefix before specifying the path, but it should be optional.
How to reproduce
Run the queries above.
Screenshots
Software version
6.1.0
Desktop (please complete the following information if relevant):
OS:
Browser:
Version:
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
The following query:
index=index_A | spath json
Doesn't parse the "json" part of the query. With the changes in #52, it gives this error:
If more commands are used after:
index=index_A | spath json | eval a=1
The error expands a bit:
Furthermore, the eval command is not executed because the parse tree ends in the spath token, which is a valid command in itself. So the spath does print some results, but they are incorrect. Any command afterwards is not executed.
Expected behavior
It can be seen in the grammar that it always requires the "path=" prefix before specifying the path, but it should be optional.
How to reproduce
Run the queries above.
Screenshots
Software version
6.1.0
Desktop (please complete the following information if relevant):
Additional context
The text was updated successfully, but these errors were encountered: