Skip to content
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

Closed
kimchy opened this issue May 7, 2010 · 1 comment
Closed

Cloud Plugin: Allow to use the cloud as gateway storage #163

kimchy opened this issue May 7, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented May 7, 2010

Allow to use the cloud as gateway storage. This include Amazon S3, Rackspace CloudFiles, and Azure blob.

The configuration is simple:

cloud:
    account: <Account ID Here>
    key: <Private Key Here>
    blobstore:
        type: s3 / cloudfiles / azureblob

gateway:
    type: cloud
    cloud:
        container: YourContainerNameHere

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).

@kimchy
Copy link
Member Author

kimchy commented May 7, 2010

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
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
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
Projects
None yet
Development

No branches or pull requests

1 participant