Inability to Modify SpeechClient Endpoint in C++ Client Leads to Global Region Lock #13729
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Does this issue affect the google-cloud-cpp project?
Yes, the same operations execute successfully in the Python and Node.js clients, yet they encounter failure when attempted with the C++ client
What component of
google-cloud-cpp
is this related to?google/cloud/speech/v2
Describe the bug
When using the Google Cloud Speech-to-Text C++ client, it appears impossible to modify the SpeechClient endpoint to use a specific region, resulting in the client defaulting to the global region. This limitation does not exist in the Python and Node.js clients, where modifying the endpoint to target a specific region works as expected.
To Reproduce Steps to reproduce the behavior:
e.g.,
request.set_recognizer("projects/{project_id}/locations/asia-southeast1/recognizers/_");
Expected resource location to be global, but found asia-southeast1 in resource name.
Expected behavior
Successfully transcribed the audio file without any errors reported.
Operating system:
macOS 14.3.1
What compiler and version are you using?
Homebrew clang version 17.0.6
What version of
google-cloud-cpp
are you using?2.21.0
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: