Is your feature request related to a problem? Please describe.
Because user can give only one datacenter per project, in load balancing policy, So user "should" give all hosts from same region also.
So if they have multiple hosts from different region, they will be forced to create different project
Also even if it connects automatically, that's not good for few reasons, one that I can think of is it can connect to "worse" regions too.. especially in production
One of the use case that I can think of, is let's say in distributed production systems , with lets say some consistency level among Cassandra nodes, let's say "one", user should be able to say that for reading this time, read from this dc and for other time read from different dc, as data might be flowing to different regions in separate time
Even for other consistency levels , data might not be always consistent, and allowing users that power to choose - to which region to read from - based on some pipeline logic for feature engineering or materialization that user has written - is worth the trouble in my opinion.
Describe the solution you'd like
User should be able to decide what DataCenter they want to read from and single feature store can have multiple hosts
Describe alternatives you've considered
I don' think alternative exists.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
Because user can give only one datacenter per project, in load balancing policy, So user "should" give all hosts from same region also.
So if they have multiple hosts from different region, they will be forced to create different project
Also even if it connects automatically, that's not good for few reasons, one that I can think of is it can connect to "worse" regions too.. especially in production
One of the use case that I can think of, is let's say in distributed production systems , with lets say some consistency level among Cassandra nodes, let's say "one", user should be able to say that for reading this time, read from this dc and for other time read from different dc, as data might be flowing to different regions in separate time
Even for other consistency levels , data might not be always consistent, and allowing users that power to choose - to which region to read from - based on some pipeline logic for feature engineering or materialization that user has written - is worth the trouble in my opinion.
Describe the solution you'd like
User should be able to decide what DataCenter they want to read from and single feature store can have multiple hosts
Describe alternatives you've considered
I don' think alternative exists.
Additional context
Add any other context or screenshots about the feature request here.