Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3543#issuecomment-126131982
Yeah, may be that is a good idea for now. In fact, SparkHadoopUtil.get.conf
calls newConfiguration only once, and then the configuration is used
everywhere. So the newConfiguration() will be called only every once in the
lifetime of the application, and the likelihood of the race condition causing a
problem here is really small. So I think its fine for now to just address this.
The way I would do this is to make the JIRA specific to streaming only (set
component and title accordingly). And file a separate JIRA (if not already
present) for a possible problem in newConfiguration() linking it to the Hadoop
JIRA. Does that make sense? @JoshRosen Any thoughts?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
