[Vis: Default editor] EUIficate regex control

[maryia-lapata]

Summary

I started migration of regex control for aggregation parameter and noticed that that control is used in Significant Terms aggregation only. And the request fails with 400 status code when that field is defined.

On the screenshot below you can see that Significant Terms aggregation with a pattern fails with 400 code whereas Terms aggregation with a pattern is run well, though the doc says that filtering values functionality in Significant Terms is the same as in Terms.

Significant Terms request fails with the reason: Unknown parameter in Include/Exclude clause: pattern. The request body was:

Terms request is succeeded. The request body was:

As you may note the include field has the different types: Significant Terms sends an object and fails because of unknown parameter in Include, Terms sends a string. I guess that the API was changed and Significant Terms config wasn't undated.

Since the Include/Exclude pattern configuration of Significant Terms should be the same as for Terms, I changed the model structure for Significant Terms's pattern parameters: include: { pattern: '*' } -> include: '*'.

Part of #30922

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[timroes]

Closing this in favor of moving the significant terms include/exclude over to a string (see #33263). Sorry for the unnecessary work :-(

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request