Github user tdas commented on the issue:
https://github.com/apache/spark/pull/11863
I played around with the API and I found a few issues
1. I mentioned above, case classes lead to problems in the public API. The
API could be simpler, and same for both Java and Scala users (dont like the
apply vs create).
2. The wrapping between java and scala maps were sometimes leading to the
map not being serializable, and thus causing serialization issues in Subscribe
and Assign strategies when checkpointing.
3. ConsumerStrategy class is an interface making it hard to add methods
later without breaking compatibility.
I have opened a new PR to address them - please take a look - #13996
---
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]
