Github user budde commented on the issue:
https://github.com/apache/spark/pull/16744
There shouldn't be any change to behavior or compatibility when using the
existing implementations of ```KinesisUtils.createStream()```. Only drawback I
can think of is this is making the ```createStream()``` API more complex by
introducing an additional set of optional config values, which in turn
necessitates an additional set of overridden interface implementations. I think
the longer-term solution here is to introduce a builder-style API for
generating Kinesis streams and eventually put the existing
```KinesisUtils.createStream()``` on the deprecation path, but I've chosen to
bite the bullet and just extend ```createStream()``` further in the interest of
making this a minimal change.
---
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
