Skip to content
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

fix(http/legacy): filter on Default=true when no RP given in V1 write #20074

Merged
merged 2 commits into from
Nov 17, 2020

Conversation

danxmoran
Copy link
Contributor

Closes #20070

If no RP is specified on a V1 write, the system should find & use the default DBRP mapping, not any DBRP mapping.

  • CHANGELOG.md updated with a link to the PR (not the Issue)
  • Well-formatted commit messages
  • Rebased/mergeable
  • Tests pass
  • http/swagger.yml updated (if modified Go structs or API)
  • Feature flagged (if modified API)
  • Documentation updated or issue created (provide link to issue/pr)
  • Signed CLA (if not already signed)

@danxmoran danxmoran force-pushed the dm-legacy-write-default-rp-20070 branch from 34aee74 to 9ccf438 Compare November 17, 2020 20:38
@danxmoran danxmoran merged commit 71f8de3 into master Nov 17, 2020
@danxmoran danxmoran deleted the dm-legacy-write-default-rp-20070 branch November 17, 2020 21:04
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.

Legacy write path should filter on Default=true when RP not specified
2 participants