flowchartsman commented on issue #19721: URL: https://github.com/apache/pulsar/issues/19721#issuecomment-1479782312
Does this relate to non-standalone as well? I also submitted a few similar bugs related to updating pulsar functions, so tagging them here, since there PRs: #18966 #18973 #18972 It's still not clear to me what the function workflow is supposed to be like, and which technique we should use: - `pulsar-admin function upload` - `pulsar-admin packages upload` - `pulsar-admin functions create --py|--go|--jar <path>` This could use some documentation help, I think, to make things more clear on the function lifecycle so that we know how to 1. Provide a py/go/jar function package to pulsar at version 0 2. Run new functions with this package 3. Add a new version of the package 4. Update running functions to use the new version 5. list all versions of a function package and, finally 6. delete old versions when they are no longer necessary. -- 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]
