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
Is your feature request related to a problem? Please describe.
When a connection is lost for a long time, and restart again, it takes back the data from the last maxInstant retrieved. It retrieves first the oldest values instead of the most recent ones.
For some real time usages, it may be a problem
Describe the solution you'd like
On the south History settings, allow the user to select different recovery strategies:
From oldest to newest (default)
From newest to oldest (strategy to implement)
Alternate newest strategy and oldest strategy depending on the latency of the recovery (to implement later if needed)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When a connection is lost for a long time, and restart again, it takes back the data from the last maxInstant retrieved. It retrieves first the oldest values instead of the most recent ones.
For some real time usages, it may be a problem
Describe the solution you'd like
On the south History settings, allow the user to select different recovery strategies:
The text was updated successfully, but these errors were encountered: