-
Notifications
You must be signed in to change notification settings - Fork 25.6k
ESQL: Updated RENAME docs with the behaviour of multiple column renames #126462
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
Conversation
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add the new example to the rename.csv-spec file so it can be included in the commands docs once that automation is re-enabled (hopefully soon).
| With multiple `RENAME` commands: | ||
|
|
||
| ```esql | ||
| FROM employees |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not the same as the version in docs.csv-spec:104
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will be automating the inclusion of examples soon, so my PR will fix this, making it the same as the example in the csv-spec. If you prefer this two-line RENAME, then edit the example in the csv-spec
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait, I see now, this is the third example, and it does not exist at all in rename.csv-spec
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the example
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💔 Backport failed
You can use sqren/backport to manually backport by running |
…es (elastic#126462) * ESQL: Updated RENAME docs with the behaviour of multiple column renames * Added rename example to csv-spec
Update
RENAMEdocumentation after #122250