Updating indexes for block
It adds a new cluster block for the index when the index.read_only setting is true.https://gist.github.com/f089f90787e5a691668d Having thought about this more... the above is a simplified description of upgrading, but maybe too simple.constructs an index on the specified column(s) of the specified table.Indexes are primarily used to enhance database performance (though inappropriate use can result in slower performance).But we would prefer to be able to set this on the server side, so we can make sure that not servers add documents by accident and we don't have these documents in the new index. 0.18 to 0.19): mark all indices read-only, take half the cluster offline and upgrade it, restart, and repeat for the other half.Because of the fact that shay mentioned in the Forum, I assume there won't be any performance gain. Searches can proceed against both halves so availability is maintained but no new new documents or deletes can occur in half while they are disconnected.I would also prefer if the index would not allow any changes as you described in the second part.
This feature can be used to obtain fast access to data based on some transformation of the basic data.
For example, if you have a table that contains both billed and unbilled orders where the unbilled orders take up a small fraction of the total table and yet that is an often used section, you can improve performance by creating an index on just that portion.
Another possible application is to use , that is, their results must depend only on their arguments and never on any outside influence (such as the contents of another table or the current time).
This patch seems to basically work as a proof of concept.
Of course, I don't know if this is the approach that should be taken--feel free to tell me it's completely wrong!
For many applications action.auto_create_index would be needed.