[GitHub] [pulsar] codelipenghui commented on a change in pull request #5824: Publish a blog post to apache pulsar blog

[GitBox <gi...@apache.org>]

codelipenghui commented on a change in pull request #5824: Publish a blog post to apache pulsar blog
URL: https://github.com/apache/pulsar/pull/5824#discussion_r355365344
 
 

 ##########
 File path: site2/website/blog/2019-12-04-Apache-Pulsar-2-4-2.md
 ##########
 @@ -0,0 +1,103 @@
+---
+author: Xiaolong Ran
+authorURL: https://twitter.com/wolf4j1
+title: Apache Pulsar 2.4.2
+---
+
+We are glad to publish Apache Pulsar 2.4.2. This is the result of a huge 
+effort from the community, with over 110 commits, general improvements and bug fixes.
+
+Check out the <b>[release notes](../release-notes.md/)</b> for a detailed list of 
+the changes, with links to the relevant pull requests, discussions and documentation.
+
+Regarding improvements and bug fixes introduced, I just want to highlight here a tiny subset of them:
+
+<!--truncate-->
+
+- In Pulsar 2.4.1, we instead of using a shaded JAR to start a java function instance, use different classLoaders to 
+load the internal pulsar code, user code, and the interfaces that the two interacts with each other. This is a good 
+change, but this change will cause the following two problems:
+    - The windowed functions were broken when we changed java function instance to use classLoaders. 
+    - When using the `--output-serde-classname` option, functionClassLoader is not set correctly.  
+
+  In Pulsar 2.4.2, we fixed this issue to make sure them works. 
+
+- In Pulsar 2.4.1, Broker fails to start with function worker enabled and broker client using TLS. Looking at the 
 
 Review comment:
   ```suggestion
   - Before Pulsar 2.4.2, Broker fails to start with function worker enabled and broker client using TLS. Looking at the 
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services