Github user bOOm-X commented on the issue:
https://github.com/apache/spark/pull/18253
@cloud-fan
In my opinion, having the queues indexed by a string and reflecting that in
the API is a bit too error prone in this case. What you want is to be in an
isolated queue. With this kind of API it is easy to have an other listener
added to the same queue because of a conflicting label. In the contrary, it is
quite easy to not had 2 depending listeners not in the same queue because of
case, ..., of the label. With a map of queues, it enforces the mutability of
the queue, which is not really necessary here. And I think that it is a good
idea to enforce the fact that depending listeners should be put in the same
queue, it increases the readability and the clarity of the API.
---
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]
