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.

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

Ingest lambda timeout #12

Merged
merged 10 commits into from
Jul 19, 2018
Merged

Ingest lambda timeout #12

merged 10 commits into from
Jul 19, 2018

Conversation

sandyhider
Copy link
Member

No description provided.

sandyhider and others added 4 commits March 11, 2018 14:05
The DynamoDB table had its GSI removed.  delete_tiles() depends on this
index.  Cleanup will be handled by TTL policies in the future.
sandyhider and others added 6 commits June 20, 2018 14:30
Backend verifies that ingest job finished before actually "completing"
the job.  Backend returns status code 202 and adds tiles from incomplete
chunks back to the upload queue.
May not always want to index a downsampled channel.  Also, indexing
process is much more complex so decoupling so downsampling isn't
potentially broken by indexing.

Add aws-region argument.

Just in case we end up running in another region.
Remove id_index argument since indexing is now decoupled from
downsampling.

(cherry picked from commit db74f58)
…. downsample_volume_sfn should not be in the codebase anymore.
@sandyhider sandyhider merged commit 412d146 into master Jul 19, 2018
@sandyhider sandyhider deleted the ingest-lambda-timeout branch February 18, 2019 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants