github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-25 07:07:54 -04:00
Code Issues Projects Releases Packages Wiki Activity

Fix formatting of breaking changes to not split across pages

Browse source 
The current formatting results in multiple pages, which is confusing, as seen on https://www.elastic.co/guide/en/logstash/current/breaking-changes.html

Fixes #9550
This commit is contained in:
Andrew Cholakian 2018-05-09 18:48:05 -05:00
parent f2e9cbe303
commit bf6e5ca632
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/static/breaking-changes.asciidoc vendored
View file

@ -1,6 +1,6 @@
[[breaking-changes]] [[breaking-changes]]
== Breaking Changes Across PQ Versions Prior to Logstash 6.3.0 ===== Breaking Changes Across PQ Versions Prior to Logstash 6.3.0
The following applies only to users upgrading from Logstash installations that used the persistent queue prior to 6.3.0. The following applies only to users upgrading from Logstash installations that used the persistent queue prior to 6.3.0.
@ -10,12 +10,12 @@ If you are upgrading Logstash from a pre 6.3.0 version and use the persistent qu
To drain the queue, enable the `queue.drain` setting, and then shutdown Logstash. Wait for it to shutdown completely. This may take a while if you have a large queue backlog. To drain the queue, enable the `queue.drain` setting, and then shutdown Logstash. Wait for it to shutdown completely. This may take a while if you have a large queue backlog.
== Breaking Changes in 6.0.0 === Breaking Changes in 6.0.0
This section discusses the changes that you need to be aware of when migrating to Logstash 6.0.0 from the previous major releases. This section discusses the changes that you need to be aware of when migrating to Logstash 6.0.0 from the previous major releases.
[float] [float]
=== Changes in Logstash Core ==== Changes in Logstash Core
These changes can impact any instance of Logstash and are plugin agnostic, but only if you are using the features that are impacted. These changes can impact any instance of Logstash and are plugin agnostic, but only if you are using the features that are impacted.