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

Python API websockets option #32

Open
gaffer01 opened this issue Jun 23, 2022 · 0 comments
Open

Python API websockets option #32

gaffer01 opened this issue Jun 23, 2022 · 0 comments
Labels
enhancement New feature or request python-api

Comments

@gaffer01
Copy link
Member

Running queries from the Python API currently works as follows:

  • Query is sent to the query SQS queue where it is picked up by a lambda and then the results written to S3.
  • Whilst this is happening the Python client is polling Dynamo to see if the query has finished.
  • When the query is finished, the results are read from S3 into a list.

The need to wait for the results to have been written to S3 means that the queries are slower than they could be. This could be improved by using the same websockets approach as is used in QueryWebSocketClient.
@gaffer01 gaffer01 added enhancement New feature or request python-api labels Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request python-api
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gaffer01