-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DC-Specific indexing #67
Comments
I wrote a comment earlier about doing it on a per-node configuration basis, but that would complicate querying. So I will think a bit more about this. |
Ideally it could be enabled on a per-DC basis. That's the way that DSE
|
Okay the DC aware indexing seems possible, but would require a lot of testing. If there is readiness to help in testing, this can be implemented. |
It would help support mixed clusters if Stargate could index only in a specific DC, so for example the reporting DC could pay the secondary-index overhead for using Stargate without impacting the OLTP nodes.
Ideally, it would be nice to not need to have Stargate installed on the production OLTP nodes at all, but not sure if that's feasible.
The text was updated successfully, but these errors were encountered: