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

Jump to bottom

REST Create Index: Not taking JSON index settings into account unless wrapped in settings. #578

Closed
kimchy opened this issue Dec 29, 2010 · 2 comments
Closed

REST Create Index: Not taking JSON index settings into account unless wrapped in settings. #578

kimchy opened this issue Dec 29, 2010 · 2 comments
Labels
>bug v0.14.1 v0.15.0

Comments

@kimchy
Copy link
Member

kimchy commented Dec 29, 2010

Using JSON based settings does not work in 0.14 unless wrapped in settings.

This will not work:

curl -XPUT 'http://localhost:9200/test/' -d '
{
    "index" : { 
        "number_of_shards" : 3, 
        "number_of_replicas" : 0
    }
}'

And this will work:

curl -XPUT 'http://localhost:9200/test/' -d '
{
    "settings" : {
        "index" : { 
            "number_of_shards" : 3, 
            "number_of_replicas" : 0
        }
    }
}'

This bug happens as a result of the feature in 0.14 adding the ability to specify mappings in the REST index create request.

Yaml based settings still work.
@kimchy
Copy link
Member Author

kimchy commented Dec 29, 2010

Fixed.

@lukas-vlcek
Copy link
Contributor

Also the following works fine too:

curl -XPUT 'http://localhost:9200/test/' -d ' {
    settings : { number_of_shards : 3, number_of_replicas : 0 }
}

Note: you do not have to explicitly specify "index" section inside "settings". See #541

mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
Merged in dev/can/MPC-5208-backend1-jenkins-2022-04-04 (pull request e…
92c7073 
…lastic#578)

MPC-5208: Update jenkins agent AMI for backend1 build

Approved-by: Gideon Avida
Approved-by: fabien
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@dliappis
Improve resiliency in Vagrant workflow (elastic#578)
09a5b04 
A difference between the bare metal nightly environment groups and
the Vagrant workflow is the disk setup: while we try to simulate a
large disk `~20GiB` for `~/.rally/benchmarks/races` on the target
nodes, `/` is very limited to `10GiB`.

This is problematic on both the loaddriver and target nodes, as it can
fill up (esp on the target nodes) by gradlew operations when testing
nightly builds where ES is built from source.

This commit uses a separate add-on disk for `/var/lib/jenkins/.rally`
on all nodes and still mounts a separate add-on disk for
`/var/lib/jenkins/.rally/benchmarks/races`.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug v0.14.1 v0.15.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @lukas-vlcek