Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.5.1
-
Untriaged
-
1
-
Unknown
Description
If customer is using N1QL in 5.5.x or 6.0.x - due to the need to do close(), and if they had dropped down to N1qlQuery() class the change to N1QL() call, they will be forced to undeploy the handler before upgrading to 6.5.1. This presents an unacceptable challenge if the handlers were taking actions with side effects. While admittedly these features were Beta, we still can't not have a working recipe to allow upgrade, as there are several significant users online today. This bug is to ensure we have a working path for these users to upgrade to 6.5.1 without having to reprocess all their data (assuming MB-39079 can be solved)
Attachments
Issue Links
- is a backport of
-
MB-39974 Support 6.0.x to 6.6 upgrade of handlers using N1qlQuery() Beta API
- Closed