Add support for telemetry type specific tables #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the existing SCC hardware info blob as an example, implement a telemetry type specific transformation to store the data in the table specific to that telemetry type.
This new mechanism define row handlers matching the associated tables that can be used to process the received JSON blob and store it into the appropriate telemetry table, with a default handler that stores the JSON blob as a single field.
Reorganise the app code to move logically related code into the same files, and renamed some files to better reflect their content.
Updated the staging and subsequent processing of received telemetry reports to align with the expected background processing model that will be implemented at a later date.