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)
Request for new functionality
View staffing
Description
This will create a public issue which anybody can view and comment on.
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered: There is api to fetch processors for each location - [1], this API is present in the discovery doc mentioned at [2]
[1]https://cloud.google.com/document-ai/docs/reference/rest/v1/projects.locations.processors/list
[2] https://documentai.googleapis.com/$discovery/rest?version=v1
In this same api which is pointed at [1], [2] there were no EU location resources returned even when correct eu location is passed.
To elaobrate further: Document AI has a regional service endpoint specifically for EU Resources.
For EU we have to use eu-documentai.googleapis.com endpoint to get 200 responses.
The request here is to add support for EU resources in a single endpoint -> documentai.googleapis.com
The expectation here is that there should not be any redirects with main url documentai.googleapis.com it should work based on the location parameter passed to it