As evidenced by the sheer bulk of patterns necessary to cover the spectrum of SUSE CaaS Platform... it is a huge issue that we are mandating patterns be applied on just one space-separated token:
Each extra space-separated word necessitates a new pattern. Checking for "Container as a Service" v/ "Container a s a Service" necessitates multiple pattern groups, despite the difference being just one small extra space.
This also creates a performance issue: fewer big patterns perform much better than many smaller ones. So, if we could even just on the consumer side concatenate the various patterns belonging to patterngroup, that'd already be fantastic.
As evidenced by the sheer bulk of patterns necessary to cover the spectrum of SUSE CaaS Platform... it is a huge issue that we are mandating patterns be applied on just one space-separated token:
Each extra space-separated word necessitates a new pattern. Checking for "Container as a Service" v/ "Container a s a Service" necessitates multiple pattern groups, despite the difference being just one small extra space.
This also creates a performance issue: fewer big patterns perform much better than many smaller ones. So, if we could even just on the consumer side concatenate the various patterns belonging to patterngroup, that'd already be fantastic.