You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
Currently, ML Commons allows updating or deleting models without validation, which can lead to the following issues:
Deleting a model that is still in use, potentially breaking dependent processes.
Updating critical model configurations (e.g., embedding_dimension for a dense model), which may cause incompatibility with existing index configurations or stored embeddings.
What solution would you like?
To prevent these issues, we need a mechanism that tracks which resources are using a model and enforces validation before updates or deletions.
Model Deletion Rules
Before deleting a model:
Check if the model is currently in use.
If the model is in use, ensure it is properly unregistered and no longer referenced before proceeding with deletion.
Model Update Rules
Before updating a model:
Validate compatibility with existing usage.
If the update is incompatible, either:
Adjust dependencies to maintain compatibility.
Stop using the model before applying the update.
What alternatives have you considered?
N/A
Do you have any additional context?
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Currently, ML Commons allows updating or deleting models without validation, which can lead to the following issues:
What solution would you like?
To prevent these issues, we need a mechanism that tracks which resources are using a model and enforces validation before updates or deletions.
Model Deletion Rules
Before deleting a model:
Model Update Rules
Before updating a model:
What alternatives have you considered?
N/A
Do you have any additional context?
N/A
The text was updated successfully, but these errors were encountered: