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
[ML] Inconsistent validation of detectors between Java and C++ #29843
Comments
Original comment by @tveasey: This needs updating on the Java side IMO: sum / non_null_sum are equivalent for population analysis. Arguably it would be cleaner to only support non_zero_count/non_null_sum for population analysis, but this will create backwards compatibility issues. I don't think this is confusing enough to warrant a breaking change. |
Original comment by @davidkyle: The docs also say non_null_sum cannot be used with an over field |
Original comment by @davidkyle: According to the docs these functions cannot be used with an over field by that isn't enforced in code.
|
Original comment by @droberts195: In the case of I agree that for the other 3 it’s better to change the validation in the Java code, due to BWC reasons. |
Original comment by @davidkyle: I updated the docs for |
Original comment by @davidkyle: Relates to LINK REDACTED |
Original comment by @davidkyle:
The x-pack plugin allows you to use the
non_null_sum
function with anover_field
But when you open the job autodetect rejects this configuration
bool CFieldConfig::isPopulation(EFunction function)
returns false for this functionResolve this conflict.
The text was updated successfully, but these errors were encountered: