[
https://issues.apache.org/jira/browse/SPARK-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482749#comment-14482749
]
Paweł Kopiczko commented on SPARK-6514:
---------------------------------------
I named the param `regionName` after the one in the
KinesisClientLibConfiguration. I thought it will obvious when someone is
familiar with KCL consumer API. But dynamoRegion is also good. We can extract
region from streamURL but maybe someone would want to set different region than
the stream location. Why do you think that implementation exposure is not good?
Don't you think that everything that is configurable in KCL client that we use
should also be configurable when creating DStream?
> For Kinesis Streaming, use the same region for DynamoDB (KCL checkpoints) as
> the Kinesis stream itself
> --------------------------------------------------------------------------------------------------------
>
> Key: SPARK-6514
> URL: https://issues.apache.org/jira/browse/SPARK-6514
> Project: Spark
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 1.3.0
> Reporter: Chris Fregly
>
> context: i started the original Kinesis impl with KCL 1.0 (not supported),
> then finished on KCL 1.1 (supported) without realizing that it's supported.
> also, we should upgrade to the latest Kinesis Client Library (KCL) which is
> currently v1.2 right now, i believe.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
