-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
Renaming an index / hotswapping / aliasing #21871
Comments
+ Proper field mapping update should be implemented. One of the advantages of noSQL is schema-less. I don't see how this is schemaless looking at 1-9 and all the manipulations I have to do if 1 tiny field wasn't "analyzerized" properly when it entered the database. In SQL, I'd do "ALTER TABLE MODIFY COLUMN" and I'm done. This thing should really be better in this regard, or at least close. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There should be a way to safely rename / revoke / reindex / manipulate an index.
Currently, I have to do the following:
3-4 transition is a race cond. If app is heavily writing to index, you're out of luck. Your index will be constantly created, you won't be able to even make an alias.
6-7 is a potential race condition.
To work around the problem, we need aliases to work with existing indexes.
Also, an index rename functionality should be implemented, so that entire 4-7 would not be needed.
The text was updated successfully, but these errors were encountered: