ae3e8beca4
filtered query parses _name incorrectly
...
fixes #4960
2014-01-30 21:32:52 +01:00
dddfe23bed
Randomized number of shards / replicas & add mapping for numeric fields
2014-01-30 20:42:31 +01:00
cd9be4364f
Improve boolean handling in snapshot/restore request parsing
...
Fixes #4949
2014-01-30 13:16:53 -05:00
7e1eed9814
The forceful no cache behaviour for range filter with now date match expression should only be active if no rounding has been specified for `now` in the date range range expression (for example: `now/d`).
...
Also the automatic now detection in range filters is overrideable by the `_cache` option.
Closes #4947
Relates to #4846
2014-01-30 15:51:33 +01:00
abf9a86678
Add version to plugins
...
Plugin developpers can now add a version number to their es-plugin.properties file:
```properties
plugin=org.elasticsearch.test.integration.nodesinfo.TestPlugin
version=0.0.7-SNAPSHOT
```
Also, for site plugins, it's recommended to add a `es-plugin.properties` file in root site directory with `description` and `version` properties:
```properties
description=This is a description for a dummy test site plugin.
version=0.0.7-BOND-SITE
```
When running Nodes Info API, you will get information on versions:
```sh
$ curl 'http://localhost:9200/_nodes?plugin=true&pretty '
```
```javascript
{
"ok" : true,
"cluster_name" : "test-cluster-MacBook-Air-de-David.local",
"nodes" : {
"RHMsToxiRcCXwHiS6mEaFw" : {
"name" : "node2",
"transport_address" : "inet[/192.168.0.15:9301]",
"hostname" : "MacBook-Air-de-David.local",
"version" : "0.90.0.Beta2-SNAPSHOT",
"http_address" : "inet[/192.168.0.15:9201]",
"plugins" : [ {
"name" : "dummy",
"version" : "0.0.7-BOND-SITE",
"description" : "This is a description for a dummy test site plugin.",
"url" : "/_plugin/dummy/",
"site" : true,
"jvm" : false
} ]
},
"IKiUOo-LSCq1Km1GUhBwPg" : {
"name" : "node3",
"transport_address" : "inet[/192.168.0.15:9302]",
"hostname" : "MacBook-Air-de-David.local",
"version" : "0.90.0.Beta2-SNAPSHOT",
"http_address" : "inet[/192.168.0.15:9202]",
"plugins" : [ {
"name" : "test-plugin",
"version" : "0.0.7-SNAPSHOT",
"description" : "test-plugin description",
"site" : false,
"jvm" : true
} ]
},
"H64dcSF2R_GNWh6XRCYZJA" : {
"name" : "node1",
"transport_address" : "inet[/192.168.0.15:9300]",
"hostname" : "MacBook-Air-de-David.local",
"version" : "0.90.0.Beta2-SNAPSHOT",
"http_address" : "inet[/192.168.0.15:9200]",
"plugins" : [ ]
},
"mGEZcYl8Tye0Rm5AACBhPA" : {
"name" : "node4",
"transport_address" : "inet[/192.168.0.15:9303]",
"hostname" : "MacBook-Air-de-David.local",
"version" : "0.90.0.Beta2-SNAPSHOT",
"http_address" : "inet[/192.168.0.15:9203]",
"plugins" : [ {
"name" : "test-plugin",
"version" : "0.0.7-SNAPSHOT",
"description" : "test-plugin description",
"site" : false,
"jvm" : true
}, {
"name" : "test-no-version-plugin",
"version" : "NA",
"description" : "test-no-version-plugin description",
"site" : false,
"jvm" : true
}, {
"name" : "dummy",
"version" : "NA",
"description" : "No description found for dummy.",
"url" : "/_plugin/dummy/",
"site" : true,
"jvm" : false
} ]
}
}
}
```
Relative to #2668 .
Closes #2784 .
2014-01-30 14:13:46 +01:00
2c67ba8f1a
REST Get Field Mapping API: Fix NPE if field not existent
...
When fixing #4738 , a small issue leaked into the implementation.
The equals check in the RestAction only applied when the master node
returned the rest request, otherwise the object equality would not hold
due to being transferred over the wire and being deserialized into
another object (from and an equality point of view) than the
FieldMappingMetaData.NULL object - this could result in serialization
exceptions as an empty length bytes reference is used in toXContent.
2014-01-30 12:02:52 +01:00
79d1633dd6
fixed a bug where when executing on a single shard and sorting terms agg based on sub metric agg, the order (asc/desc) is not respected
...
- fixed tests for terms order
Closes #4951
2014-01-30 06:54:25 +01:00
4c06c533e8
Fix javadocs for DeleteResponse.isFound()
2014-01-29 22:29:05 -07:00
d3f2173ef9
fixed date_/histogram aggregation documentation - added documentation for the `min_doc_count` setting
...
Closes #4944
2014-01-29 20:55:26 +01:00
2755eecf65
Add throttling to snaphost and restore operations
...
Closes #4855
2014-01-29 10:33:59 -05:00
0541456b34
scroll REST API should support source parameter
...
As stated in documentation, we should support `?source=` parameter in `/_search/scroll` REST operations.
This is how to reproduce it:
```sh
curl -XDELETE "http://localhost:9200/test "
curl -XPOST "http://localhost:9200/test/type/1 " -d'
{
"foo": "bar"
}'
# This one works
curl -XPOST "http://localhost:9200/_search/scroll " -d "FAKESCROLLID"
# This one gives: {"error":"Failed to derive xcontent from org.elasticsearch.common.bytes.BytesArray@0"}
curl -XGET "http://localhost:9200/_search/scroll/?source=FAKESCROLLID "
```
Closes #4941 .
2014-01-29 14:43:36 +01:00
c900ec2152
[TEST] Fixed whitespace in cluster.state/20_filtering.yaml
2014-01-29 13:33:29 +01:00
2b80c752df
Remove waiting for green in CopyToMapperIntegrationTests
2014-01-29 07:29:35 -05:00
c82f27577b
Added dedicated thread pool cat api, that can show all thread pool related statistic (size, rejected, queue etc.) for all thread pools (get, search, index etc.)
...
By default active, rejected and queue thread statistics are included for the index, bulk and search thread pool.
Other thread statistics of other thread pools can be included via the `h` query string parameter.
Closes #4907
2014-01-29 13:25:06 +01:00
a0e381ad3a
Improve test stability
2014-01-29 07:14:27 -05:00
9f04e5fe38
fixed nested example response in docs
...
Closes #4935
2014-01-29 13:09:12 +01:00
2de0e60342
Wait for green after indexing doc, so that the mapping update is always after the index operation on replica has completed. (replica shard may needed to catch up)
2014-01-29 12:10:17 +01:00
aadcfa7b51
Updated URLs to include 1.x and 1.0 snapshots
...
This file is used by elasticsearch client jerkin projects
2014-01-28 10:59:50 -08:00
d621ab9958
Fix potential NPE when no source and no body
...
In recent changes, we added missing support for `source` parameter in some REST APIs:
* #4892 : mget
* #4900 : mpercolate
* #4901 : msearch
* #4902 : mtermvectors
* #4903 : percolate
```java
BytesReference content = null;
if (request.hasContent()) {
content = request.content();
} else {
String source = request.param("source");
if (source != null) {
content = new BytesArray(source);
}
}
```
It's definitely better to have:
```java
BytesReference content = request.content();
if (!request.hasContent()) {
String source = request.param("source");
if (source != null) {
content = new BytesArray(source);
}
}
```
That said, it could be nice to have a single method to manage it for various REST actions.
Closes #4924 .
2014-01-28 18:15:27 +01:00
dd389d1cc5
Made all multi-bucket aggs return consistent response format
...
Closes #4926
2014-01-28 17:46:57 +01:00
f9d1552282
Use #ensureSearchable() in GeoHashGridTests
2014-01-28 15:11:49 +01:00
25f0bba30c
Use num of actual threads if busiestThreads is larger
...
We currently use the number of hot threads that we are
interested in as the value for iterating over the actual
hot threads which can lead to AIOOB is the actual number
of threads is less than the given number.
Closes #4927
2014-01-28 14:23:42 +01:00
2ba2fb193d
fixed compilation error on jdk7
2014-01-28 14:12:51 +01:00
b21b7ac40f
Make test more reliable
2014-01-28 13:32:34 +01:00
fc6bc4c477
cleanup of aggregations api
...
- add javadocs
- remove Iterable from all multi-bucket aggregations
- all single-bucket aggregations should have getDocCount() and getAggregations()
- all multi-bucket aggregations should have getBuckets() that returns Collection
- every multi-bucket aggregation should have these methods:
- getBuckets() : Collection
- getBucketByKey(String) : Bucket
- getBucketByKey(Number) : Bucket (only for numeric buckets)
- getBucketByKey(DateTime) : Bucket (only for date buckets)
- getBucketByKey(GeoPoint) : Bucket (only for geohash_grid)
- every bucket in all multi-bucket aggregations should have these methods:
- getKey() : String
- getKeyAsText() : Text
- getKeyAsNumber() : Number (if the key can be numeric value, eg. range & histograms)
- getKeyAsGeoPoint() : GeoPoint (in case of the geohash_grid agg)
Closes #4922
2014-01-28 13:28:04 +01:00
b61ca9932a
[DOCS] Clarified docs for cluster.routing.allocation.same_shard.host cluster setting
...
Clarified also javadocs for SameShardAllocationDecider
2014-01-28 12:32:37 +01:00
cb75830c68
Fixed failure for testDeletePercolatorType where the .percolator mapping hasn't propagated to master that was dynamically created via an index call, which made the delete mapping call fail.
2014-01-28 11:19:57 +01:00
b5a6a5a6ed
Ignore internal errors if JVM can't find the memory pool
2014-01-28 11:11:41 +01:00
215df2e52f
foreground mode is now the default, s/lets/let's/
2014-01-28 11:07:20 +01:00
91acca7836
Upgrade to Lucene 4.6.1
...
This upgrade includes a fix for RAM estimation on IndexReader
that allows to expose the amount of used bytes per segment now
as a setting in Elasticsearch. (LUCENE-5373)
Additionally this bugfix release contained a small fix for highlighting
that was already ported to Elasticsearch when reported (LUCENE-5361)
Closes #4897
2014-01-28 10:35:39 +01:00
1da5f3af67
Fix for #4902
2014-01-28 10:12:32 +01:00
6aaddb03f1
Changed p/c benchmarks to use random generated parent ids, index parent and its children in a non deterministic order and let query values match with multiple child / parent documents.
2014-01-28 10:11:00 +01:00
8706cf610a
percolate REST API should support source parameter
...
As stated in documentation, we should support `?source=` parameter in percolate REST operations.
This is how to reproduce it:
```sh
curl -XDELETE "http://localhost:9200/test "
curl -XPUT "http://localhost:9200/test/.percolator/1 " -d'
{
"query" : {
"match" : {
"foo" : "bar"
}
}
}'
# This one works
curl -XPOST "http://localhost:9200/test/message/_percolate " -d '{
"doc" : {
"foo" : "bar is in foo"
}
}'
# This one gives: BroadcastShardOperationFailedException[[test][2] ]; nested: PercolateException[failed to percolate]; nested: ElasticsearchIllegalArgumentException[Nothing to percolate];
curl -XGET "http://localhost:9200/test/message/_percolate?source=%7B%22doc%22%3A%7B%22foo%22%3A%22bar%20is%20in%20foo%22%7D%7D "
```
Closes #4903 .
2014-01-28 09:43:28 +01:00
71b8876d83
mtermvectors REST API should support source parameter
...
As stated in documentation, we should support `?source=` parameter in msearch REST operations.
This is how to reproduce it:
```sh
curl -XDELETE "http://localhost:9200/test "
curl -XPOST "http://localhost:9200/test/type/1?refresh " -d'{
"foo": "bar"
}'
# This one works
curl -XPOST "http://localhost:9200/test/type/_mtermvectors " -d'
{
"ids" : ["1"]
}'
# This one gives: "ActionRequestValidationException[Validation Failed: 1: multi term vectors: no documents requested;]"
curl -XGET "http://localhost:9200/test/type/_mtermvectors?source=%7B%22ids%22%3A%5B%221%22%5D%7D "
```
Closes #4902 .
2014-01-28 09:40:35 +01:00
bf3d20eb05
msearch REST API should support source parameter
...
As stated in documentation, we should support `?source=` parameter in msearch REST operations.
This is how to reproduce it:
```sh
curl -XDELETE "http://localhost:9200/test "
curl -XPOST "http://localhost:9200/test/type/1?refresh " -d'{
"foo": "bar"
}'
cat requests
{}
{"query" : {"match_all" : {}}}
# This one works
curl -XGET localhost:9200/_msearch --data-binary @requests
# This one gives: {"error":"Failed to derive xcontent from org.elasticsearch.common.bytes.BytesArray@0"}
curl -XGET "http://localhost:9200/test/type/_mget?source=%7B%7D%0A%7B%22query%22%3A%7B%22match_all%22%3A%7B%7D%7D%7D%0A "
```
Closes #4901 .
2014-01-28 09:39:44 +01:00
03c02143dd
mpercolate REST API should support source parameter
...
As stated in documentation, we should support `?source=` parameter in mpercolate REST operations.
This is how to reproduce it:
```sh
curl -XDELETE "http://localhost:9200/test "
curl -XPUT "http://localhost:9200/test/.percolator/1 " -d'
{
"query" : {
"match" : {
"foo" : "bar"
}
}
}'
# This one works
curl -XPOST "http://localhost:9200/test/message/_mpercolate " -d '
{"percolate" : {}}
{"doc" : {"foo" : "bar is in foo"}}
'
# This one gives: BroadcastShardOperationFailedException[[test][2] ]; nested: PercolateException[failed to percolate]; nested: ElasticsearchIllegalArgumentException[Nothing to percolate];
curl -XGET "http://localhost:9200/test/message/_mpercolate?source=%7B%22percolate%22%3A%7B%7D%7D%0A%7B%22doc%22%3A%7B%22foo%22%3A%22bar is in foo%22%7D%7D%0A"
```
Closes #4900 .
2014-01-28 09:38:30 +01:00
5e58f4066e
REST API: Consistent get field mapping response
...
If a get field mapping request is issued, and all but the field can be
found, the response should return an empty JSON object instead of a 404.
Closes #4738
2014-01-28 08:12:53 +01:00
d9699e02f4
Changed GeoEncodingTests to ensure accuracy always >1mm due to rounding errors with very small numbers
2014-01-27 17:05:19 +00:00
95bf091dd6
[DOCS] unified index settings info and added warmers section in create index docs
2014-01-27 17:10:38 +01:00
f38296da61
Percolator response now always returns the `matches` key.
...
Closes #4881
2014-01-27 16:37:09 +01:00
04c41fe349
Add missing PHRASE flag for simple_query_string
...
Closes #4911
2014-01-27 07:18:32 -07:00
da1e3ed8fc
[TEST] Added REST tests for create index api
2014-01-27 14:50:04 +01:00
2ad7f2b8a6
Improved CreateIndexRequest and CreateIndexRequestBuilder javadocs
2014-01-27 14:50:04 +01:00
c4edf15633
[TEST] Improved IndexAliasesTests
...
more assertAcked, removed TODO and needless sleep
2014-01-27 14:50:04 +01:00
c1c2d343c4
move msearch to use atomic array instead of synchronize
2014-01-27 13:22:49 +01:00
24abb6cf3f
Cluster state toXContent serialization only returns needed data
...
In order to make sure, that only the requested data is returned to the client,
a couple of fixes have been applied in the ClusterState.toXContent() method.
Also some tests were added to the yaml test suite
Closes #4885
2014-01-27 12:04:57 +01:00
35e5432354
Bulk: Failed preparsing does not fail whole bulk request
...
If a preparsing of the source is needed (due to mapping configuration,
which extracts the routing/id value from the source) and the source is not
valid JSON, then the whole bulk request is failed instead of a single
BulkRequest.
This commit ensures, that a broken JSON request is not forwarded to the
destination shard and creates an appropriate BulkItemResponse, which
includes a failure.
This also implied changing the BulkItemResponse serialization, because one
cannot be sure anymore, if a response includes an ID, in case it was not
specified and could not be extracted from the JSON.
Closes #4745
2014-01-27 11:33:41 +01:00
09575eb95f
Revert mget yaml test changes
...
Relative to #4892
2014-01-27 11:28:32 +01:00
fdbdb705b9
Revert mget yaml test changes
...
Relative to #4892
2014-01-27 11:25:39 +01:00
4c50770a89
mget REST API should support source parameter
...
As stated in documentation, we should support `?source=` parameter in mget REST operations.
This is how to reproduce it:
```sh
curl -XDELETE "http://localhost:9200/test "
curl -XPOST "http://localhost:9200/test/type/1?refresh " -d'{
"foo": "bar"
}'
curl -XPOST "http://localhost:9200/test/type/_mget " -d'{
"ids": ["1"]
}'
curl -XGET "http://localhost:9200/test/type/_mget?source=%7B%22ids%22%3A%20%5B%221%22%5D%7D "
```
Closes #4892 .
2014-01-27 11:05:50 +01:00
Shay Banon
Simon Willnauer
Mark Conlin
Martijn van Groningen
David Pilato
Alexander Reelsen
uboness
Lee Hinman
Igor Motov
Clinton Gormley
mrsolo
Luca Cavanna
Benjamin Devèze
markharwood