Scala Common Enrich: support POST requests in API Request enrichment
See original GitHub issueCurrently the API request enrichment only supports GET requests where each of the inputs
is either added as part of the URL path or alternatively as part of the query parameters.
Supporting POST would make it possible to reliably send significantly larger payloads that may either involve a large number of inputs or a smaller number of inputs but with a large amount of text (e.g., encrypted data, large arrays etc).
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Effective data enrichment in Spark jobs from external API
Enriching a dataframe with some data gathered from external API; Reading/writing data from some database that doesn't have a usual Spark ...
Read more >Simple REST Requests Using Requests-Scala - Baeldung
Requests -Scala is a Scala port of the popular Python library Requests. It provides a straightforward API to make REST calls.
Read more >Enrichment and batch processing in Snowplow - datamindedbe
Enrichment starts with an adapter mapping raw HTTP GET and POST requests to one or more “raw events”. Raw events have properties and...
Read more >Data Enrichment in Flink SQL using HTTP Connector For Flink
In this blog post I will focus on the use case we came across: using Flink SQL to enrich data streams with data...
Read more >Snowplow Enrichment - Scaladex
Snowplow Enrich · Snowplow Common Enrich - a core library, containing all validation and transformation logic. · Snowplow Stream Enrich - a set...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@alexanderdean Yes, currently it is 1.
I think in this case, we need only create a new version of JSON Schema when
"size": { "type": "integer", "minimum": 0 }
.Current implementation of cache supports
size = 0
:Agreed - it isn’t semantically ideal from a REST point of view but could also make it quite a bit easier to support POST queries to GraphQL APIs.