Skip to content

[#185] Modified datatype in the Sparkplug payload definition to use the DataType enumeration in the proto file #550

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
May 13, 2025
Merged

[#185] Modified datatype in the Sparkplug payload definition to use the DataType enumeration in the proto file #550

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion specification/src/main/asciidoc/chapters/Sparkplug_6_Payloads.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -300,7 +300,7 @@ message Payload {
optional string name = 1; // Metric name - Required in BIRTH messages, optional in DATA messages if using aliases
optional uint64 alias = 2; // Metric alias - tied to name on BIRTH and included in all later DATA messages
optional uint64 timestamp = 3; // Timestamp associated with data acquisition time - if omitted, the overall payload timestamp is assumed as the data acquisition time
optional uint32 datatype = 4; // DataType of the metric/tag value
optional DataType datatype = 4; // DataType of the metric/tag value
optional string source = 5; // Source for CMD messages if unique to the Metric (typically for forwarded writes in CMD messages)
optional bool is_historical = 6; // If this is historical data and should not update real time tag
optional bool is_transient = 7; // Tells consuming clients such as MQTT Engine to not store this as a tag
Expand Down
Loading