Github user budde commented on the issue:
https://github.com/apache/spark/pull/17467
Not a Spark committer, but I've contributed to this component in the past.
I would strongly prefer an approach that avoids adding an additional parameter
to all of the Kinesis classes if the ```SparkConf``` from ```sc``` can be used
instead. I haven't looked at the initial version of your code, but based on
the stacktrace you've posted it seems like you might've been referencing
```sc``` directly from code running running on the executor (e.g. the
```KinesisSequenceRangeIterator``` instance created in the ```compute()```
method via ```getBlockFromKinesis()```). Did you try simply extracting the two
config values from ```sc``` and storing them as fields for
```KinesisBackedBlockRDDPartition``` then passing them as constructor arguments
to ```KinesisSequenceRangeIterator```?
---
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]
