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
This is in the reference of issue #8877 @clintongormley I agree that there are internal issue of deleting types but it is one of the widely used feature too. Since, if an index contains more than one type and you are not allowing the users to delete a single type from it, users are forced to re-index complete data of other types first in a new index. I think this features should be enabled with putting some constraints rather than completely removing it from elasticsearch. In any data store one should be able to delete a collection/table/type at any time.
The text was updated successfully, but these errors were encountered:
The reason why we removed the ability to delete types is that Lucene does not support removing fields. We could potentially add it back if we divorced mappings from types (as mentioned on #15613), but I suspect this would just change your problem from "Allow deletion of types" to "Allow deletion of fields", which we can't solve: it is a natural limitation of the data-structures that Lucene is using to store data.
This is in the reference of issue #8877
@clintongormley I agree that there are internal issue of deleting types but it is one of the widely used feature too. Since, if an index contains more than one type and you are not allowing the users to delete a single type from it, users are forced to re-index complete data of other types first in a new index. I think this features should be enabled with putting some constraints rather than completely removing it from elasticsearch. In any data store one should be able to delete a collection/table/type at any time.
The text was updated successfully, but these errors were encountered: