You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the problem including expected versus actual behavior:
Seems really important for debugging and lookup purposes to have the field name attached to a property. Maybe this could be stored in local metadata?. We use this heavily in Foundatio.Parsers for:
Getting server and local code mappings to resolve field names based on partial name matches.
Help with resolving FieldAliasProperty (seems really odd that FieldAliasProperty is missing the name).
this is a difficult one. In ES, property objects do not hold their names. They are always used as part of a dictionary (Properties type in the new client):
Keeping the property name as local metadata in the IProperty instance could easily cause inconsistencies if the same IProperty instance is added to multiple Properties dictionaries while using different names for the keys.
Would it help, if I add an additional method to the Properties dictionary type that allows to perform a reverse lookup? Something like:
Elastic.Clients.Elasticsearch version: 8.15.6
Elasticsearch version: 8.15.1
.NET runtime version: 8.x
Operating system version: Any
Description of the problem including expected versus actual behavior:
Seems really important for debugging and lookup purposes to have the field name attached to a property. Maybe this could be stored in local metadata?. We use this heavily in Foundatio.Parsers for:
Expected behavior
Being able to lookup properties by name
Reference: FoundatioFx/Foundatio.Parsers#84
The text was updated successfully, but these errors were encountered: