# Can you tune the split\_on\_case\_change setting on the word delimiter token filter? **URL:** \ **Category:** Elasticsearch\ **Created:** [March 12, 2021, 3:20pm UTC](https://discuss.elastic.co/t/can-you-tune-the-split-on-case-change-setting-on-the-word-delimiter-token-filter/267102 "2021-03-12T15:20:00Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![peterbe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peterbe/32/14836_2.png) [@peterbe](https://discuss.elastic.co/u/peterbe)\ **Post date:** [March 12, 2021, 3:20pm UTC](https://discuss.elastic.co/t/can-you-tune-the-split-on-case-change-setting-on-the-word-delimiter-token-filter/267102/1 "2021-03-12T15:20:00Z")
I have a love-hate relationship with [`split_on_case_change`](https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-word-delimiter-tokenfilter.html#word-delimiter-tokenfilter-configure-parms) My problem is that only certain words make sense to split on case change. For example, I'd like to treat `TypedArray` as `Typed`, `Array`. But I don't want to split up `forEach` into `for`,`each` because then `for` is treated as the common stop word that it is. I _think_ it would be nice if I could configure `split_on_case_change` such that it only splits by case if the first character is `[A-Z]`. E.g. `[A-Z][a-z]+[A-Z][a-z]+...`. But _not_ for `[a-z]+[A-z][a-z]+...`. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 9, 2021, 3:20pm UTC](https://discuss.elastic.co/t/can-you-tune-the-split-on-case-change-setting-on-the-word-delimiter-token-filter/267102/2 "2021-04-09T15:20:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.