github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 01:38:56 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Fixes tagging for notable breaking changes (#41264)

Browse source
This commit is contained in:
gchaps 2019-07-16 10:02:36 -07:00 • committed by GitHub
parent ce361bb36b
commit 72383d9939
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/migration/migrate_7_3.asciidoc
View file

@ -9,14 +9,6 @@ your application to Kibana 7.3.
See also <<release-highlights-7.3.0, release highlights>> and <<release-notes-7.3.0, release notes>>.
[float]
=== Visibility of features after configuring a term join in Maps
*Details:* When performing a terms join in a vector layer in the Maps app, features that do not have a matching term in the join will no longer be visible on the map. Before, these features would remain visible, although they would not show any results for the join in their corresponding tooltip. This aligns the behavior of this functionality with the behavior in the Region Maps visualization. The old behavior, in which features without a corresponding record in the term-query result would still be visible on the map, is no longer supported.
*Impact:* This affects all maps that have a term join configured on a vector layer. The effect is primarily a change in the visual representation of the layer. In practice, fewer features will be visible if the results of the term-query have no corresponding record for all features on the map. This also means that all fields in a tooltip will have a corresponding value. Previously, the aggregation metrics for some rows in the tooltip would just be empty if there was no corresponing result in the term-query.
//NOTE: The notable-breaking-changes tagged regions are re-used in the
//Installation and Upgrade Guide
@ -27,6 +19,12 @@ The following section is re-used in the Installation and Upgrade Guide
////
// tag::notable-breaking-changes[]
[float]
=== Visibility of features after configuring a term join in Maps
*Details:* When performing a terms join in a vector layer in the Maps app, features that do not have a matching term in the join will no longer be visible on the map. Before, these features would remain visible, although they would not show any results for the join in their corresponding tooltip. This aligns the behavior of this functionality with the behavior in the Region Maps visualization. The old behavior, in which features without a corresponding record in the term-query result would still be visible on the map, is no longer supported.
*Impact:* This affects all maps that have a term join configured on a vector layer. The effect is primarily a change in the visual representation of the layer. In practice, fewer features will be visible if the results of the term-query have no corresponding record for all features on the map. This also means that all fields in a tooltip will have a corresponding value. Previously, the aggregation metrics for some rows in the tooltip would just be empty if there was no corresponing result in the term-query.
[float]
[[breaking_73_data_frames_date_format]]
=== Removed support for date histogram format specifications in {dataframe-transforms}