Overall, the Avro support in dapr doesn't really have support for logicalType and will only consider the type... This is the same as for date/datetime. The type is int/long and the logicalType is not leveraged to convert to the JSON. They will be sent as the corresponding JSON type int/long...
So it's not a bug but the way it works today..

Thank you for the reply. At least I can change it to feature request, do you agree?

Well it's down to the avro library implementation. We use goavro. The more prevalent hamba/avro is not a good option because it doesn't support avro/standard Json conversion. It only expects go native types. To make it all work with dapr we have to go through JSON as the lowest common denominator.

In the current implementation, we go from standard Json to avro as opposed to avro Json which has higher type accuracy.
Maybe we could introduce an option to use avro Json which would most likely offer higher accuracy of types (to be tested).

I could create a branch for you to test locally

Actually this is an issue for the component-contrib repo, not the dapr one. Please close this one and create one on the appropriate repo.

Thank you for moving the issue to the proper repository. I haven't had time recently and now I see it is already done.

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.