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
Cloud Plugin: Allow to use the cloud as gateway storage #163
Comments
Implemented. |
rmuir
added a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
this removes a lot of obscure parsers, and leaves us with the basics. This includes at least all of the formats listed on elastic/elasticsearch-mapper-attachments#163 I will start adding tests for each one of these document formats, and take it as it goes and see what trouble we run into. Closes elastic#163
IanvsPoplicola
pushed a commit
to IanvsPoplicola/elasticsearch
that referenced
this issue
Mar 24, 2017
Claim issue elastic#3590 and release issue elastic#10795
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
same as https://bitbucket.org/engageli/devops/pull-requests/154 but for fabric Approved-by: Can Yildiz
costin
added a commit
that referenced
this issue
Dec 6, 2022
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow to use the cloud as gateway storage. This include Amazon S3, Rackspace CloudFiles, and Azure blob.
The configuration is simple:
There is also other properties that can be set on the gateway type, such as the location (east-1, west) that can be set.
A blob container (bucket in s3 terms) is created for the metadata, and for each index (both for the actual index files and the transaction log).
The text was updated successfully, but these errors were encountered: