Cloud Plugin: Gateway should store meta data and indices under the same container #180
Comments
|
Cloud Plugin: Gateway should store meta data and indices under the same container, closed by c7075c1. |
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
Filter out Hive 'virtual' columns Filter out Elasticsearch built-in types Change validation default to warn to cope with cases where the schema is incomplete Fix elastic#180
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…#180) Remove leftover ConcurrentRecorders flag/value Approved-by: ttang2
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
…r-hooks fix before/after integration hooks
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems like the restriction I thought was in place in S3 (others don't have restriction) regarding the number of files in a bucket has been removed. There is a restriction for number of buckets though, so creating a bucket for metadata, and 2 buckets per shard does not make sense.
Everything should be stored under the same bucket. With the option, on the index leve, to store it on a different bucket if configured.
Sadly, this breaks backward... . So a reindex should be done.
The text was updated successfully, but these errors were encountered: