-
-
Notifications
You must be signed in to change notification settings - Fork 821
Allow double equals in hive dialect #6623
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
Allow double equals in hive dialect #6623
Conversation
Coverage Results ✅
|
FROM | ||
t | ||
WHERE | ||
t.a = = t.b |
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.
Can you add a test case without the space? I just want to make sure this doesn't actually require a lexer change
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 replaced the spaced version as that one seemed odd (and was inadvertent). Let me know if you want both test cases.
|
||
match_grammar: Matchable = OneOf( | ||
Ref("RawEqualsSegment"), | ||
Sequence( |
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 can be simplified to a sequence with
Ref("RawEqualsSegment"),
Ref("RawEqualsSegment", optional=True),
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.
Done
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
Brief summary of the change made
Allows the use of a
==
in the hive sql dialect as a synonym of=
per https://cwiki.apache.org/confluence/display/Hive/Hive+Operatorsfixes #6622
Are there any other side effects of this change that we should be aware of?
None that I'm aware of
Pull Request checklist
Please confirm you have completed any of the necessary steps below.
Included test cases to demonstrate any code changes, which may be one or more of the following:
.yml
rule test cases intest/fixtures/rules/std_rule_cases
..sql
/.yml
parser test cases intest/fixtures/dialects
(note YML files can be auto generated withtox -e generate-fixture-yml
).test/fixtures/linter/autofix
.Added appropriate documentation for the change.
Created GitHub issues for any relevant followup/future enhancements if appropriate.