-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for on-demand capacity #86
Comments
Could I know the current status of this issue? I see the PR #85 is closed but not merged. My customer and I are encountering this issue. A query to DynamoDB (on-demand) would fail with the below exception.
|
Also, the exception thrown is somehow misleading. Line 66 in 880145c
The value maxReadThroughputAllocated is read from dynamodb.throughput.read, which is not a 'percent'. |
+1, we have been waiting for this feature to be released too. |
It is being worked on PR #88 |
I've been trying to export DynamoDB from HiveSQL.
Using a simple Hive Script
select * from tableName
I encounter a read capacity error. The capacity calculation of the connector is made by using a percentage.This script works great when the DynamoDB table is set on managed capacity mode. But when switched to on-demand error I encounter the Capacity error.
Could you enable a configuration setting that allows to use a table con on-demand capacity and that uses the maximum throughput the EMR Cluster will use?
Thanks you
The text was updated successfully, but these errors were encountered: