When enriching signals (e.g. events/messages) with extraFields, duplicate paths lead to not all fields to be enriched
#1826
Comments
thjaeckle
added a commit
that referenced
this issue
Nov 29, 2023
…objects both being included in selected fields
thjaeckle
added a commit
that referenced
this issue
Nov 29, 2023
#1826 fix JsonFieldSelectorTrie logic for objects and parts of those objects both being included in selected fields
thjaeckle
added a commit
that referenced
this issue
Nov 30, 2023
…objects both being included in selected fields
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using signal enrichment, e.g. in connections or websockets to receive additional fields to the actually changes ones, it leads to unexpected problems when e.g. selecting the following
extraFields:In this example,
{{feature:id}}would also resolve tooperationalMode.We encountered that in such a case, only the first field will be enriched, the
features/{{feature:id}}/properties/configurationwill be ignored. Changing the order does not make a difference.The cause is not yet really clear to me - maybe because of the
{{feature:id}}placeholder or maybe becauseconfiguration/modeis a part ofconfiguration.Has to be investigated in order to fix.
The text was updated successfully, but these errors were encountered: