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

Optimize API: Allow to optimize index/indices #9

Closed
kimchy opened this Issue Feb 14, 2010 · 8 comments

Comments

Projects
None yet
2 participants
@kimchy
Member

kimchy commented Feb 14, 2010

Provide the ability to optimize an index or indices down to a provided number of segments.

@kimchy

This comment has been minimized.

Member

kimchy commented Feb 14, 2010

Optimize API: Allow to optimize index/indices. Closed by cfafb52.

@clintongormley

This comment has been minimized.

Member

clintongormley commented Feb 18, 2010

is this the correct usage for the options?

curl -XPOST http://127.0.0.2:9200/_optimize?onlyExpungeDeletes=1&flush=1&refresh=1

ta

clint

@kimchy

This comment has been minimized.

Member

kimchy commented Feb 18, 2010

Yes, except that the boolean parameters expect true, and not 1. Ohh wait, just pushed support for 1 as well for http parameters to indicate true :)

@kimchy

This comment has been minimized.

Member

kimchy commented Feb 18, 2010

By the way, I think I am also going to add support to provide all this parameters in the body of the request as a JSON (instead in the query string), what do you think?

@clintongormley

This comment has been minimized.

Member

clintongormley commented Feb 19, 2010

about you added support for true / 1 - please can you do that for the JSON as well. For instance:

{ query: {
        filteredQuery: {
                query: {............},
                explain: true      # should accept 1 here as well
}}

re adding the params to the JSON instead:

yes, that would make sense to me - for a wrapper like ElasticSearch.pm, it makes little difference having the params in one place or the other - it'd probably be easier to just deal with the JSON.

@kimchy

This comment has been minimized.

Member

kimchy commented Feb 20, 2010

Added support for 0 to represent false in all places where I parse JSON or http parameters. Will work later on getting support for JSON body as well.

@clintongormley

This comment has been minimized.

Member

clintongormley commented Feb 20, 2010

Hiya

Just had another thought about this:

By the way, I think I am also going to add support to provide all this
parameters in the body of the request as a JSON (instead in the
query string), what do you think?"

One request that wouldn't work so well is:

curl -XPUT 'http://127.0.0.2:9200/es_test/type_1/1?opType=create'  -d '
{
   "num" : 2,
   "text" : "foo"
}
'

because the entire JSON document represents the document being indexed, so slipping opType=create in there wouldn't work

clint

@kimchy

This comment has been minimized.

Member

kimchy commented Feb 20, 2010

Yes, I am referring currently only to requests that don't have a body. The one mentioned as the index/delete/create and search operations do not fall into this category. I need to think what a solution (if needed) for them will be.

kimchy added a commit that referenced this issue Jun 5, 2015

dadoonet added a commit that referenced this issue Jun 5, 2015

dadoonet added a commit that referenced this issue Jun 5, 2015

dadoonet added a commit that referenced this issue Jun 5, 2015

Update to GCE API 1.17.0-rc
Seen in #9, Google changed its APIs. We need to update as it previous version causes a `404` error.

Closes #12.
Closes #9.

dadoonet added a commit that referenced this issue Jun 9, 2015

dadoonet added a commit that referenced this issue Jun 9, 2015

Add plugin version in es-plugin.properties
With #2784, we can now add plugin version in `es-plugin.properties` file.

It will only be used with elasticsearch 1.0.0 and upper. No need to push it in 1.x branch.

Closes #9.

rahul1193 referenced this issue in rahul1193/elasticsearch Jan 19, 2017

ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue Dec 21, 2017

Remove electionValueForced (elastic#9)
* Remove electionValueForced
* Replace believed-unnecessary check with an assertion

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment