Assigned
Status Update
Comments
nr...@google.com <nr...@google.com>
nr...@google.com <nr...@google.com> #2
Hello,
Thank you for reaching out.
This issue was forwarded to our product team. Please keep in mind that this issue has to be analyzed and considered by the product team and I can't provide you ETA for it to be delivered. However, you can keep track of the status by following this thread.
Kind Regards
st...@gmail.com <st...@gmail.com> #3
Is there any update on this issue?
nr...@google.com <nr...@google.com> #4
Hello,
Thank you for your patience.
Our product team is currently working on it. Once there will be an update it will be shared in this thread.
Kind Regards
st...@gmail.com <st...@gmail.com> #5
Are there any alternative solutions or workarounds that would allow us to access the pipeline run id? This functionality is useful for us to be able to correlate our predictions with the pipeline runs that created them. And that in turn can help analysis/troubleshooting.
br...@google.com <br...@google.com> #6
Hello,
Thank you for reaching out. Our internal team is handling the case. Unfortunately there are no updates about it. For now, please stay tune to this thread for updates.
Regards,
Description
This post is using machine translation. Sorry if it is difficult to understand.
Problem you have encountered:
I am using "DOCUMENT_TEXT_DETECTION".
If the "builtin/stable" model is changed to the "builtin/latest" model released on December 5, the recognition accuracy of Japanese may decrease.
Even if "ja" is specified for languageHints, hiragana and half-width katakana are sometimes recognized as kanji and the languageCode is sometimes "zh".
In "builtin/stable", setting languageHints changes the response, but in "builtin/latest", setting languageHints does not change the response.
Is the setting by languageHints not working?
This is the result of testing with "Try this method" in the Documentation Guide.
"2024年(令和06年)06月01日まで有効" is incorrectly recognized as "2024年(令和06年)06月01日下有効".
Request:
Response (excerpt):