-
Notifications
You must be signed in to change notification settings - Fork 76
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
Bulk entity creation via API #1070
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ktuite
force-pushed
the
ktuite/bulk_append
branch
3 times, most recently
from
January 30, 2024 20:40
58210fc
to
e295d23
Compare
ktuite
force-pushed
the
ktuite/bulk_append
branch
from
February 6, 2024 00:31
e295d23
to
d5890b9
Compare
ktuite
force-pushed
the
ktuite/bulk_append
branch
from
February 13, 2024 19:31
e76aeb8
to
9b11b48
Compare
ktuite
commented
Feb 13, 2024
ktuite
commented
Feb 13, 2024
matthew-white
approved these changes
Feb 15, 2024
ktuite
commented
Feb 15, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interactive review with @matthew-white
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes getodk/central#573
Uses POSTing to existing
/v1/projects/1/datasets/people/entities
endpoint so it can handle{uuid, label, data}
{entities: [{}, {}], source: {name, size}}
For the source object,
source
is requiredname
within source is required (not sure if it should be but it will help with displaying on the front end...)size
(meant to represent file size)I was thinking about how to handle the bulk SQL insert and decided it was easiest to think/build two separate queries, one for the
entities
table and another for theentity_defs
table. Elsewhere the code, we have complex queries for inserting a single entity's data into both tables at once, but it didn't seem reasonable to try to do that with multiple entities.What has been done to verify that this works as intended?
Tests, trying it out.
Why is this the best possible solution? Were any other approaches considered?
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Does this change require updates to the API documentation? If so, please update docs/api.md as part of this PR.
Documentation is included in this PR!!
Before submitting this PR, please make sure you have:
make test-full
and confirmed all checks still pass OR confirm CircleCI build passes