Usage of FastURLFilter via ES JSONURLFilterWrapper

[jnioche]

Discussed in #1012

^{Originally posted by sebastian-nagel December 12, 2022}
The FastURLFilter configuration file contains a JSON array, not a JSON object. How can it be put into ES?

When I try to put a FastURLFilter configuration file into ES (as described in JSONURLFilterWrapper, ES responds with an error (indicating that ES expects a JSON object):

curl -XPUT 'localhost:9200/config/config/fast.urlfilter.json?pretty' -H 'Content-Type: application/json' -d @fast.urlfilter.json
{
  "error" : {
    "root_cause" : [
      {
        "type" : "mapper_parsing_exception",
        "reason" : "failed to parse"
      }
    ],
    "type" : "mapper_parsing_exception",
    "reason" : "failed to parse",
    "caused_by" : {
      "type" : "not_x_content_exception",
      "reason" : "Compressor detection can only be called on some xcontent bytes or compressed xcontent bytes"
    }
  },
  "status" : 400
}
```</div>

[jnioche]

@sebastian-nagel we could change the format so that it optionally consumes a simple object with a single field, the value of which is the array.
When using with the ES wrapper, you'd need to have the field but if used directly you wouldn't necessarily need to.
What do you think?

[sebastian-nagel]

so that it optionally consumes a simple object with a single field, the value of which is the array

Yes, makes sense. Ev., could also require a predefined field "config" or "content" or similar. This special case needs to be documented anyway, so it's maybe clearer to require a specific field name.

[jnioche]

Fixed by allowing an optional top level field. Thanks @sebastian-nagel