Skip to content

Commit eadd8a0

Browse files
ESS-3357 Document how to convert boolean values after DRIO has stopped doing implicit conversion (#135)
* ESS-3357 Document how to convert boolean values
1 parent e13f231 commit eadd8a0

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

docs/user_guide/access_data.rst

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,14 @@ or contact support to restore it.
6868

6969
The time resolution of aggregated data is in ticks (1tick = 100 nanoseconds), while the time resolution of non-aggregated data is in nanoseconds. This may lead to discrepancies in data when comparing the two, and some datapoints might get lost when using aggregation to access data, in cases when there are multiple datapoints within the same 100 nanosecond range.
7070

71+
.. warning::
72+
73+
Regarding boolean values (true and false). A change in DRIO affects data ingested after approximately 10th of March 2025 10:00, booleans are no longer automatically converted to integer values 1 and 0.
74+
If this conversion is desried, it can be done manually where required by using the following code after downloading the data as shown above:
75+
76+
.. code-block:: python
77+
78+
timeseries.replace({True: 1, 'true': 1, 'True': 1, False: 0, 'false': 0, 'False': 0}, inplace=True)
7179

7280
.. tip::
7381
When handling high-frequency data and/or extended timespans, it is crucial to consider memory usage.

0 commit comments

Comments
 (0)