# Different wildcard handling **URL:** \ **Category:** Elasticsearch\ **Created:** [February 7, 2013, 12:29pm UTC](https://discuss.elastic.co/t/different-wildcard-handling/10651 "2013-02-07T12:29:28Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![andrea\_crotti](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@andrea\_crotti](https://discuss.elastic.co/u/andrea_crotti)\ **Post date:** [February 7, 2013, 12:29pm UTC](https://discuss.elastic.co/t/different-wildcard-handling/10651/1 "2013-02-07T12:29:28Z")
I'm having a crisis situation with elasticsearch here, we use a couchdb river, and I get different results running on my local ES and the production one. It looks like for example that wildcards, something like StringQuery("responding\* to\*", default\_operator='AND') works in one and doesn't work in the other one. We didn't touch ES, but we are ruling out all the things which can't be and I'm finishing the possibilities. The only thing maybe might be the mapping, which is dynamically updated from the river. The problem is that the mapping is massive and not really easy to compare, and I don't see how that should have just changed by itself either. Any idea? Thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:52am UTC](https://discuss.elastic.co/t/different-wildcard-handling/10651/2 "2017-07-06T02:52:33Z")
Closed on July 6, 2017, 2:52am UTC