-
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
Move legacy/server/index_patterns -> src/plugins/data/server #46537
Move legacy/server/index_patterns -> src/plugins/data/server #46537
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
Pinging @elastic/kibana-app-arch |
jenkins, test this |
💔 Build Failed |
…IndexPatternsService
d635764
to
5315f22
Compare
@elasticmachine merge upstream |
@elasticmachine merge upstream |
...lugins/data/server/index_patterns/fetcher/lib/field_capabilities/field_caps_response.test.js
Outdated
Show resolved
Hide resolved
Jenkins test this |
@sainthkh seems like there's another reference to |
💔 Build Failed |
@elasticmachine merge upstream |
Jenkins test this |
@elasticmachine merge upstream |
Jenkins, test this |
💚 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.
Code changes look good.
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.
@sainthkh I'm still getting an error when navigating to APM application:
Could you add a test to catch this failure please?
@lizozom I found out that the bug has something to do with indexPatternsFetcher (because APM team decided to use it), but it wasn't introduced in this PR. After following the history, I found out that it was introduced in 46304f0. If you check out that commit and a10cf38 (the commit right below that), 404 error doesn't show on a10, but on 463. I guess it should be a separate issue and PR. |
@sainthkh I might be missing some context, but I cannot reproduce the 404 on master, if that is what you're suggesting. Can you? |
Yes, I found 404 on master.
Env: ubuntu 18.04. It's run from main kibana folder, not x-pack. If you cannot reproduce it, please let me know. I'll check it out again tomorrow. |
@dgieselaar @sainthkh I can confirm that this bug happens on |
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
@lizozom strange, I've not been able to reproduce it on any of our environments. Do you have any settings that are out of the ordinary? |
@dgieselaar nope just fresh out of the box setup. |
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.
404 is likely because of lack of APM indices. Not a concern. Verified the branch against clusters with APM indices and all seems fine.
…#46537) Dismissed @elastic/kibana-app review of import changes. ts-ignored @ts-ignore * Moved files to plugins/data/server. * Renamed IndexPatternsService to IndexPatternsFetcher and created new IndexPatternsService * Set routerPath. * Fixed type error. * Changed beats_management _fields_for_wildcard request with data/public/legacy api. * Fixed changed paths. * Fixes crashes after merge. * Updated path for clarity. * Applied Plugin interface to service. * Fixed test failure caused by non camel case local variable name. * Fixed import to IndexPatternsService to IndexPatternsFetcher.
…#50081) Dismissed @elastic/kibana-app review of import changes. ts-ignored @ts-ignore * Moved files to plugins/data/server. * Renamed IndexPatternsService to IndexPatternsFetcher and created new IndexPatternsService * Set routerPath. * Fixed type error. * Changed beats_management _fields_for_wildcard request with data/public/legacy api. * Fixed changed paths. * Fixes crashes after merge. * Updated path for clarity. * Applied Plugin interface to service. * Fixed test failure caused by non camel case local variable name. * Fixed import to IndexPatternsService to IndexPatternsFetcher.
Summary
Partially solves #44190.
legacy/server/index_patterns
tosrc/plugins/data/server
.IndexPatternsService
toIndexPatternsFetcher
. Becauseservice
s are classes used by plugins that havesetup()
,start()
,stop()
methods. It can cause confusion.IndexPatternsApiClient
apis fromIndexPatterns
class. And used it inx-pack/beats_management
.Note.
eslint
test will fail untilno-restricted-paths
bug is fixed in eslint no-restricted-path false positive: bug caused by dir names that start with "index". #46544.src/plugins
, the server-side_fields_for_wildcard
request inrollup
cannot be replaced withIndexPatternsFetcher
yet.Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.This was checked for cross-browser compatibility, including a check against IE11Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n supportDocumentation was added for features that require explanation or tutorialsThis was checked for keyboard-only and screenreader accessibilityFor maintainers