[
https://issues.apache.org/jira/browse/AVRO-3540?focusedWorklogId=784051&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-784051
]
ASF GitHub Bot logged work on AVRO-3540:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jun/22 06:36
Start Date: 23/Jun/22 06:36
Worklog Time Spent: 10m
Work Description: czf commented on code in PR #1728:
URL: https://github.com/apache/avro/pull/1728#discussion_r904632059
##########
lang/csharp/src/apache/main/Reflect/DotnetProperty.cs:
##########
@@ -67,7 +67,8 @@ private bool IsPropertyCompatible(Avro.Schema.Type schemaTag)
case Avro.Schema.Type.Array:
return typeof(IEnumerable).IsAssignableFrom(propType);
case Avro.Schema.Type.Map:
- return typeof(IDictionary).IsAssignableFrom(propType);
+ var dictionaryType = typeof(IDictionary);
+ return dictionaryType.IsAssignableFrom(propType) &&
propType.GenericTypeArguments[0] == typeof(string);
Review Comment:
Ideally if it implements IDictionary<TKey, TValue> and TKey can be
reasonably converted to string then it would be supported. Unfortunately its
not very straight forward to determine what a type implements without checking
all the interfaces on the type.
I noticed ConfigurationBinder has a
[FindOpenGenericInterface](https://github.com/dotnet/runtime/blob/main/src/libraries/Microsoft.Extensions.Configuration.Binder/src/ConfigurationBinder.cs#L732)
method that seems to do the trick
Issue Time Tracking
-------------------
Worklog Id: (was: 784051)
Time Spent: 2.5h (was: 2h 20m)
> .NET/C# Allow Reflect reader/writer to support Dictionaries keyed by
> something other than string
> ------------------------------------------------------------------------------------------------
>
> Key: AVRO-3540
> URL: https://issues.apache.org/jira/browse/AVRO-3540
> Project: Apache Avro
> Issue Type: Improvement
> Components: csharp
> Reporter: Christopher Fingar
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Currently the existing reflect code does not support converting other key
> types to string.
> My change provides an opt-in functionality using the default converters.
> This allows users to keep there existing code instead of converting types to
> use string keys.
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
