gboo-infa commented on PR #39097: URL: https://github.com/apache/spark/pull/39097#issuecomment-1360812426
Oops sorry, I was hoping someone with authority or at least familiarity with the Spark committer culture would answer your question. I don't really have either of those things so I can't really comment on whether Spark JIRAs are ok to use for related issues... My only concern was that someone would mistake your PR as a fix for the underlying issue and mark the JIRA as resolved, and I didn't want to cause the confusion of reopening the JIRA or submitting an identical one with a different example operation. Personally, I think if you've already gone to the trouble to create the PR, and it doesn't break anything, then maybe it's not so bad to just check it in regardless of what JIRA it uses... It'll probably make it harder for people to make sense of the release notes, so a few extra minutes from you might save hours of collective time for the rest of the world, but I dunno, up to you. :/ -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
