Breaking changes in 7.3edit

This section discusses the changes that you need to be aware of when migrating your application to Kibana 7.3.

See also release highlights and release notes.

Visibility of features after configuring a term join in Mapsedit

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.

Removed support for date histogram format specifications in transformsedit

Details: If your transform groups your data by using a date histogram, the format property is no longer supported.

Impact: Transforms that were created in 7.2 and use date histograms might no longer work in 7.3. If you run into issues starting a transform, recreate it by copying the pivot part of the configuration into the advanced editor of the transforms wizard. The advanced editor will remove the unsupported attribute once the configuration gets applied.

Dashboard import and export APIsedit

Dashboard import and export APIs error status codesedit

Details: The dashboard import and export APIs will return more accurate HTTP status codes instead of returning a HTTP 400 status code for all failure scenarios. Specifically, authorization failures will now correctly return a HTTP 403 when the authenticated user lacks sufficient privileges.

Impact: Review the error handling logic of any integrations with the dashboard import and export APIs.