[ML-Dataframe] Register Data Frame named writables and xcontents #39569
Conversation
This file contains 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
|
Pinging @elastic/ml-core |
davidkyle
force-pushed
the
dataframe-missing-named
branch
from
818914b to
65bb192
Compare
davidkyle
added a commit
to davidkyle/elasticsearch
that referenced
this pull request
Mar 4, 2019
…stic#39569) Register types in the Dataframe plugin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Register missing Data Frame named writables and move the registration of Data Frame named xcontent objects from the Data Frame plugin to the XPackClientPlugin as is the style of the day.
The DataFrameTransform class was moved to core to facilitate this.
non-issue as unreleased code