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
Describe the bug
When using Telemetry Extractor with the following configuration, a delimiter is placed after the final item on the first row. This is an issue with tools like SQLite's importer function. SQLite expects one more item to exist due to the final comma, and since it doesn't there's a null column appended to each item.
DELIMITER ","
DONT_OUTPUT_FILENAMES
Note: the examples here do not have a comma on the last item of the first row.
To Reproduce
Steps to reproduce the behavior:
Run Telemetry Extractor with the above configuration.
Extract a packet.
View the resulting file and note the final item also has a comma at the end of it.
Expected behavior
The final item of the first row shouldn't have a comma.
Environment (please complete the following information):
OS: Windows 10
COSMOS Version 4.4.2
The text was updated successfully, but these errors were encountered:
Describe the bug
When using Telemetry Extractor with the following configuration, a delimiter is placed after the final item on the first row. This is an issue with tools like SQLite's importer function. SQLite expects one more item to exist due to the final comma, and since it doesn't there's a null column appended to each item.
Note: the examples here do not have a comma on the last item of the first row.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The final item of the first row shouldn't have a comma.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: