Add additional note for release
diff --git a/website/0.9.9/src/site/apt/releasenotes/release-0.9.9.apt b/website/0.9.9/src/site/apt/releasenotes/release-0.9.9.apt
index f262dbc..5dd14cc 100644
--- a/website/0.9.9/src/site/apt/releasenotes/release-0.9.9.apt
+++ b/website/0.9.9/src/site/apt/releasenotes/release-0.9.9.apt
@@ -35,6 +35,14 @@
* Key Note for Helix Release
+ In this release, there are three type of configuration for ZK write limitations:
+
+ * jute.maxbuffer: This used to be consistent with jute maxbuffer set for ZkClient. So if your data size is over this value, write is not allowed.
+
+ * zk.serializer.znrecord.write.size.limit.bytes: If the ZNode size is larger than the value you set (even after compression), the data will NOT be written to ZK at ZNRecorderSerializer level. Default is 1MB
+
+ * zk.serializer.znrecord.auto-compress.threshold.bytes: If the ZNode size is larger than the value you set, compression will be applied for this ZNode.
+
[]
* Detailed Changes
@@ -43,6 +51,8 @@
* Add separate ZK serializer configuration to active ZNRecord compression when size exceeds a threshold. #1901
+ * Validate data write size limit in ZkClient #1072
+
[]
Cheers,
diff --git a/website/pom.xml b/website/pom.xml
index 20a6a8f..310d268 100644
--- a/website/pom.xml
+++ b/website/pom.xml
@@ -42,6 +42,7 @@
<module>0.9.4</module>
<module>0.9.7</module>
<module>0.9.8</module>
+ <module>0.9.9</module>
<module>1.0.0</module>
<module>1.0.1</module>
<module>1.0.2</module>
