Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10492#issuecomment-167543175
@JoshRosen it's not the scope that's an issue but the version. Not
specifying it lets the SDK version required by the Kinesis client come in at
whatever it needs to be. I am not sure provided scope works since it does
really need to be bundled and isn't necessarily otherwise available from the
env.
There's a little wrinkle here in that the Kinesis code uses SDK classes
directly, so technically the POM should declare that. However the SDK is used
only in the context of the Kinesis client, so it seems like the lesser evil to
rely on it as a transitive dependency but at the right version.
---
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]
