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
Data deduplication by output-restructure normally takes all columns into account. For this reason the value.timeReceived is causing the same piece of data to be added as a separate line.
I suspect that previous from older versions of Fitbit connector, the current connector repeatedly downloads the same date range for the problematic topics. The inclusion of the value.timeReceived column during de-deduplication causes the data to appear multiple times in the output files.
Problem
For certain Fitbit topics on a client deployment, selected topics started showing duplicated data rows in output storage analogous to:
Note that Fitbit data recorded at the same time appears as a separate line; the only difference is the
value.timeReceived
.This was observed for the following Fitbit topics:
it was noted to NOT occur for the following Fitbit topics:
Some observations
value.timeReceived
is causing the same piece of data to be added as a separate line.value.timeReceived
column during de-deduplication causes the data to appear multiple times in the output files.1d
time period hard-coded in the request URL whereas others do not:The text was updated successfully, but these errors were encountered: