-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
refactor(http): Extract write handler logic for re-use elsewhere #18507
Conversation
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.
Really great improvements to overall code structure in the PR. I had a single question regarding the LimitedReadCloser
, and I recognize the behavior is the same, as you've just shuffled code around.
Free to merge if that question is of no concern.
WithParserOptions( | ||
models.WithParserMaxBytes(b.WriteParserMaxBytes), | ||
models.WithParserMaxLines(b.WriteParserMaxLines), | ||
models.WithParserMaxValues(b.WriteParserMaxValues), | ||
), |
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.
👏
c4ce13a
to
cb8d38d
Compare
cb8d38d
to
e1f063c
Compare
This is the first PR in a 3-part story to deliver an API for 1.x writes.
This shuffles the structure of the existing
/api/v2/write
endpoint to allow the/write
(1.x) endpoint to share the point parse and writing code. Code that was originally placed directly in the main HTTP handler has been moved out into other supporting structures for re-use.📎 influxdata/idpe#6948