jiangpengcheng commented on issue #19721: URL: https://github.com/apache/pulsar/issues/19721#issuecomment-1479039494
I met the same problem and found the reason: When `--py` or `--jar`, `--go` is specified while updating functions, Pulsar will upload the given file to the package path like `function://public/default/test-function@0`, but this package path is used when the function is created, so we should add 1 to the function's version and use package path: `function://public/default/test-function@1` if you do not specify the `--py|--go|--jar`, it will success, and the function version is updated to 1, and then update the function again with `--py|--go|--jar`, it will succeed too since it will use path `function://public/default/test-function@1` while such package doesn't exist yet and this is the same for `source` and `sink` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
