-
Notifications
You must be signed in to change notification settings - Fork 26
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
TypeError: client.newScanBuilder(...).filterAttributeEquals is not a function #125
Comments
Did you solve this? |
@0xd5 I ended up using other libs ;) |
Same here, this had a lot of promise but in the end I just stuck with the AWS SDK. Which lib did you use? @aterreno |
A mix, the raw sdk for some crazy stuff, http://dynastyjs.com for simple
things.
Settling now on https://github.com/clarkie/dynogels
It's pretty awesome, takes a bit to get it configured right but totally
worth it after.
We also use the promisified version to leverage async await syntax
On 11 May 2018 18:38, "Daniel Sutton" <notifications@github.com> wrote:
Same here, this had a lot of promise but in the end I just stuck with the
AWS SDK. Which lib did you use?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#125 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEpCgpP9fbAYo6qeSoVuQU0u6uzdBX8ks5txcx4gaJpZM4TfuQ6>
.
|
Having the same issue as the OP. Any way around the issue? I really want to stick with |
Following this thread. Hope someone can share a solution |
Try with:
It works for me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there, my code looks like:
but I get the exception:
Is the readme up to date?
Thanks
The text was updated successfully, but these errors were encountered: