I think I'm just going to no-op this migration.

This is now possible.

This is now supported.

These field functions have somewhat-weird scopes/context.

Getting through the ngram index alone isn't good enough, because LIKE operators against utf8mb4_unicode_ci treat combining accents as separate characters:

Normalizer requires intl which I'm hesitant to add a dependency on.

One possible improvement remains here: in streaming mode, HTTPSFuture will not "Accept-Encoding: gzip" and can not inflate responses. Today, this only applies to arc download.

I get the sense that most of this discussion is around diffs, but we've been having issues with the default size of 8 showing in code blocks in Phriction causing more wrapping than we would like.

There's also one minor related concern in PHI1638 that I want to take care of here, since it's adjacent.

In fairness, "SetInputFilter DEFLATE" is documented as uniquely opinionated, if you catch this box and read between the lines a little bit:

A grand aventure in PHI1679 led to identifying the Apache "SetInputFilter DEFLATE" directive as a problem with implementing compression.

This appears to be working properly, now.

Query parsing of certain unusual or ambiguous inputs has changed slightly.

wilds and experimental have mostly collapsed together into master, and this is survived by T13488.

These are in better shape now:

I think I'm going to remove these workflows outright:

We currently have no interest in this from customers, so I don't plan to pursue it. If customer interest arises, there's a plausible pathway forward.