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
When a collect type (monoInstance or multiInstance) is not specified in a job within the connector, the custom JsonDeserializer improperly computes the node key during its traversal from the source node to the root node. This leads to an incorrect node keys for the source objects, such as ${source::monitors.system.collect.mapping.sources.source_1}, instead of the expected ${source::monitors.system.collect.sources.source_1}.
The text was updated successfully, but these errors were encountered:
* Source keys are now generated at the pre processing phase.
* Added unit tests.
* Fixed failed unit tests.
* Removed keys retrieval method from the AbstractMapDeserializer class.
* Source keys are now generated at the pre processing phase.
* Added unit tests.
* Fixed failed unit tests.
* Removed keys retrieval method from the AbstractMapDeserializer class.
* Source keys are now generated at the pre processing phase.
* Added unit tests.
* Fixed failed unit tests.
* Removed keys retrieval method from the AbstractMapDeserializer class.
…keys-are-incorrectly-generated-when-the-collect-type-is-not-defined-in-the-connector
Issue #131: Fixed incorrect source keys when collect type is undefined
Problem
When a collect type (
monoInstance
ormultiInstance
) is not specified in a job within the connector, the customJsonDeserializer
improperly computes the node key during its traversal from the source node to the root node. This leads to an incorrect node keys for the source objects, such as${source::monitors.system.collect.mapping.sources.source_1}
, instead of the expected${source::monitors.system.collect.sources.source_1}
.The text was updated successfully, but these errors were encountered: