N-gram and edge_N-gram differences do not work anymore

yobottehg → changed the visibility of the branch 3504243-n-gram-and-edgen-gram to hidden.

this is ony a demonstration.

The phpstan fails come out of deprecations of opensearch 2.4.0

Is this something you can change directly on opensearch? We don't try and provide all the possible settings via the module. There would just be too many.

Yes sure it is possible.

However previously it was possible to use this module with zero config opensearch containers like on lando / ddev / platform.sh.

Now this this not work anymore if an ngram or edge ngram field is used as the min / max config set on the analyser is not enough anymore.

New commits go into 3.x

@yobottehg I've rebased this on 3.x.

Can you explain why you chose a value of 20 rather than any other arbitrary number? Also, should this be configurable?

Made it configurable and added an update hook. @yobottehg it would be great if you could test this out manually.

Can you explain why you chose a value of 20 rather than any other arbitrary number? Also, should this be configurable?

I chose 20 because of the setting of min_gram: 1 and max_gram: 20 on the analyser.

Made it configurable and added an update hook. @yobottehg it would be great if you could test this out manually.

Tested it locally. After setting the number to atleast 19, updating an index with edge-n_gram fields worked again.

Committed to 2x. and 3.x. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.