It should be possible to leverage the work done for SUSE/Telemetry#26 to avoid unnecessary telemetry data item unmarshaling when processing received telemetry reports.
Currently we are unmarshaling the telemetry report JSON payload into an in-memory representation, and then marshaling the telemetry data item payloads to store then as unstructured telemetry data, or, if there is a storage transformation defined for the associated telemetry type, using the in-memory representation to extract the data to store in the structured representation.
However, we really should only be unmarshaling the telemetry data item payload into an in-memory representation if there is an associated telemetry type storage transformation, and otherwise we should be storing the telemetry data item JSON data blob untouched, as it was originally provided to the telemetry client that submitted it.
It should be possible to leverage the work done for SUSE/Telemetry#26 to avoid unnecessary telemetry data item unmarshaling when processing received telemetry reports.
Currently we are unmarshaling the telemetry report JSON payload into an in-memory representation, and then marshaling the telemetry data item payloads to store then as unstructured telemetry data, or, if there is a storage transformation defined for the associated telemetry type, using the in-memory representation to extract the data to store in the structured representation.
However, we really should only be unmarshaling the telemetry data item payload into an in-memory representation if there is an associated telemetry type storage transformation, and otherwise we should be storing the telemetry data item JSON data blob untouched, as it was originally provided to the telemetry client that submitted it.