Skip to content
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.

Sign up for GitHub

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

Jump to bottom

feat: use input catalog properties to optimize dynamodb request #23

Open
pnadolny13 opened this issue Apr 24, 2023 · 0 comments
Open

feat: use input catalog properties to optimize dynamodb request #23

pnadolny13 opened this issue Apr 24, 2023 · 0 comments

Comments

@pnadolny13
Copy link
Contributor

pnadolny13 commented Apr 24, 2023 •
edited
Loading

Following #11 closed by #22 the tap respects input catalogs but the selections arent accounted for in the scan request. This is inefficient because data is retrieved that is not emitted. Instead the tap could use the selected properties to build the ProjectionExpression argument for the scan operation, this way the API request will only return the desired properties.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pnadolny13