Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/11863
Regarding your general comments
1 + 2 sure, will add
3. The reason ConsumerStrategy is last is because it's much more natural
for inline one-off subclasses of it to customize setup. There are only 3
arguments for the constructor at this point (ssc, locationStrategy,
consumerStrategy) so I don't think requiring an explicit location strategy is
much of a burden, and it makes sure people who were using brokers with the old
api know what's going on.
4 a sure
b Yeah, I can test those. Do you think there's a need to test things
with implict args (e.g. classtags) from java, because those are super awkward.
Seems unlikely to be used when there's a version with explicit equivalent args.
---
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]
