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

SQL: Make FULL non-reserved keyword in the grammar #37377

Merged
merged 1 commit into from Jan 11, 2019

Conversation

matriv
Copy link
Contributor

@matriv matriv commented Jan 11, 2019

Since full can be common as a field name or part of a field name
(e.g.: full.name or name.full), it's nice if it's not a reserved
keyword of the grammar so a user can use it without resorting to quotes.

Fixes: #37376

Since `full` can be common as a field name or part of a field name
(e.g.: `full.name` or `name.full`), it's nice if it's not a reserved
keyword of the grammar so a user can use it without resorting to quotes.

Fixes: elastic#37376
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search

@matriv
Copy link
Contributor Author

matriv commented Jan 11, 2019

@costin do you think we should backport it to earlier version too?

Copy link
Member

@costin costin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - and the test is a good asset.

Let's back port this to 6.6.x as well

@matriv matriv added the v6.6.0 label Jan 11, 2019
@matriv matriv merged commit 359222c into elastic:master Jan 11, 2019
@matriv matriv deleted the mt/fix-37376 branch January 11, 2019 21:08
matriv added a commit that referenced this pull request Jan 11, 2019
Since `full` can be common as a field name or part of a field name
(e.g.: `full.name` or `name.full`), it's nice if it's not a reserved
keyword of the grammar so a user can use it without resorting to quotes.

Fixes: #37376
@matriv
Copy link
Contributor Author

matriv commented Jan 11, 2019

Backported to 6.x with 764da16

matriv added a commit that referenced this pull request Jan 11, 2019
Since `full` can be common as a field name or part of a field name
(e.g.: `full.name` or `name.full`), it's nice if it's not a reserved
keyword of the grammar so a user can use it without resorting to quotes.

Fixes: #37376
@matriv
Copy link
Contributor Author

matriv commented Jan 11, 2019

Backported to 6.6 with b71d503

jasontedor added a commit to jasontedor/elasticsearch that referenced this pull request Jan 12, 2019
…rsistence

* elastic/master:
  Fix PrimaryAllocationIT Race Condition (elastic#37355)
  SQL: Make `FULL` non-reserved keyword in the grammar (elastic#37377)
  SQL: [Tests] Fix and enable internalClusterTests (elastic#37300)
  ML: Fix testMigrateConfigs  (elastic#37373)
  Fix RollupDocumentation test to wait for job to stop
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants