-
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
[elasticsearch] patch mappings that are missing types #12783
Conversation
* @property {Function} options.log a method for writing log messages | ||
* @property {string} options.indexName name of the index in elasticsearch | ||
* @property {Function} options.callCluster a function for executing client requests | ||
* @param {Array<Object>} options.types an array of objects with `name` and `mapping` properties |
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.
Should be @property
Switching between v5 and v6 partial mappings types:
|
Jenkins, test it |
The failure might be legit - re-running as it was a timeout. https://kibana-ci.elastic.co/job/elastic+kibana+pull-request+multijob-selenium/5950/console |
Here is the issue:
|
Any ideas as to how it's becoming a long? |
This is mostly a guess, but I think this issue with long -> integer is the result of our tests seeding the .kibana index before Kibana has been started up, so mappings haven't yet been created. Elasticsearch sees a numeric field and assumes long, and then it errors later when Kibana starts up and tries to set integer as the field type. |
jenkins, test this |
LGTM |
* [elasticsearch] patch mappings that are missing types * [elasticsearch/healthCheck] fix tests * fix doc typo * [tests/functional/dashboard] fix suite name * [es/healthCheck/ensureTypesExist] limit randomness a bit * [test/functional] update es archives with complete mappings (cherry picked from commit 929aa8e)
… (#12817) * [elasticsearch] patch mappings that are missing types * [elasticsearch/healthCheck] fix tests * fix doc typo * [tests/functional/dashboard] fix suite name * [es/healthCheck/ensureTypesExist] limit randomness a bit * [test/functional] update es archives with complete mappings (cherry picked from commit 929aa8e)
Because this pr is targetting compatibility with 5.6 I started in 5.x and will forward port it to 6.0
With the transition to using the
SavedObjectClient
for everything and maintaining compatibility with two index formats the front-end code that creates mapping types was brought into focus. Rather than port it to use theSavedObjectClient
, or continuing to use some sort of proxy, this change adds a step to the health check that determines if the kibana index has all of the types defined by the'mappings'
uiExport type.We will remove the type management from the front-end in another pr.