Skip to content

CDA-130 - Adds support for patial patches. Implements for text-timeseries - #1931

Open
rma-bryson wants to merge 1 commit into
developfrom
feature/CDA-130-partial-patch-for-timeseries-text
Open

rma-bryson wants to merge 1 commit into
developfrom
feature/CDA-130-partial-patch-for-timeseries-text

Conversation

@rma-bryson

@rma-bryson rma-bryson commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

Establishes support for partial patch with text timeseries implementation.

Related Issue

Closes #1715

Validation

Integration and unit tests

Checklist

  • AI tools used

@rma-bryson
rma-bryson force-pushed the feature/CDA-130-partial-patch-for-timeseries-text branch 6 times, most recently from bfa25b9 to 35435ad Compare September 11, 2026 18:32
@rma-bryson
rma-bryson marked this pull request as ready for review September 11, 2026 19:07
…eries. updates open api doc test to check abstractions of accessors for parameters
@rma-bryson
rma-bryson force-pushed the feature/CDA-130-partial-patch-for-timeseries-text branch from 35435ad to 439249f Compare September 16, 2026 21:15
)
@Override
public void create(@NotNull Context ctx) {
super.create(ctx);

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MikeNeilson - the create for v2 does the same thing as previous behavior where it stores regardless of if the data exists or not (essentially acting as both a create and an update). Wondering if we want to start enforcing POST is only for non-existing data, PATCH should be used for data that already exists in v2 and beyond?

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.

Standard Text Timeseries PATCH requires FULL write to update

1 participant