-
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
Remove reference to mapping types #23650
Comments
This comment has been minimized.
This comment has been minimized.
Awhile ago I did a full run of the functional test suite and logged every request the ES client makes to the .kibana index. This was the list of the unique routes I found that are using types in the path (obviously this only includes routes with test coverage; nothing too surprising here):
Of course I just now saw #23654, which pretty much covers all of these already. But figured I would post this info here anyway for posterity. |
Got a little ways down the road on this, and am currently blocked waiting for this: Currently, put mapping still expects you to provide the root-level type. That PR will fix this (and other inconsistencies). |
Follow-up to elastic#28497 Since elastic/elasticsearch#37285 has been merged, it's aparent there are a couple more places we need to specify include_type_name as a stop-gap until elastic#23650 is completed Signed-off-by: Tyler Smalley <[email protected]>
* [migrations] Fetch additional mappings with types Follow-up to #28497 Since elastic/elasticsearch#37285 has been merged, it's aparent there are a couple more places we need to specify include_type_name as a stop-gap until #23650 is completed Signed-off-by: Tyler Smalley <[email protected]> * Updates tests Signed-off-by: Tyler Smalley <[email protected]>
Pinging @elastic/infrastructure-ui |
Pinging @elastic/stack-monitoring |
Pinging @elastic/kibana-app |
Pinging @elastic/es-ui |
Pinging @elastic/kibana-qa |
Current list of failing tests, after the es archives were updated:
Pull that updates the archives: #28862 |
The context for this issue is in an email thread, but the TL;DR; is: I had a PR open that updated all es_archives, but I closed the PR after talking to some other teams who were independently working on fixing their own tests. It seems best to let each team fix their own slice of the app, including their es_archvies so that there wasn't a big nasty merge involved. |
We've moved forward with this, but are currently blocked by this issue: Elasticsearch is loading up index templates which create mappings with the wrong root types (e.g. 'doc' or whatever), so our tests fail when we attempt to create indices / load archives with @chrisronline is currently working around this by deleting all index templates prior to running the test suite. |
To expand on this a bit, Kibana is probably only affected by a subset of the templates listed in elastic/elasticsearch#37773. Due to the templates existing, we need to create hacks to delete the templates in our functional testing to proceed (monitoring example) |
Elasticsearch is taking the next step in working towards a world with no types. In 6.x, we enforced using a single type. In 7.0 we plan to offer APIs which do not require a type at all. Relevant APIs are indexing APIs, read APIs, and management APIs for things like index templates and mapping.
The plan is to take a two-step approach:
The text was updated successfully, but these errors were encountered: