-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add ingestion of large DK or SK records #181
Comments
StephenAbbott
changed the title
Register v2: Add ingestion of large DK or SK records
Add ingestion of large DK or SK records
Sep 1, 2023
Blocks #164 QA. |
spacesnottabs
moved this from Todo (highest priority at top)
to In Progress
in Open Ownership Register and BODS pipelines
Sep 17, 2023
spacesnottabs
moved this from In Progress
to In Testing
in Open Ownership Register and BODS pipelines
Sep 17, 2023
@spacesnottabs, @StephenAbbott, what is the testing status of this ticket, please? |
@spacesnottabs Are you happy that the large DK and SK records have been reinserted now? |
Outstanding work to do here... |
I'm not sure whether this should be in testing, @StephenAbbott, if there's still work to do. But maybe this relates to other tickets (or other tickets will be created)? |
StephenAbbott
moved this from In Testing
to In Progress
in Open Ownership Register and BODS pipelines
Nov 3, 2023
StephenAbbott
moved this from In Progress
to Todo
in Open Ownership Register and BODS pipelines
Nov 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently DK and SK source records larger than 1Mb are not being processed and instead stored in a separate S3 folder with a link provided in the output stream.
These need to also be imported.
The text was updated successfully, but these errors were encountered: