Skip to content

fix(router): l2 cache uses client name in key, persisted operation not found returns 200#1351

Merged
df-wg merged 1 commit intomainfrom
dave/eng-5910-persisted-query-not-found-should-return-200
Nov 8, 2024
Merged

fix(router): l2 cache uses client name in key, persisted operation not found returns 200#1351
df-wg merged 1 commit intomainfrom
dave/eng-5910-persisted-query-not-found-should-return-200

Conversation

@df-wg
Copy link
Copy Markdown
Contributor

@df-wg df-wg commented Nov 8, 2024

Motivation and Context

Previous PRs added APQ, and affected persisted operations. This PR makes two changes:

Checklist

@github-actions github-actions Bot added the router label Nov 8, 2024
@df-wg df-wg force-pushed the dave/eng-5910-persisted-query-not-found-should-return-200 branch from ee35394 to 0cba6b3 Compare November 8, 2024 08:23
@df-wg df-wg changed the title fix(router): L2 cache uses client name in key, persisted operation not found returns 200 fix(router): l2 cache uses client name in key, persisted operation not found returns 200 Nov 8, 2024
@df-wg df-wg merged commit 34cf5b5 into main Nov 8, 2024
@df-wg df-wg deleted the dave/eng-5910-persisted-query-not-found-should-return-200 branch November 8, 2024 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect ClientInfo Handling When Loading Persisted Operations from Cache

2 participants