Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/4632#issuecomment-84209577
Hey @JoshRosen can probably take a look at this. One thing though, IIRC the
reason why we have a unique ID here is because some sets of users requested the
exact opposite behavior as what you want:
https://issues.apache.org/jira/browse/SPARK-3377
If we do decide to allow this, I think it's best to have a specific set of
naming schemes (don't give them a latch to chose an arbitrary conf), in order
to limit the surface area of possible configurations. I'm also not so sure
about the right way to do this in terms of the current MetricsConfing
infrastructure. It seems a bit weird to hard code handling of this particular
configuration hard coded in the MetricsConfig class. Only had time to take a
quick look though and I'm not familiar with that code at all.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
