analyze_sentiment API for Dutch language is returning empty response

[zubair ahmed]

analyze_sentiment API of Google Natural Language for Dutch language is returning empty response. even if Dutch language is supported for Sentiment Analysis as per Documentation.

Even tried using the 'Try the API' section on Cloud Natural Language Page, it did not work here as well. please find the screenshot attached. 

For other languages such as 'spanish',  'French' and "German' the API is working fine as expected, The issue is only with languages such as 'Dutch' and 'Vietnamese'

Is the Dutch (nl) language actually supported for sentiment analysis using google natural language API as mentioned in the documentation?

Kindly Help.

Thanking in advance.

Regards,

Zubair Gazzali

[Hu (Google Cloud Platform Support)]

Hi Zubair,

Can you refer to this guide to open Public Issue Report (PIT) for this issue? So that the issue will report to the respective product team.

[rmir]

Hi Zubair,

To complement the previous answer, this is a known issue that the product team is currently working on fixing.

As far as I know it affects Vietnamese, Polish and Dutch. 

You have this [1] public issue already open that tracks the polish sentiment analysis issue. As the three languages sentiment analysis issues are related to the same issue, fixing one should fix the others. 

You can “star” [2] that issue to get updated when it gets fixed or any significant updates are posted in the thread.

---

[1] https://issuetracker.google.com/159562010 

[2] https://developers.google.com/issue-tracker/guides/subscribe#subscribing_by_starring_an_issue 

[Björn Van der Auwera]

Am I correct that the issue is not solved yet?

I'm also still getting empty responses.

Op donderdag 31 december 2020 om 15:04:34 UTC+1 schreef rmir:

[ivanasharma]

Hello,

Yes, you are right. As you can see in the public feature report[1] opened, the request has been assigned to the dedicated team. However, there is no ETA for when this feature will be rolled out. 

As you are experiencing this issue, I would recommend you to kindly up-vote on the public report[1] so that the engineering team can be notified of how many users are being affected by this issue. 

Thank you. 

[1]  https://issuetracker.google.com/159562010