-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[6.x] Move buildEsQuery to a package #26306
[6.x] Move buildEsQuery to a package #26306
Conversation
* fix: move buildEsQuery to utils * fix: tests that I broke * fix: add back link to the docs * fix: don't export from ui/ and link to utils * fix: move to a package * fix: move error to errors.js * fix: paths for peg task * fix: update reference to kuery * fix: build step for transpilation * fix: add typescript declaration file * fix: test * tmp: debug individual tests * debug: add debug stuff for reporting tests * try to debug test * Testing splitting reporting jobs in two * Testing splitting each job * Fix ci yaml * Skipping job to check failing test * debug - adding a catch to jobResponseHandler on report * Testing a different job and enabling verbose mode * Testing verbose on phantom_api skipping other CI tests * Fix script mode * fix: try running tests in chromium * fix: move out of devDependencies * fix: remove commented test * Revert "fix: try running tests in chromium" This reverts commit 991d46f. * Revert testing changes * Fixing build for phantomjs * Revert CI configuration to master. Remove verbose logging for tests
Pinging @elastic/kibana-app |
💚 Build Succeeded |
💚 Build Succeeded |
💚 Build Succeeded |
will this be merged any time soon or should I work around it? |
@weltenwort Just waiting on reviews. @Bargs @markov00 do either of you have time to give this a look? Or do you have time @weltenwort? |
I'm a bit swamped with stuff that has a deadline attached, sorry... I can use the old imports in my PR for now if you expect this to take a while |
💚 Build Succeeded |
Going to try to get to this in the next couple days |
…ana into backport/es-query-package
💔 Build Failed |
💚 Build Succeeded |
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.
The code that had to change for 6.x looks good. I also did a little smoke testing in Discover. KQL and lucene queries still work as do filters. I also verified that query_string
filters get decorated with query:queryString:options
. LGTM.
…ana into backport/es-query-package
💔 Build Failed |
Retest |
💚 Build Succeeded |
@weltenwort @sqren Did you want to check out this PR and ensure your usages are still working (in 6.x)? |
@lukasolson Sorry for not getting back to you before. I'll check this out tomorrow (Tuesday) |
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
Backports #23345 to 6.x.
This wasn't quite a clean backport because #15640 wasn't backported to 6.x, so we had to fix a couple of things manually.
The files that had to be manually fixed are the following:
Basically,
fromFilters
andfromLucene
now importdecorateQuery
instead of being passed it as an argument, and instead acceptconfig
as an argument, which they pass down todecorateQuery
.Since
buildOtherBucketAgg
historically sent a noop asdecorateQuery
intofromFilters
, it doesn't need to pass anyconfig
, sodecorateQuery
was updated to check ifconfig
is passed in, and only if it is, to decorate the query with the query string options from the config.