Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telematic messaging server: Partial write failure field type conflict with input field payload.MessageFrame.value.PersonalSafetyMessage.id #160

Merged
merged 1 commit into from
Nov 29, 2023

Conversation

dan-du-car
Copy link
Collaborator

@dan-du-car dan-du-car commented Nov 28, 2023

PR Details

Description

Collect PSM data from v2xhub, and stream it into the telematic tool. This data is eventually saved into influxDB. The influxDB creates fields and assigns data types based on the data values received. In the PSM message, payload.MessageFrame.value.PersonalSafetyMessage.id field was initially a float/number value, and influxDB created a number field type. However, payload.MessageFrame.value.PersonalSafetyMessage.id was randmonly generated 4 octet, it could populate characters in the payload.MessageFrame.value.PersonalSafetyMessage.id field beside numbers. This causes issue with influxDB when trying to save characters into a number field

Related Issue

#157

Motivation and Context

How Has This Been Tested?

Types of changes

  • Defect fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that cause existing functionality to change)

Checklist:

  • I have added any new packages to the sonar-scanner.properties file
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
    CDA Telematics Contributing Guide
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@dan-du-car dan-du-car changed the title ISSUE 157: Telematic messaging server: Partial write failure field type conflict with input field payload.MessageFrame.value.PersonalSafetyMessage.id Telematic messaging server: Partial write failure field type conflict with input field payload.MessageFrame.value.PersonalSafetyMessage.id Nov 29, 2023
is_ignored = true;
}
}
boolean is_processed = false;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a huge concern, but since we are processing all the fields, can we change this bool to something like is_str_cast?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we plan to add number_cast, we may reuse this bool

@adev4a adev4a merged commit 3f95f0a into develop Nov 29, 2023
20 of 26 checks passed
@adev4a adev4a deleted the ignore_fields branch November 29, 2023 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants