-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore(deps): update dependency apollographql/router to v1.59.0 #12
base: 0.18.0
Are you sure you want to change the base?
Conversation
Run & review this pull request in StackBlitz Codeflow. |
|
c148448
to
bbd7c84
Compare
bbd7c84
to
7871c69
Compare
7871c69
to
6b1a894
Compare
6b1a894
to
b626340
Compare
b626340
to
434e142
Compare
434e142
to
39de428
Compare
39de428
to
c67f2cf
Compare
c67f2cf
to
126d690
Compare
126d690
to
f264753
Compare
f264753
to
8f730fd
Compare
8f730fd
to
4dc9a30
Compare
4dc9a30
to
93081bd
Compare
93081bd
to
93fe1b7
Compare
dff25df
to
e5fa7cc
Compare
e5fa7cc
to
a1f7f0f
Compare
a1f7f0f
to
e73cecc
Compare
e73cecc
to
5cfa735
Compare
5cfa735
to
49d57e0
Compare
49d57e0
to
2915d4b
Compare
2915d4b
to
e50e223
Compare
e50e223
to
40d7ecf
Compare
40d7ecf
to
a6b0b6d
Compare
a6b0b6d
to
c513754
Compare
c513754
to
10742ba
Compare
10742ba
to
283ea6e
Compare
283ea6e
to
95ec461
Compare
95ec461
to
db39c7e
Compare
This PR contains the following updates:
v1.26.0
->v1.59.0
Release Notes
apollographql/router (apollographql/router)
v1.59.0
Compare Source
🚀 Features
General availability of native query planner
The router's native, Rust-based, query planner is now generally available and enabled by default.
The native query planner achieves better performance for a variety of graphs. In our tests, we observe:
apollo.router.query_planning.plan.duration
)The native query planner supports Federation v2 supergraphs. If you are using Federation v1 today, see our migration guide on how to update your composition build step. Subgraph changes are typically not needed.
The legacy, JavaScript, query planner is deprecated in this release, but you can still switch
back to it if you are still using Federation v1 supergraph:
By @sachindshinde, @goto-bus-stop, @duckki, @TylerBloom, @SimonSapin, @dariuszkuc, @lrlna, @clenfest, and @o0Ignition0o.
Ability to skip persisted query list safelisting enforcement via plugin (PR #6403)
If safelisting is enabled, a
router_service
plugin can skip enforcement of the safelist (including therequire_id
check) by adding the keyapollo_persisted_queries::safelist::skip_enforcement
with valuetrue
to the request context.In cases where an operation would have been denied but is allowed due to the context key existing, the attribute
persisted_queries.safelist.enforcement_skipped
is set on theapollo.router.operations.persisted_queries
metric with valuetrue
.By @glasser in https://github.com/apollographql/router/pull/6403
Add fleet awareness plugin (PR #6151)
A new
fleet_awareness
plugin has been added that reports telemetry to Apollo about the configuration and deployment of the router.The reported telemetry include CPU and memory usage, CPU frequency, and other deployment characteristics such as operating system and cloud provider. For more details, along with a full list of data captured and how to opt out, go to our
data privacy policy.
By @jonathanrainer, @nmoutschen, @loshz in https://github.com/apollographql/router/pull/6151
Add fleet awareness schema metric (PR #6283)
The router now supports the
apollo.router.instance.schema
metric for itsfleet_detector
plugin. It has two attributes:schema_hash
andlaunch_id
.By @loshz and @nmoutschen in https://github.com/apollographql/router/pull/6283
Support client name for persisted query lists (PR #6198)
The persisted query manifest fetched from Apollo Uplink can now contain a
clientName
field in each operation. Two operations with the sameid
but differentclientName
are considered to be distinct operations, and they may have distinct bodies.The router resolves the client name by taking the first from the following that exists:
apollo_persisted_queries::client_name
context key that may be set by arouter_service
plugintelemetry.apollo.client_name_header
, which defaults toapollographql-client-name
If a client name can be resolved for a request, the router first tries to find a persisted query with the specified ID and the resolved client name.
If there is no operation with that ID and client name, or if a client name cannot be resolved, the router tries to find a persisted query with the specified ID and no client name specified. This means that existing PQ lists that don't contain client names will continue to work.
To learn more, go to persisted queries docs.
By @glasser in https://github.com/apollographql/router/pull/6198
🐛 Fixes
Fix coprocessor empty body object panic (PR #6398)
Previously, the router would panic if a coprocessor responds with an empty body object at the supergraph stage:
This has been fixed in this release.
By @BrynCooke in https://github.com/apollographql/router/pull/6398
Ensure cost directives are picked up when not explicitly imported (PR #6328)
With the recent composition changes, importing
@cost
results in a supergraph schema with the cost specification import at the top. The@cost
directive itself is not explicitly imported, as it's expected to be available as the default export from the cost link. In contrast, uses of@listSize
to translate to an explicit import in the supergraph.Old SDL link
New SDL link
Instead of using the directive names from the import list in the link, the directive names now come from
SpecDefinition::directive_name_in_schema
, which is equivalent to the change we made on the composition side.By @tninesling in https://github.com/apollographql/router/pull/6328
Fix query hashing algorithm (PR #6205)
The router includes a schema-aware query hashing algorithm designed to return the same hash across schema updates if the query remains unaffected. This update enhances the algorithm by addressing various corner cases to improve its reliability and consistency.
By @Geal in https://github.com/apollographql/router/pull/6205
Fix typo in persisted query metric attribute (PR #6332)
The
apollo.router.operations.persisted_queries
metric reports an attribute when a persisted query was not found.Previously, the attribute name was
persisted_quieries.not_found
, with onei
too many. Now it'spersisted_queries.not_found
.By @goto-bus-stop in https://github.com/apollographql/router/pull/6332
Fix telemetry instrumentation using supergraph query selector (PR #6324)
Previously, router telemetry instrumentation that used query selectors could log errors with messages such as
this is a bug and should not happen
.These errors have now been fixed, and configurations with query selectors such as the following work properly:
By @bnjjj in https://github.com/apollographql/router/pull/6324
More consistent attributes on
apollo.router.operations.persisted_queries
metric (PR #6403)Version 1.28.1 added several unstable metrics, including
apollo.router.operations.persisted_queries
.When an operation is rejected, Router includes a
persisted_queries.safelist.rejected.unknown
attribute on the metric. Previously, this attribute had the valuetrue
if the operation is logged (vialog_unknown
), andfalse
if the operation is not logged. (The attribute is not included at all if the operation is not rejected.) This appears to have been a mistake, as you can also tell whether it is logged via thepersisted_queries.logged
attribute.Router now only sets this attribute to true, and never to false. Note these metrics are unstable and will continue to change.
By @glasser in https://github.com/apollographql/router/pull/6403
Drop experimental reuse fragment query optimization option (PR #6354)
Drop support for the experimental reuse fragment query optimization. This implementation was not only very slow but also very buggy due to its complexity.
Auto generation of fragments is a much simpler (and faster) algorithm that in most cases produces better results. Fragment auto generation is the default optimization since v1.58 release.
By @dariuszkuc in https://github.com/apollographql/router/pull/6353
📃 Configuration
Add version number to distributed query plan cache keys (PR #6406)
The router now includes its version number in the cache keys of distributed cache entries. Given that a new router release may change how query plans are generated or represented, including the router version in a cache key enables the router to use separate cache entries for different versions.
If you have enabled distributed query plan caching, expect additional processing for your cache to update for this router release.
By @SimonSapin in https://github.com/apollographql/router/pull/6406
🛠 Maintenance
Remove catch_unwind wrapper around the native query planner (PR #6397)
As part of internal maintenance of the query planner, the
catch_unwind
wrapper around the native query planner has been removed. This wrapper served as an extra safeguard for potential panics the native planner could produce. Thenative query planner however no longer has any code paths that could panic. We have also
not witnessed a panic in the last four months, having processed 560 million real
user operations through the native planner.
This maintenance work also removes backtrace capture for federation errors, which
was used for debugging and is no longer necessary as we have the confidence in
the native planner's implementation.
By @lrlna in https://github.com/apollographql/router/pull/6397
Deprecate various metrics (PR #6350)
Several metrics have been deprecated in this release, in favor of OpenTelemetry-compatible alternatives:
apollo_router_deduplicated_subscriptions_total
- use theapollo.router.operations.subscriptions
metric'ssubscriptions.deduplicated
attribute.apollo_authentication_failure_count
- use theapollo.router.operations.authentication.jwt
metric'sauthentication.jwt.failed
attribute.apollo_authentication_success_count
- use theapollo.router.operations.authentication.jwt
metric instead. If theauthentication.jwt.failed
attribute is absent orfalse
, the authentication succeeded.apollo_require_authentication_failure_count
- use thehttp.server.request.duration
metric'shttp.response.status_code
attribute. Requests with authentication failures have HTTP status code 401.apollo_router_timeout
- this metric conflates timed-out requests from client to the router, and requests from the router to subgraphs. Timed-out requests have HTTP status code 504. Use thehttp.response.status_code
attribute on thehttp.server.request.duration
metric to identify timed-out router requests, and the same attribute on thehttp.client.request.duration
metric to identify timed-out subgraph requests.The deprecated metrics will continue to work in the 1.x release line.
By @goto-bus-stop in https://github.com/apollographql/router/pull/6350
v1.58.1
Compare Source
🐛 Fixes
Particular
supergraph
telemetry customizations using thequery
selector do not error (PR #6324)Telemetry customizations like those featured in the request limits telemetry documentation now work as intended when using the
query
selector on thesupergraph
layer. Prior to this fix, this was sometimes causing athis is a bug and should not happen
error, but is now resolved.By @bnjjj in https://github.com/apollographql/router/pull/6324
Native query planner now receives both "plan" and "path" limits configuration (PR #6316)
The native query planner now correctly sets two experimental configuration options for limiting query planning complexity. These were previously available in the configuration and observed by the legacy planner, but were not being passed to the new native planner until now:
supergraph.query_planning.experimental_plans_limit
supergraph.query_planning.experimental_paths_limit
By @goto-bus-stop in https://github.com/apollographql/router/pull/6316
v1.58.0
Compare Source
🚀 Features
Support DNS resolution strategy configuration (PR #6109)
The router now supports a configurable DNS resolution strategy for the URLs of coprocessors and subgraphs.
The new option is called
dns_resolution_strategy
and supports the following values:ipv4_only
- Only query forA
(IPv4) records.ipv6_only
- Only query forAAAA
(IPv6) records.ipv4_and_ipv6
- Query for bothA
(IPv4) andAAAA
(IPv6) records in parallel.ipv6_then_ipv4
- Query forAAAA
(IPv6) records first; if that fails, query forA
(IPv4) records.ipv4_then_ipv6
(default) - Query forA
(IPv4) records first; if that fails, query forAAAA
(IPv6) records.You can change the DNS resolution strategy applied to a subgraph's URL:
You can also change the DNS resolution strategy applied to a coprocessor's URL:
By @IvanGoncharov in https://github.com/apollographql/router/pull/6109
Configuration options for HTTP/1 max headers and buffer limits (PR #6194)
This update introduces configuration options that allow you to adjust the maximum number of HTTP/1 request headers and the maximum buffer size allocated for headers.
By default, the router accepts HTTP/1 requests with up to 100 headers and allocates ~400 KiB of buffer space to store them. If you need to handle requests with more headers or require a different buffer size, you can now configure these limits in the router's configuration file:
If you are using the router as a Rust crate, the
http1_request_max_buf_size
option requires thehyper_header_limits
feature and also necessitates using Apollo's fork of the Hyper crate until the changes are merged upstream.You can include this fork by adding the following patch to your Cargo.toml file:
By @IvanGoncharov in https://github.com/apollographql/router/pull/6194
Compress subgraph operations by generating fragments (PR #6013)
The router now compresses operations sent to subgraphs by default by generating fragment
definitions and using them in the operation.
This change enables
generate_query_fragments
by default while disablingexperimental_reuse_query_fragments
. When enabled,experimental_reuse_query_fragments
attempts to intelligently reuse the fragment definitionsfrom the original operation. However, fragment generation with
generate_query_fragments
is much faster and produces better outputs in most cases.If you are relying on the shape of fragments in your subgraph operations or tests, you can opt out of the new algorithm with the configuration below.
By @lrlna in https://github.com/apollographql/router/pull/6013
Add subgraph request id (PR #5858)
The router now supports a subgraph request ID that is a unique string identifying a subgraph request and response. It allows plugins and coprocessors to keep some state per subgraph request by matching on this ID. It's available in coprocessors as
subgraphRequestId
and Rhai scripts asrequest.subgraph.id
andresponse.subgraph.id
.By @Geal in https://github.com/apollographql/router/pull/5858
Add
extensions.service
for all subgraph errors (PR #6191)For improved debuggability, the router now supports adding a subgraph's name as an extension to all errors originating from the subgraph.
If
include_subgraph_errors
istrue
for a particular subgraph, all errors originating in this subgraph will have the subgraph's name exposed as aservice
extension.You can enable subgraph errors with the following configuration:
Consequently, when a subgraph returns an error, it will have a
service
extension with the subgraph name as its value. The following example shows the extension for aproducts
subgraph:By @IvanGoncharov in https://github.com/apollographql/router/pull/6191
Add
@context
support in the native query planner (PR #6310)The
@context
feature is now available in the native query planner.This brings the native query planner to feature parity with the legacy query planner for all Federation v2 graphs. The native query planner can be enabled with the following configuration:
By @clenfest, @TylerBloom in https://github.com/apollographql/router/pull/6310
🐛 Fixes
Remove noisy demand control logs (PR #6192)
Demand control no longer logs warnings when a subgraph response is missing a requested field.
By @tninesling in https://github.com/apollographql/router/pull/6192
Renamed headers' original values can again be propagated (PR #6281)
PR #4535 introduced a regression where the following header propagation config would not work:
The goal of the original PR was to prevent multiple headers from being mapped to a single target header. However, it did not consider renames and instead prevented multiple mappings from the same source header.
The router now propagates headers properly and ensures that a target header is only propagated to once.
By @BrynCooke in https://github.com/apollographql/router/pull/6281
Introspection response deduplication should always produce results (Issue #6249)
To reduce CPU usage, query planning and introspection queries are deduplicated. In some cases, deduplicated introspection queries were not receiving their result. This issue has been fixed, and the router now sends results in all cases.
By @Geal in https://github.com/apollographql/router/pull/6257
Don't log response data upon notification failure for subgraph batching (PR #6150)
For a subgraph batching operation, the router now doesn't log the entire subgraph response when failing to notify a waiting batch participant. This saves the router from logging the large amount of data (PII and/or non-PII data) that a subgraph response may contain.
By @garypen in https://github.com/apollographql/router/pull/6150
Move heavy computation to a thread pool with a priority queue (PR #6247)
The router now avoids blocking threads when executing asynchronous code by using a thread pool with a priority queue.
This improves the performance of the following components that can take non-trivial amounts of CPU time:
The size of the thread pool is based on the number of available CPU cores.
The thread pool replaces the router's prior implementation that used Tokio’s
spawn_blocking
.apollo.router.compute_jobs.queued
is a new gauge metric for the number of items in the thread pool's priority queue.By @SimonSapin in https://github.com/apollographql/router/pull/6247
Limit the amount of GraphQL validation errors returned per response (PR #6187)
When an invalid query is submitted, the router now returns at most one hundred GraphQL parsing and validation errors in a response. This prevents generating too large of a response for a nonsensical document.
By @goto-bus-stop in https://github.com/apollographql/router/pull/6187
Remove placeholders from file upload query variables (PR #6293)
Previously, file upload query variables in subgraph requests incorrectly contained internal placeholders.
According to the GraphQL Multipart Request Spec, these variables should be set to null.
This issue has been fixed by ensuring that the router complies with the specification and improving compatibility with subgraphs handling file uploads.
By @IvanGoncharov in https://github.com/apollographql/router/pull/6293
Overhead processing metrics should exclude subgraph response time when deduplication is enabled (PR #6207)
The router's calculated overhead processing time has been fixed, where the time spent waiting for the subgraph response of a deduplicated request had been incorrectly included.
By @Geal in https://github.com/apollographql/router/pull/6207
Fix demand control panic for custom scalars that represent non-GraphQL-compliant JSON (PR #6288)
Previously, a panic could be triggered in the router's demand control plugin with the following schema:
Then, submitting the query
and variables
During scoring, the demand control plugin would attempt to convert the variable structure into a GraphQL-compliant structure requiring valid GraphQL names as keys. The dot characters in the keys however would cause a panic.
With this fix, only the GraphQL compliant part of the input object is scored, and the arbitrary JSON marked by the custom scalar is scored as an opaque scalar (similar to how built-ins like
Int
orString
are processed).By @tninesling in https://github.com/apollographql/router/pull/6288
Fix incorrect overriding of concrete type names with interface names when merging responses (PR #6250)
When using
@interfaceObject
, differing pieces of data can come back with either concrete types or interface types depending on the source. Previously, receiving the data in a particular order could incorrectly result in the interface name of a type overwriting its concrete name.To make the response merging order-agnostic, the router now checks the schema to ensure concrete types are not overwritten with interfaces or less specific types.
By @tninesling in https://github.com/apollographql/router/pull/6250
🛠 Maintenance
Query planner cache key improvements (Issue #5160)
Several performance improvements have been implemented for query plan cache key generation. In particular, the distributed cache's key format has changed, which adds prefixes to the different key segments to help in debugging.
By @Geal in https://github.com/apollographql/router/pull/6206
Add entity caching invalidation configuration metrics (PR #6286)
We've added metrics for our analytics to know if entity caching invalidation is enabled.
By @bnjjj in https://github.com/apollographql/router/pull/6286
Avoid creating stub span for supergraph events if current span exists (PR #6096)
The router optimized its telemetry implementation by not creating a redundant span when it already has a span available to use the span's extensions for supergraph events.
By @bnjjj in https://github.com/apollographql/router/pull/6096
📚 Documentation
Clarify docs for authorization directive composition (PR #6216)
The docs for authorization directive composition have been clarified, including corrected code examples.
By @Meschreiber in https://github.com/apollographql/router/pull/6216
v1.57.1
Compare Source
🐛 Fixes
Progressive override: fix query planner cache warmup (PR #6108)
This fixes an issue in progressive override where the override labels were not transmitted to the query planner during cache warmup. Queries were correctly using the overridden fields at first, but after an update, reverted to non overridden fields, and could not recover.
By @Geal in https://github.com/apollographql/router/pull/6108
v1.57.0
Compare Source
🚀 Features
Remove legacy schema introspection (PR #6139)
Schema introspection in the router now runs natively without JavaScript. We have high confidence that the new native implementation returns responses that match the previous Javascript implementation, based on differential testing: fuzzing arbitrary queries against a large schema, and testing a corpus of customer schemas against a comprehensive query.
Changes to the router's YAML configuration:
experimental_introspection_mode
key has been removed, with thenew
mode as the only behavior in this release.supergraph.query_planning.legacy_introspection_caching
key is removed, with the behavior in this release now similar to what wasfalse
: introspection responses are not part of the query plan cache but instead in a separate, small in-memory—only cache.When using the above deprecated configuration options, the router's automatic configuration migration will ensure that existing configuration continue to work until the next major version of the router. To simplify major upgrades, we recommend reviewing incremental updates to your YAML configuration by comparing the output of
./router config upgrade --config path/to/config.yaml
with your existing configuration.By @SimonSapin in https://github.com/apollographql/router/pull/6139
Support new
request_context
selector for telemetry (PR #6160)The router supports a new
request_context
selector for telemetry that enables access to the supergraph schema ID.You can configure the context to access the supergraph schema ID at the router service level:
You can use the selector in any service at any stage. While this example applies to
events
attributes, the selector can also be used on spans and instruments.By @bnjjj in https://github.com/apollographql/router/pull/6160
Support reading and setting
port
on request URIs using Rhai (Issue #5437)Custom Rhai scripts in the router now support the
request.uri.port
andrequest.subgraph.uri.port
functions for reading and setting URI ports. These functions enable you to update the full URI for subgraph fetches. For example:By @lleadbet in https://github.com/apollographql/router/pull/5439
🐛 Fixes
Fix various edge cases for
__typename
field (PR #6009)The router now correctly handles the
__typename
field used on operation root types, even when the subgraph's root type has a name that differs from the supergraph's root type.For example, given a query like this:
Even if the subgraph's root type returns a
__typename
that differs fromQuery
, the router will still useQuery
as the value of the__typename
field.This change also includes fixes for other edge cases related to the handling of
__typename
fields. For a detailed technical description of the edge cases that were fixed, please see this description.By @IvanGoncharov in https://github.com/apollographql/router/pull/6009
Support
uri
andmethod
properties on router "request" objects in Rhai (PR #6147)The router now supports accessing
request.uri
andrequest.method
properties from custom Rhai scripts. Previously, when trying to accessrequest.uri
andrequest.method
on a router request in Rhai, the router would return error messages stating the properties were undefined.An example Rhai script using these properties:
By @andrewmcgivery in https://github.com/apollographql/router/pull/6114
Cost calculation for subgraph requests with named fragments (PR #6162)
In some cases where subgraph GraphQL operations contain named fragments and abstract types, demand control used the wrong type for cost calculation, and could reject valid operations. Now, the correct type is used.
This fixes errors of the form:
By @goto-bus-stop in https://github.com/apollographql/router/pull/6162
Federation v2.9.3 (PR #6161)
This release updates to Federation v2.9.3, with query planner fixes:
__typename
may be omitted in the subgraph query.@key
/@requires
selection sets were not optimized away.@context
/@fromContext
.By @sachindshinde in https://github.com/apollographql/router/pull/6161
v1.56.0
Compare Source
🚀 Features
Native query planner is now in public preview
The native query planner is now in public preview. You can configure the
experimental_query_planner_mode
option in the router configuration YAML to change the mode of the native query planner. The following modes are available:new
: Enable only the new Rust-native query planner in the hot-path of query execution.legacy
: Enable only the legacy JavaScript query planner in the hot-path of query execution.both_best_effort
: Enables both the new and legacy query planners. They are configured in a comparison-based mode of operation with the legacy planner in the hot-path and the and the new planner in the cold-path. Comparisons are made between the two plans on a sampled basis and metrics are available to analyze the differences in aggregate.Support loading Apollo key from file (PR #5917)
You can now specific the location to a file containing the Apollo key that's used by Apollo Uplink and usage reporting. The router now supports both the
--apollo-key-path
CLI argument and theAPOLLO_KEY_PATH
environment variable for passing the file containing your Apollo key.Previously, the router supported only the
APOLLO_KEY
environment variable to provide the key. The new CLI argument and environment variable help users who prefer not to pass sensitive keys through environment variables.Note: This feature is unavailable for Windows.
By @lleadbet in https://github.com/apollographql/router/pull/5917
🐛 Fixes
Prevent sending internal
apollo_private.*
attributes to Jaeger collector (PR #6033)When using the router's Jaeger collector to send traces, you will no longer receive span attributes with the
apollo_private.
prefix. Those attributes were incorrectly sent, as that prefix is reserved for internal attributes.By @bnjjj in https://github.com/apollographql/router/pull/6033
Fix displaying custom event attributes on subscription events (PR #6033)
The router now properly displays custom event attributes that are set with selectors at the supergraph level.
An example configuration:
By @bnjjj in https://github.com/apollographql/router/pull/6033
Update to Federation v2.9.2 (PR #6069)
This release updates to Federation v2.9.2, with a small fix to the internal
__typename
optimization and a fix to prevent argument name collisions in the@context
/@fromContext
directives.By @dariuszkuc in https://github.com/apollographql/router/pull/6069
📃 Configuration
Add metrics for Rust vs. Deno configuration values (PR #6056)
To help track the migration from JavaScript (Deno) to native Rust implementations, the router now reports the values of the following configuration options to Apollo:
apollo.router.config.experimental_query_planner_mode
apollo.router.config.experimental_introspection_mode
By @goto-bus-stop in https://github.com/apollographql/router/pull/6056
v1.55.0
Compare Source
🚀 Features
Support aliasing standard attributes for telemetry (Issue #5930)
The router now supports creating aliases for standard attributes for telemetry.
This fixes issues where standard attribute names collide with reserved attribute names. For example, the standard attribute name
entity.type
is a reserved attribute name for New Relic, so it won't work properly. Moreoverentity.type
is inconsistent with our other GraphQL attributes prefixed withgraphql.
The example configuration below renames
entity.type
tographql.type.name
:By @bnjjj in https://github.com/apollographql/router/pull/5957
Enable router customizations to access demand control info (PR #5972)
Rhai scripts and coprocessors can now access demand control information via the context. For more information on Rhai constants to access demand control info, see available Rhai API constants.
By @tninesling in https://github.com/apollographql/router/pull/5972
Support Redis connection pooling (PR #5942)
The router now supports Redis connection pooling for APQs, query planners and entity caches. This can improve performance when there is contention on Redis connections or latency in Redis calls.
By @Geal in https://github.com/apollographql/router/pull/5942
🐛 Fixes
Remove unused fragments and input arguments when filtering operations (PR #5952)
This release fixes the authorization plugin's query filtering to remove unused fragments and input arguments if the related parts of the query are removed. Previously the plugin's query filtering generated validation errors when planning certain queries.
By @Geal in https://github.com/apollographql/router/pull/5952
Hot-reloads will no longer interrupt certain gauges (PR #5996, PR #5999, PR #5999)
Previously when the router hot-reloaded a schema or a configuration file, the following gauges stopped working:
apollo.router.cache.storage.estimated_size
apollo_router_cache_size
apollo.router.v8.heap.used
apollo.router.v8.heap.total
apollo.router.query_planning.queued
This issue has been fixed in this release, and the gauges now continue to function after a router hot-reloads.
By @BrynCooke in https://github.com/apollographql/router/pull/5996 and https://github.com/apollographql/router/pull/5999 and https://github.com/apollographql/router/pull/6012
Datadog sample propagation will respect previous sampling decisions (PR #6005)
PR #5788 introduced a regression where sampling was set on propagated headers regardless of the sampling decision in the router or upstream.
This PR reverts the code in question and adds a test to check that a non-sampled request doesn't result in sampling in the downstream subgraph service.
By @BrynCooke in https://github.com/apollographql/router/pull/6005
Include request variables when scoring for demand control (PR #5995)
Demand control scoring in the router now accounts for variables in queries.
By @tninesling in https://github.com/apollographql/router/pull/5995
📃 Configuration
Enable new and old schema introspection implementations by default (PR #6014)
Starting with this release, if schema introspection is enabled, the router runs both the old Javascript implementation and a new Rust implementation of its introspection logic by default.
The more performant Rust implementation will eventually replace the Javascript implementation. For now, both implementations are run by default so we can definitively assess the reliability and stability of the Rust implementation before removing the Javascript one.
You can still toggle between implementations using the
experimental_introspection_mode
configuration key. Its valid values:new
runs only Rust-based validationlegacy
runs only Javascript-based validationboth
(default) runs both in comparison and logs errors if differences ariseHaving
both
as the default causes no client-facing impact. It will record and output the metrics of its comparison as aapollo.router.operations.introspection.both
counter. (Note: if this counter in your metrics hasrust_error = true
oris_matched = false
, please open an issue with Apollo.)Note: schema introspection itself is disabled by default, so its implementation(s) are run only if it's enabled in your configuration:
By @SimonSapin in https://github.com/apollographql/router/pull/6014
🧪 Experimental
Allow disabling persisted-queries-based query plan cache prewarm on schema reload
The router supports the new
persisted_queries.experimental_prewarm_query_plan_cache.on_reload
configuration option. It toggles whether a query plan cache that's prewarmed upon loading a new schema includes operations from persisted query lists. Its default istrue
. Setting itfalse
precludes operations from persisted query lists from being added to the prewarmed query plan cache.Some background about the development of this option:
In router v1.31.0, we started including operations from persisted query lists when the router prewarms the query plan cache when loading a new schema.
Then in router v1.49.0, we let you also prewarm the query plan cache from the persisted query list during router startup by setting
persisted_queries.experimental_prewarm_query_plan_cache
to true.In this release, we now allow you to disable the original feature so that the router can prewarm only recent operations from the query planning cache (and not operations from persisted query lists) when loading a new schema.
Note: the option added in v1.49.0 has been renamed from
persisted_queries.experimental_prewarm_query_plan_cache
topersisted_queries.experimental_prewarm_query_plan_cache.on_startup
. Existing configuration files will keep working as before, but with a warning that can be resolved by updating your config file:By @glasser in [https://gi
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.