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
in_serial plugin read a stream of bytes, so the only thing is that user need to specify a delimiter string so the plugin can know when a message ends and a new one begins.
But, adding delimiter to JSON format is not suitable.
The request is that in_serial supports JSON Format.
The text was updated successfully, but these errors were encountered:
this patch add support for raw JSON messages over the serial
interface, it can receive multiple messages and parse them upon
arrival time.
Note this implementation (as of this patch) is still under development
as there is some issues with lib/jsmn. A bad former JSON message
may generate incorrect messages. I have logged an issue here:
zserge/jsmn#81
In order to enable JSON support the 'Format' property must to be set
with the 'json' value, e.g:
[INPUT]
Name serial
...
Format json
Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
The serial_json branch contains the implementation of this requested feature. As described in the 7d4700e commit, there is an issue in the used lib/jsmn library when some bad formed JSON message is received.
The following issue have been logged with jsmn team:
in_serial plugin read a stream of bytes, so the only thing is that user need to specify a delimiter string so the plugin can know when a message ends and a new one begins.
But, adding delimiter to JSON format is not suitable.
The request is that in_serial supports JSON Format.
The text was updated successfully, but these errors were encountered: