Skip to content

Conversation

@rjrudin
Copy link
Contributor

@rjrudin rjrudin commented Jul 14, 2023

I realized my initial "DocumentBatch" design was not good because it limited the user to defining a single set of default metadata. And the v1/documents endpoint allows for many sets of default metadata. The new design - introducing a DefaultMetadata class, and allowing the user to provide a list of any number of Document and DefaultMetadata instances - is simpler and adheres to what /v1/documents allows too.

No docs yet. Going to do a separate PR for those next.

I realized my initial "DocumentBatch" design was not good because it limited the user to defining a single set of default metadata. And the v1/documents endpoint allows for many sets of default metadata. The new design - introducing a DefaultMetadata class, and allowing the user to provide a list of any number of Document and DefaultMetadata instances - is simpler and adheres to what /v1/documents allows too. 

No docs yet. Going to do a separate PR for those next.
@rjrudin rjrudin merged commit aee68d2 into develop Jul 17, 2023
@rjrudin rjrudin deleted the feature/498-batch-metadata branch July 17, 2023 12:38
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.

4 participants