honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-07 21:48:39 +00:00
Code Issues Packages Projects Releases Wiki Activity
11,908 Commits 7 Branches 6 Tags
Commit Graph

72 Commits

Author SHA1 Message Date
Ryan Ernst
b96bd201c1 Mappings: Lock down _id field 
There are two implications to this change.
First, percolator now uses _uid internally, extracting the id portion
when needed. Second, sorting on _id is no longer possible, since you
can no longer index _id. However, _uid can still be used to sort, and
is better anyways as indexing _id just to make it available to
fielddata for sorting is wasteful.

see #8143
closes #9842
 2015-02-24 14:26:22 -08:00
Colin Goodheart-Smithe
2753db4685 Scripting: Removed deprecated script parameter names 
This change removes the deprecated script parameter names ('file', 'id', and 'scriptField').
It also removes the ability to load file scripts using the 'script' parameter. File scripts should be loaded using the 'script_file' parameter only.
 2015-02-23 13:49:21 +00:00
Adrien Grand
4708227ecf Codecs: Remove the ability to have custom per-field postings and doc values formats. 
This commit makes the `postings_format` and `doc_values_format` options of
mappings illegal on 2.0 and ignored on 1.x (meaning that the default postings
and doc values formats from the codec will be used in such a case).

This removes a fair amount of code.

Close #8746 #9741
 2015-02-19 15:47:25 +01:00
Christoph Büscher
30fd70f07b Aggregations: Simplify time zone option in date_histogram 
Removed the existing `pre_zone` and `post_zone` option in `date_histogram` in favor of
the simpler `time_zone` option. Previously, specifying different values for these could
lead to confusing scenarios where ES would return bucket keys that are not UTC.
Now `time_zone` is the only option setting, the calculation of date buckets to take place in the
preferred time zone, but after rounding converting the bucket key values back to UTC.

Closes #9062
Closes #9637
 2015-02-16 16:54:06 +01:00
Ryan Ernst
533fdbdf75 Mappings: Remove support for field access by short name 
When multiple fields under object fields share the same name, accessing
by short name is ambiguous.  This removes support for short names,
always requiring the full name when used in queries.

closes #8872
 2015-02-12 09:58:37 -08:00
Christoph Büscher
d2f852a274 Aggregations: Add 'offset' option to date_histogram, replacing 'pre_offset' and 'post_offset' 
Add offset option to 'date_histogram' replacing and simplifying the previous 'pre_offset' and 'post_offset' options.
This change is part of a larger clean up task for `date_histogram` from issue #9062.
 2015-02-09 14:03:28 +01:00
Ryan Ernst
6079d88d43 Mappings: Remove type prefix support from field names in queries 
This is the first part of #8872.
 2015-02-02 13:10:56 -08:00
Colin Goodheart-Smithe
285ef0f06d Aggregations: Clean up response API for Aggregations 
This change makes the response API object for Histogram Aggregations the same for all types of Histogram, and does the same for all types of Ranges.
The change removes getBucketByKey() from all aggregations except filters and terms. It also reduces the methods on the Bucket class to just getKey() and getKeyAsString().
The getKey() method returns Object and the actual Type is returns will be appropriate for the type of aggregation being run. e.g. date_histogram will return a DateTime for this method and Histogram will return a Number.
 2015-01-27 10:53:44 +00:00
David Pilato
052645903a Rest: remove status code from main action 
Today we give the HTTP status back within the HTTP response itself and within the JSON response as well:

```sh
curl localhost:9200/
```

```js
{
  "status" : 200,
  "name" : "Red Wolf",
  "version" : {
    "number" : "2.0.0",
    "build_hash" : "6837a61d8a646a2ac7dc8da1ab3c4ab85d60882d",
    "build_timestamp" : "2014-08-19T13:55:56Z",
    "build_snapshot" : true,
    "lucene_version" : "4.9"
  },
  "tagline" : "You Know, for Search"
}
```
 2015-01-12 12:37:46 +01:00
Ryan Ernst
060f963a8e Mappings: Remove allow_type_wrapper setting 
Before Elasticsearch 1.0, the type was allowed to be passed as the root
element when uploading a document.  However, this was ambiguous if the
mappings also contained a field with the same name as the type.  The
behavior was changed in 1.0 to not allow this, but a setting was added
for backwards compatibility.  This change removes the setting for 2.0.
 2015-01-08 09:13:40 -08:00
Martijn van Groningen
ca4f27f40e Core: Added _shards header to all write responses. 
The header indicates to how many shard copies (primary and replicas shards) a write was supposed to go to, to how many
shard copies to write succeeded and potentially captures shard failures if writing into a replica shard fails.

For async writes it also includes the number of shards a write is still pending.

Closes #7994
 2015-01-08 18:10:08 +01:00
