summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2012-08-26 12:27:37 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2012-08-26 12:27:37 +0200
commit9a9282b86c785d7c0b67a0b546748e3591a487a2 (patch)
tree5aafe351c270af16cdad2a16dcd69cc7825676bc
parent9068d7fa1e1ce57ab55838866ac58b060721193e (diff)
downloadrsyslog-9a9282b86c785d7c0b67a0b546748e3591a487a2.zip
rsyslog-9a9282b86c785d7c0b67a0b546748e3591a487a2.tar.gz
rsyslog-9a9282b86c785d7c0b67a0b546748e3591a487a2.tar.xz
doc: add incompatible patch info to ChangeLog
-rw-r--r--ChangeLog12
1 files changed, 12 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index dd165e1..95cd80e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -4,6 +4,18 @@ Version 6.4.1 [V6-STABLE] 2012-08-??
This lead to queue file corruption. While the root cause is a config
error, it is a bug that this important and hard to find config error
was not detected by rsyslog.
+- bugfix: "jsonf" property replacer option did generate invalid JSON
+ in JSON, we have "fieldname":"value", but the option emitted
+ "fieldname"="value". Interestingly, this was accepted by a couple
+ of sinks, most importantly elasticsearch. Now the correct format is
+ emitted, which causes a remote chance that some things that relied on
+ the wrong format will break.
+ Thanks to Miloslav Trmač for the patch
+- change $!all-json did emit an empty (thus non-JSON) string if no libee
+ data was present. It now emits {} and thus valid JSON. There is a
+ small risk that this may break some things that relied on the previous
+ inconsistency.
+ Thanks to Miloslav Trmač for the patch
---------------------------------------------------------------------------
Version 6.4.0 [V6-STABLE] 2012-08-20
- THIS IS THE FIRST VERSION OF THE 6.4.x STABLE BRANCH