freeznet commented on a change in pull request #11392:
URL: https://github.com/apache/pulsar/pull/11392#discussion_r673620387



##########
File path: site2/website/release-notes.md
##########
@@ -3,6 +3,15 @@
 
 ### 2.8.0 &mdash; 2021-06-12 <a id=“2.8.0”></a>
 
+### Update notice
+
+Due to a breaking change in the Schema API it may happen that some Pulsar 
Functions or Pulsar IO Connector fail to work, 
+throwing an `IncompatibleClassChangeError`.
+In this case you have to rebuild your Function using Apache Pulsar 2.8.0 as 
dependency and redeploy it.
+If you are running on Kubernetes you can temporarily let the Functions Worker 
pod run with a previous version of Pulsar

Review comment:
       From my understanding, for Kubernetes users, we need to take into 
account the runtime which users using. If users use thread or process runtime, 
then they should keep functions worker pod with a previous version of Pulsar. 
If users use Kubernetes runtime, they should keep the 
`functionRuntimeFactoryConfigs.functionDockerImages` or 
`functionRuntimeFactoryConfigs.pulsarDockerImageName` with previous version of 
Pulsar in `functions_worker.yml`.




-- 
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.

To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to