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
With CSV dataset
from addresses,cartesian_multipolygons,hosts| rename city.name as message | lookup join message_types_lookup on message | eval card = -6013949614291505456, hOntTwnVC = null, PQAF = null, DXkxCFXyw = null, number = -7336429038807752405 | eval dewAwHC = -1186293612, message = null | sort number ASC, street ASC, ip0 DESC, name ASC NULLS FIRST, host ASC | drop number, host_group, *umber, `city.country.continent.name`, dewAwHC, `zip_code`, `message`, city.country.continent.planet.name, `name`, `ip1`, message, zip_code | drop description, *e, id | keep `hOntTwnVC`, city.country.continent.planet.galaxy
DROP *e seems to work fine by itself, but as soon as we add another KEEP after that, the query starts failing
DROP *e
{ "error": { "root_cause": [ { "type": "verification_exception", "reason": "Found 1 problem\nline 1:542: No matches found for pattern [*e]" } ], "type": "verification_exception", "reason": "Found 1 problem\nline 1:542: No matches found for pattern [*e]" }, "status": 400 }
The text was updated successfully, but these errors were encountered:
Pinging @elastic/es-analytical-engine (Team:Analytics)
Sorry, something went wrong.
This issue can be reproduced using the simplified query below.
from test | eval first_name = 1 | drop first_name | drop *name | keep emp_no
DROP
Successfully merging a pull request may close this issue.
With CSV dataset
DROP *e
seems to work fine by itself, but as soon as we add another KEEP after that, the query starts failingThe text was updated successfully, but these errors were encountered: