2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2017-08-28 11:43:59 -04:00
|
|
|
[[breaking_70_mappings_changes]]
|
|
|
|
=== Mapping changes
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2017-08-28 11:43:59 -04:00
|
|
|
==== The `_all` meta field is removed
|
|
|
|
|
2017-09-25 17:43:14 -04:00
|
|
|
The `_all` field deprecated in 6 have now been removed.
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2018-04-11 03:41:37 -04:00
|
|
|
==== The `_uid` meta field is removed
|
|
|
|
|
|
|
|
This field used to index a composite key formed of the `_type` and the `_id`.
|
|
|
|
Now that indices cannot have multiple types, this has been removed in favour
|
|
|
|
of `_id`.
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2018-03-21 05:44:11 -04:00
|
|
|
==== The `_default_` mapping is no longer allowed
|
|
|
|
|
|
|
|
The `_default_` mapping has been deprecated in 6.0 and is now no longer allowed
|
|
|
|
in 7.0. Trying to configure a `_default_` mapping on 7.x indices will result in
|
|
|
|
an error.
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2017-09-25 17:43:14 -04:00
|
|
|
==== `index_options` for numeric fields has been removed
|
|
|
|
|
2017-11-22 10:16:28 -05:00
|
|
|
The `index_options` field for numeric fields has been deprecated in 6 and has now been removed.
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2017-11-22 10:16:28 -05:00
|
|
|
==== Limiting the number of `nested` json objects
|
|
|
|
|
|
|
|
To safeguard against out of memory errors, the number of nested json objects within a single
|
|
|
|
document across all fields has been limited to 10000. This default limit can be changed with
|
2018-01-22 06:03:07 -05:00
|
|
|
the index setting `index.mapping.nested_objects.limit`.
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2018-01-22 06:03:07 -05:00
|
|
|
==== The `update_all_types` option has been removed
|
|
|
|
|
|
|
|
This option is useless now that all indices have at most one type.
|
2018-04-03 10:45:25 -04:00
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2018-09-07 19:53:36 -04:00
|
|
|
==== The `classic` similarity has been removed
|
2018-04-03 10:45:25 -04:00
|
|
|
|
|
|
|
The `classic` similarity relied on coordination factors for scoring to be good
|
|
|
|
in presence of stopwords in the query. This feature has been removed from
|
|
|
|
Lucene, which means that the `classic` similarity now produces scores of lower
|
|
|
|
quality. It is advised to switch to `BM25` instead, which is widely accepted
|
|
|
|
as a better alternative.
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2018-09-07 19:53:36 -04:00
|
|
|
==== Similarities fail when unsupported options are provided
|
2018-04-03 10:45:25 -04:00
|
|
|
|
|
|
|
An error will now be thrown when unknown configuration options are provided
|
|
|
|
to similarities. Such unknown parameters were ignored before.
|
[Geo] Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach (#36751)
* [Geo] Expose BKDBackedGeoShapes as new VECTOR strategy
This commit exposes lucene's LatLonShape field as a new
strategy in GeoShapeFieldMapper. To use the new indexing
approach, strategy should be set to "vector" in the
geo_shape field mapper. If the tree parameter is set
the mapper will throw an IAE. Note the following:
When using vector strategy:
* geo_shape query does not support querying by POINT,
MULTIPOINT, or GEOMETRYCOLLECTION.
* LINESTRING and MULTILINESTRING queries do not support
WITHIN relation.
* CONTAINS relation is not supported.
* The tree, precision, tree_levels, distance_error_pct,
and points_only parameters will not throw an exception
but they have no effect and will be marked as
deprecated..
All other features are supported.
* revert change to PercolatorFieldMapper
* fix ExistsQuery for geo_shape vector strategy
* add deprecation logging for tree, precision, tree_levels, distance_error_pct, and points_only
* initial update to geoshape docs, including mapping migration updates
* initial support for GeoCollection queries
* fix docs and javadoc errors
* clean up geocollection queries
* set deprecated mapping tests to NOTCONSOLE
* fix geo-shape mapper asciidoc mapping and test warnings
* add support for point queries using LatLonShapeBoundingBoxQuery
* update GeoShapeQueryBuilderTests to include POINT queries for VECTOR strategy. Other comment cleanups
* add lucene geometry build testing to ShapeBuilder tests
* remove deprecated prefix tree mapping from geo-shape.asciidoc
* refactor GeoShapeFieldMapper into LegacyGeoShapeFieldMapper and GeoShapeFieldMapper
Both classes derive from BaseGeoShapeFieldMapper that provides shared parameters:
coerce, ignoreMalformed, ignore_z_value, orientation.
* update docs to remove vector strategy
* fix GeometryCollectionBuilder#buildLucene to return the object created by the shape builder
* fix LineLength failure in GeoJsonShapeParserTests
* ShapeMapper refactor changes from PR feedback
* fix typo in geo-shape.asciidoc
* ignore circle test in docs
* update indexing-approach ref to geoshape-indexing-approach
* add warnings check for LegacyGeoShapeFieldMapper to AbstractBuilderTestCase
* fix deprecatedParameters setup
* update indexing approach
* fixing unexpected warnings failures
* move orientation back to field type
* remove if in LegacyGeoShapeFieldMapper#doXContent. Fix GeoShapeFieldMapper to work with double array as a point
* fix indexing-approach link in circle section of geoshape docs
* add strategy to deprecation warnings check
* fix test failures
* fix typo in QueryStringQueryBuilderTests
* fix total hits to totalHits().value
* fix version number
* add version check to BaseGeoShapeFieldMapper
* fix line length!
* revert version check in BaseGeoShapeFieldMapper
* Fix serialization of mappings of legacy shapes.
2018-12-18 10:54:56 -05:00
|
|
|
|
|
|
|
[float]
|
|
|
|
==== deprecated `geo_shape` Prefix Tree indexing
|
|
|
|
|
|
|
|
`geo_shape` types now default to using a vector indexing approach based on Lucene's new
|
|
|
|
`LatLonShape` field type. This indexes shapes as a triangular mesh instead of decomposing
|
|
|
|
them into individual grid cells. To index using legacy prefix trees `recursive` or `term`
|
|
|
|
strategy must be explicitly defined. Note that these strategies are now deprecated and will
|
|
|
|
be removed in a future version.
|
|
|
|
|
|
|
|
[float]
|
|
|
|
==== deprecated `geo_shape` parameters
|
|
|
|
|
|
|
|
The following type parameters are deprecated for the `geo_shape` field type: `tree`,
|
|
|
|
`precision`, `tree_levels`, `distance_error_pct`, `points_only`, and `strategy`. They
|
|
|
|
will be removed in a future version.
|