forked from matthewfranglen/postgres-elasticsearch-fdw
-
Notifications
You must be signed in to change notification settings - Fork 1
ES Agg pushdown v2 #2
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
Merged
Merged
Changes from 4 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
f9f3b1f
Elasticsearch implementation of upper rel + qual clause pushdown combo
gruuya d36b629
Make scan query the default one even when empty
gruuya 2f2ed9f
Enable pushdown of COUNT(*)
gruuya 2499030
Fix PG pattern matching operator handling
gruuya ff95446
Implement proper patern match translation between PG and ES
gruuya 8ed1be1
Add list of supported operators by ES
gruuya f3dd1ea
Fix backslash esacpe pattern match variants
gruuya 4dfffd7
Escape special ES character when used in pattern matching
gruuya File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Ideally this would handle underscores (single-character match) and escapes (e.g.
\%
matches%
), so something like:%
(when not preceded by a single\
) becomes*
_
(when not preceded by a single\
) becomes?
\%
becomes%
(since it has no special meaning in ES wildcards)\_
becomes_
(same)It does become complex though. I'd be happy with us returning false positives (since PG will recheck and filter them out) but I don't know how to process the input LIKE pattern to get to a pattern that definitely over-matches instead of possibly under-matching (e.g. right now the
x LIKE 'a_ple'
won't matchapple
AFAIU)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.
Right, I think this should do it, let me add a couple of tests in the engine repo.
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.
Now that I think of it, I need to handle case like
\\%
(becomes\*
), and\\\%
(becomes\%
?).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.
\\%
in PG patterns means "backslash + any characters", so it'd become\\*
\\\%
means "backslash +%
", so it'd become\\%
(since%
has no special meaning)Uh oh!
There was an error while loading. Please reload this page.
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.
Got it, this should now be covered as well. Here are the corresponding tests.
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 also test / check that this escapes special ES pattern characters, e.g.:
*
becomes\*
?
becomes\?
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.
Good catch, added a fix and a test for these cases too.