-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Memory estimation endpoint returns "0" for non-empty dataset. #49140
Comments
Pinging @elastic/ml-core (:ml) |
Turns out that although fields like Mapping:
Documents:
|
After talking to @dimitris-athanasiou, we agreed that the data extractor behavior is correct, i.e. the extractor should require all the analysable fields to exist for the outlier detection analysis (which does not support missing values). So in order to run the analysis correctly the user should exclude the missing fields explicitly from their analysis using:
In order to improve the UX, the memory estimation endpoint should throw early if it sees no analysable data so that the user is not confused that they receive "0" estimation. |
Dataset: barcelona_accidents
With the following request:
'_estimate_memory_usage' endpoint returns the following response:
Apparently problem lies in data extraction, as the following search query produced by data extractor yields no results:
It starts working fine, however if fields without a
doc.
prefix are removed from the query.The text was updated successfully, but these errors were encountered: