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
Since only one realtimeDataStore and one historyDataStore can be configured, why in MetricsDataController injection is a collection of stores instead of a single store instance.
I think it's better to inject a single instance. If the community agrees, you can assign this task to me. @tomsun28
The text was updated successfully, but these errors were encountered:
Hi, this is due to historical configuration. Although we can only configure one store, many users will configure multiple ones, or forget to turn off the default one, causing the operation to fail. So here we changed to inject multiple beans and then select one.
I think we can update it to inject only one instance.
And we need to discuss whether we need to start reporting errors when there is no bean when startup.
Hi, this is due to historical configuration. Although we can only configure one store, many users will configure multiple ones, or forget to turn off the default one, causing the operation to fail. So here we changed to inject multiple beans and then select one.
I think we can update it to inject only one instance. And we need to discuss whether we need to start reporting errors when there is no bean when startup.
from the documentation, it is possible to use only the real-time data storage and not the historical data repository.
since it's expected that no historical data repository is configured, I think it's good to give a warning at system startup if no historical data repository is configured
Question
Since only one realtimeDataStore and one historyDataStore can be configured, why in MetricsDataController injection is a collection of stores instead of a single store instance.
I think it's better to inject a single instance. If the community agrees, you can assign this task to me. @tomsun28
The text was updated successfully, but these errors were encountered: