Document accept_http and update HTTP operators#212
Open
mavam wants to merge 13 commits intotopic/new-executorfrom
Open
Document accept_http and update HTTP operators#212mavam wants to merge 13 commits intotopic/new-executorfrom
mavam wants to merge 13 commits intotopic/new-executorfrom
Conversation
…#190) * Add MySQL integration documentation and from_mysql operator reference Adds comprehensive documentation for the from_mysql operator, including: - New integration page at /integrations/mysql - Detailed operator reference at /reference/operators/from_mysql with parameter descriptions, type mappings, and usage examples - Updates to integration and operator index pages to include MySQL The from_mysql operator enables reading data from MySQL databases using table selection, raw SQL queries, or metadata inspection. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Finalize docs --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
* Add from_tcp operator documentation Document the new from_tcp operator with TLS support, including the tls record parameter, peer variable, and usage examples. Update the TCP integration page and cross-reference from_tcp in load_tcp and save_tcp See Also sections. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix from_tcp docs: use $peer syntax and correct types Use $peer instead of peer for let-bound variable references in sub-pipelines. Correct the ip field type from string to ip and the port field type from int to int64. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Document the `live` and `tracking_column` parameters that enable continuous polling for new rows using watermark tracking on an integer column. Add examples for both auto-detected and explicit tracking columns. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Add documentation for the new `accept_http` operator that starts an HTTP server and forwards incoming requests as events. Update `from_http` to reflect its new client-only design with the `$response` pipeline variable replacing `metadata_field`, and the removal of `server=true` mode. Add `accept_http` to the See Also section of the `http` operator. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
9 tasks
Contributor
|
📦 Preview · View → · 🟢 Live Auto-updates on push |
- Replace `metadata_field` with `$response` variable for `from_http`
- Move lambda pagination examples to `http` operator (from_http only
supports `paginate="link"` now)
- Fix TLS syntax to use `tls={...}` record format
- Fix incorrect parameter names (`max_retries` -> `max_retry_count`,
`timeout` -> `connection_timeout`)
- Update data enrichment and error handling examples
- Clarify which features are `from_http`-only vs `http`-only
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Restructure around use cases: fetching data, accepting requests, and sending data. Add accept_http coverage, TLS examples for both client and server, and webhook/enrichment/pagination examples. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Remove duplicated examples and link to the guide instead. Keep the page focused on explaining what operators exist and when to use each. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add a section explaining that from_http and http are both HTTP clients
with nearly identical options, differing only in being a source vs
transformation operator.
Replace nonsensical `from {} / http` patterns with realistic examples
that show http enriching actual input data.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
mavam
force-pushed
the
topic/http-with-proxygen
branch
from
592fd96 to
8b171ef
Compare
mavam
force-pushed
the
topic/new-executor
branch
from
8c59ee1 to
3886444
Compare
mavam
force-pushed
the
topic/new-executor
branch
from
588262f to
17b8b2b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
accept_httpoperator (HTTP server that accepts incoming requests as events)from_httpdocumentation to reflect the new client-only design with$responsepipeline variable (replacingmetadata_fieldandserver=truemode)accept_httpcross-reference to thehttpoperator's See Also sectionRelated PRs
Test plan
accept_http.mdxrenders correctly with all sectionsfrom_http.mdxno longer referencesserver=truemodeaccept_http,from_http, andhttp🤖 Generated with Claude Code