"maxlen" or "maxbytes" or "max<something>" if we don't want to deal with parsing <, >, or = in the value.

I think it should be consistent with what we do for filesize:

Search for file of given size, in kilobytes (kilobyte means 1024 bytes). The syntax is:

filesize:{number} or filesize:>{number} - file with size at least given number
filesize:<{number} - file with size no more than given number
filesize:{number},{number} - file with size between given numbers

Change 889074 had a related patch set uploaded (by DCausse; author: DCausse):

[mediawiki/extensions/CirrusSearch@master] Index the text_bytes field

https://gerrit.wikimedia.org/r/889074

Change 889075 had a related patch set uploaded (by DCausse; author: DCausse):

[mediawiki/extensions/CirrusSearch@master] Add new textbytes keyword

https://gerrit.wikimedia.org/r/889075

Sadly I had to change the elasticsearch mapping to allow this and thus this will have to wait for a full re-index after the first patch is merged before enabling the new textbytes keyword.

Change 889074 merged by jenkins-bot:

[mediawiki/extensions/CirrusSearch@master] Index the text_bytes field

https://gerrit.wikimedia.org/r/889074

Waiting for a re-index to enable this feature.

re-index is currently running, mappings look as expected for indices that have completed reindexing already. It's up to r, will probably take a few more days and we can ship the keyword in next weeks train with any luck.

Reindex is done for the production wikis, cloudelastic is not yet done but should not be a blocker for this patch.

Change 889075 merged by jenkins-bot:

[mediawiki/extensions/CirrusSearch@master] Add new textbytes keyword

https://gerrit.wikimedia.org/r/889075

Thanks for the patches and reindexing work. Can we close this task?

@kostajh sure, @Gehel should take care of closing soon (once the feature is active on group2 wikis, hopefully today)