Skip to content
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

Gemini controlled generation no longer supports schema fields that previously worked #4551

Open
adesso-dominik-chodounsky opened this issue Oct 15, 2024 · 0 comments
Labels
api: vertex-ai Issues related to the googleapis/python-aiplatform API.

Comments

@adesso-dominik-chodounsky

I am using Gemini's controlled generation function in one of my projects.
I use an OpenAPI schema with Vertex AI fields.

For one attribute, I had the following definition:
{"type": "string", "format": "date", "example": "2015-12-04"} which worked a few weeks ago, but currently results in:
InvalidArgument : 400 Unable to submit request because one or more response schemas specified unsupported field example.

If I remove the fields format and example, the whole generation works.

I cannot find release notes that would describe a change in this anywhere, did the support for this change? Both fields are specified in the Vertex AI Schema docs: https://cloud.google.com/vertex-ai/docs/reference/rest/v1/Schema,
but on the Controlled Generation page, they are largely limited: http://cloud.google.com/vertex-ai/generative-ai/docs/multimodal/control-generated-output#considerations

@product-auto-label product-auto-label bot added the api: vertex-ai Issues related to the googleapis/python-aiplatform API. label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: vertex-ai Issues related to the googleapis/python-aiplatform API.
Projects
None yet
Development

No branches or pull requests

1 participant