Martijn van Groningen
20f7be378b Removed parent parameter from update request, because it is just sets the routing. 
The routing option should be used instead. The parent a child document points to can't be updated.

Closes #4538
 2015-01-07 10:26:20 +01:00
Adrien Grand
bc86796592 Core: Remove terms filter cache. 
This is our only cache which is not 'exact' and might allow for stalled results.
Additionally, a similar cache that we have and needs to perform lookups in other
indices in order to run queries is the script index, and for this index we rely
on the filesystem cache, so we should probably do the same with terms filters
lookups.

Close #9056
 2015-01-06 17:21:20 +01:00
David Pilato
d2a2d1bb53 java: QueryBuilders cleanup: remove deprecated 
Related to #8667:

Some QueryBuilders have been deprecated in 1.x branches. We removed them in 2.0.

Removed
-------

* `textPhrase(...)`
* `textPhrasePrefix(...)`
* `textPhrasePrefixQuery(...)`
* `filtered(...)`
* `inQuery(...)`
* `commonTerms(...)`
* `queryString(...)`
* `simpleQueryString(...)`

Closes #8721.
 2014-12-03 16:07:34 +01:00
Adrien Grand
8346e92ebb Core: Fix script fields to be returned as a multivalued field when they produce a list. 
This change is essentially the same as #3015 but on script fields.

Close #8592
 2014-11-24 09:41:16 +01:00
Alex Ksikes
1959275622 Term Vectors: More consistent naming for term vector[s] 
We speak of the term vectors of a document, where each field has an associated
stored term vector. Since by default we are requesting all the term vectors of
a document, the HTTP request endpoint should rather be called `_termvectors`
instead of `_termvector`. The usage of `_termvector` is now deprecated, as
well as the transport client call to termVector and prepareTermVector.

Closes #8484
 2014-11-21 14:06:44 +01:00
Simon Willnauer
0fcb466555 [STORE] Remove memory/ ram store 
The RAM store is discuraged for production usage anyway and
we don't test it in our randomized infrastructure. This commit
removes it for `2.0`
 2014-11-20 14:47:19 +01:00
Colin Goodheart-Smithe
353574d6af Indices API: Fix GET index API always running all features 
Previous to this change all features (_alias,_mapping,_settings,_warmer) are run regardless of which features are actually requested. This change fixes the request object to resolve this bug
 2014-11-13 13:22:46 +00:00
Adrien Grand
9ea25df649 Switch to murmurhash3 to route documents to shards. 
We currently use the djb2 hash function in order to compute the shard a
document should go to. Unfortunately this hash function is not very
sophisticated and you can sometimes hit adversarial cases, such as numeric ids
on 33 shards.

Murmur3 generates hashes with a better distribution, which should avoid the
adversarial cases.

Here are some examples of how 100000 incremental ids are distributed to shards
using either djb2 or murmur3.

5 shards:
Murmur3: [19933, 19964, 19940, 20030, 20133]
DJB:     [20000, 20000, 20000, 20000, 20000]

3 shards:
Murmur3: [33185, 33347, 33468]
DJB:     [30100, 30000, 39900]

33 shards:
Murmur3: [2999, 3096, 2930, 2986, 3070, 3093, 3023, 3052, 3112, 2940, 3036, 2985, 3031, 3048, 3127, 2961, 2901, 3105, 3041, 3130, 3013, 3035, 3031, 3019, 3008, 3022, 3111, 3086, 3016, 2996, 3075, 2945, 2977]
DJB:     [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 900, 900, 900, 900, 1000, 1000, 10000, 10000, 10000, 10000, 9100, 9100, 9100, 9100, 9000, 9000, 0, 0, 0, 0, 0, 0]

Even if djb2 looks ideal in some cases (5 shards), the fact that the
distribution of its hashes has some patterns can raise issues with some shard
counts (eg. 3, or even worse 33).

Some tests have been modified because they relied on implementation details of
the routing hash function.

Close #7954
 2014-11-04 16:32:42 +01:00
Alex Ksikes
35f55608cc MLT Field Query: remove it from master 
The MLT field query is simply replaced by a MLT query set to specififc field.
To simplify code maintenance we should deprecate it in 1.4 and remove it in
2.0.

Closes #8238
 2014-10-29 10:19:00 +01:00
Adrien Grand
230c6684a9 Search: Remove partial fields. 
Partial fields have been deprecated since 1.0.0Beta1 in favor of _source
filtering. They will be removed in 2.0.
 2014-10-20 12:29:30 +02:00
Colin Goodheart-Smithe
9ce7ca21e4 Docs: Added breaking changes docs for Indices APIs 
Adds the breaking changes defaults for the change of default indices options for the GET Aliases API
 2014-10-08 15:08:25 +01:00