-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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 use of XPackLicenseState::isAllowedByLicense
for ML models
#79811
Comments
Pinging @elastic/ml-core (Team:ML) |
@rjernst, the only user of this method is when we check the license level of a remote cluster. CCR ( Is there work in this area already in getting CCR to stop using I am not sure which feature we would be tracking regardless as the API calls + persistent tasks cover the actual feature usage, we are simply checking the license of the remote cluster. |
Thanks Ben, I realized I was thinking of the wrong method, I've corrected the title of this issue. I will fix the remote checkers (which I don't think need to actually be tracked). The one I meant for this issue to cover is the use in |
XPackLicenseState::isMachineLearningAllowedForOperationMode
XPackLicenseState::isAllowedByLicense
for ML models
@rjernst awesome, I will look into |
For trained models, there are both basic and platinum licenses allowed. We should track the feature usage check based on the license operation mode instead of using the underlying isAllowedByLicense. closes: #79811
XPackLicenseState is meant to be an opaque view of the current license level. The
LicensedFeature
class should be used to determine whether a feature is used, so that tracking is always. However, there are a few special methods on XPackLicenseState that currently avoid feature tracking. This issue is about one of those:isMachineLearningAllowedForOperationMode
.We should convert the one user of this method to using a proper
LicensedFeature
.The text was updated successfully, but these errors were encountered: