Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Issue summary :
Documentation [1] specifies "builtin/latest" and "builtin/stable" as supported model options in the SDK and API . Cloud Vision accepts any string for the "model" field without validation or error indication. Responses lack model version information. Customer's testing yielded similar results for "stable" and "latest", raising questions about model usage. API usage history and logging do not clarify model version employed.
Customer's concern:
Is the "latest" model being correctly accessed and utilized? If an invalid model is specified, does the API have a defined fallback behavior (e.g., defaulting to "stable")?
Expected Behavior : Incorporate model version information in API responses for transparency. Update documentation to address model selection behavior and fallback mechanisms.
Request to the engineer:
Is it possible to implement model version validation and informative error handling in Cloud Vision API responses?
[1]https://cloud.google.com/vision/docs/release-notes#December_16_2022