Rollups not causing shards failures in discover for index pattern * when they are not hidden

[xavier-isecurity]

Is your feature request related to a problem? Please describe.
Rollups can't do searchs with size different than zero. But when we do a discover search, it has a size defined different than zero. If there are rollups created, and they are not hidden, they will trigger shard exception if we search on discover using "*" pattern.

I need rollups not hidden to control them with ISM policy, but I do use "*" index patterns, and it is returning the shard exception everytime I try to use discover.

Describe the solution you'd like
Since rollups can't do searchs with size different than zero, they should be excluded from discover, even if they are not hidden. But still able to execute ism policies and rollovers.

Describe alternatives you've considered
Another way to achieve my desired result, is that ISM policies could be applied also with aliases and not only index prefixes. And that ISM policies are allowed for hidden rollup indexes.

If there is another way to turn this around, please let me know.

Additional context
Exception on discover:

  "took": 420,
  "timed_out": false,
  "_shards": {
    "total": 7,
    "successful": 5,
    "skipped": 3,
    "failed": 2,
    "failures": [
      {
        "shard": 0,
        "index": "rollup_test-000001",
        "node": "-U7StgJ0QBSNOtmWa-9l7Q",
        "reason": {
          "type": "illegal_argument_exception",
          "reason": "Rollup search must have size explicitly set to 0, but found 500"
        }
      }
    ]
  },

[bowenlan-amzn]

If your rollup indexes have certain prefix rollup-, you can create index pattern in the dashboard to not include them.

There's a cluster setting plugins.rollup.search.enabled to disable rollup search function which requires size=0, but if you uses "*", it still doesn't make sense to search rollup indexes along with your normal indexes.

[xavier-isecurity]

If your rollup indexes have certain prefix rollup-, you can create index pattern in the dashboard to not include them.

There's a cluster setting plugins.rollup.search.enabled to disable rollup search function which requires size=0, but if you uses "*", it still doesn't make sense to search rollup indexes along with your normal indexes.

So it happens that even if I exclude the indexes on the searches it returns errors.

So I did find a turn around to this issue.

I added an alias for all index that matters to me when I search with *, not including rollup in this alias. Problem solved.