# Mapping between index and search analyzer **URL:** \ **Category:** Elasticsearch\ **Created:** [September 26, 2011, 2:49pm UTC](https://discuss.elastic.co/t/mapping-between-index-and-search-analyzer/5451 "2011-09-26T14:49:42Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Trym](https://avatars.discourse-cdn.com/v4/letter/t/73ab20/32.png) [@Trym](https://discuss.elastic.co/u/Trym)\ **Post date:** [September 26, 2011, 2:49pm UTC](https://discuss.elastic.co/t/mapping-between-index-and-search-analyzer/5451/1 "2011-09-26T14:49:42Z")
Hi As I understand it is important to use the same analyzer type when indexing and searching, but I have a hard time figuring out which index analyzer that matches the query "analyzer". If I e.g. want to search on prefix of words I suspect that I should use the QueryBuilders.prefixQuery(...) but which index analyzer fits this (an NGram analyzer)? Is there a general rule of thumb, documentation or how can I figure this out myself? Furthermore I have a vague idea that searching can be done using queries and filters and that filters are faster (see [http://www.elasticsearch.org/guide/reference/query-dsl/](http://www.elasticsearch.org/guide/reference/query-dsl/)), but I cannot figure out how to make a filter search in Java. Any help is great. Best regards Trym ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [September 26, 2011, 5:22pm UTC](https://discuss.elastic.co/t/mapping-between-index-and-search-analyzer/5451/2 "2011-09-26T17:22:36Z")
You can do prefix query on terms broken down by any analyzer. The standard analyzer can break: "brown fox" into two terms, "brown" and "fox", and you can do a prefix query on "bro" and find that document. You can use ngrams in order to analyze the text differently, in which case, usually, you won't need to do prefix query because of the way ngrams work. Regarding using filters with the Java API, for example: client.prepareSearch("my\_index") .setQuery(QueryBuilders.filteredQuery( QueryBuilders.matchAllQuery(), FilterBuilders.termFilter("field", "prefix") )) .execute().actionGet(); On Mon, Sep 26, 2011 at 5:49 PM, Trym [trym@sigmat.dk](mailto:trym@sigmat.dk) wrote: > Hi > > As I understand it is important to use the same analyzer type when indexing > and searching, > but I have a hard time figuring out which index analyzer that matches the > query "analyzer". > If I e.g. want to search on prefix of words I suspect that I should use the > QueryBuilders.prefixQuery(...) but which index analyzer fits this (an NGram > analyzer)? > Is there a general rule of thumb, documentation or how can I figure this > out myself? > > Furthermore I have a vague idea that searching can be done using queries > and filters and that filters are faster (see > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/query-dsl/)), > but I cannot figure out how to make a filter search in Java. > > Any help is great. > > Best regards Trym ---
**Author:** ![Trym](https://avatars.discourse-cdn.com/v4/letter/t/73ab20/32.png) [@Trym](https://discuss.elastic.co/u/Trym)\ **Post date:** [September 27, 2011, 6:08am UTC](https://discuss.elastic.co/t/mapping-between-index-and-search-analyzer/5451/3 "2011-09-27T06:08:57Z")
Hi Thanks for your kind reply. I hoped there would be a performance gain when searching for prefix queries if I had used the ngram analyzer when indexing, but this seems not to be the case? Can you describe a use case that could not be solved without the nGram index analyzer? The Java documentation on QueryBuilders.filteredQuery says that it applies a filter on the result of another query. Does that mean that the matchAllQuery returns all result to the callee and then the callee filters these (and can I think of the callee as a node, a shard or a Lucene instance)? And does Lucene have some similar concepts and can you point me to a description of these? Thanks in advance. Best regards Trym ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [September 27, 2011, 9:15pm UTC](https://discuss.elastic.co/t/mapping-between-index-and-search-analyzer/5451/4 "2011-09-27T21:15:32Z")
On Tue, Sep 27, 2011 at 9:08 AM, Trym [trym@sigmat.dk](mailto:trym@sigmat.dk) wrote: > Hi > > Thanks for your kind reply. > > I hoped there would be a performance gain when searching for prefix queries > if I had used the ngram analyzer when indexing, but this seems not to be the > case? > Can you describe a use case that could not be solved without the nGram > index analyzer? With ngrams, you usually don't need to use prefix queries, so thats your perf gain. > The Java documentation on QueryBuilders.\*\*filteredQuery says that it > applies a filter on the result of another query. Does that mean that the > matchAllQuery returns all result to the callee and then the callee filters > these (and can I think of the callee as a node, a shard or a Lucene > instance)? And does Lucene have some similar concepts and can you point me > to a description of these? Yes, Lucene has those concepts. FilteredQuery, Filters, and Queries. > Thanks in advance. > > Best regards Trym ---
**Author:** ![Trym](https://avatars.discourse-cdn.com/v4/letter/t/73ab20/32.png) [@Trym](https://discuss.elastic.co/u/Trym)\ **Post date:** [September 28, 2011, 6:23am UTC](https://discuss.elastic.co/t/mapping-between-index-and-search-analyzer/5451/5 "2011-09-28T06:23:06Z")
Hi Shay Thanks again for your reply. 1. What performance penalty do I get when searching using a PrefixQuery if I have used the standard index analyzer? 2. The Java documentation on QueryBuilders.\*\*filteredQuery says that it applies a filter on the result of another query. Does that mean that the matchAllQuery returns all result to the callee and then the callee filters these (and can I think of the callee as a node, a shard or a Lucene instance)? 3. I will read further about Lucene Thanks for any further comments. Best regards Trym ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 2, 2011, 8:00am UTC](https://discuss.elastic.co/t/mapping-between-index-and-search-analyzer/5451/6 "2011-10-02T08:00:23Z")
On Wed, Sep 28, 2011 at 9:23 AM, Trym [trym@sigmat.dk](mailto:trym@sigmat.dk) wrote: > Hi Shay > > Thanks again for your reply. > > 1. What performance penalty do I get when searching using a PrefixQuery if > I have used the standard index analyzer? The analyzer is not really relevant here. Prefix query will cause all terms that start with the prefix to be enumerated. > 1. The Java documentation on QueryBuilders. **filteredQuery** says that it > applies a filter on the result of another query. Does that mean that the > matchAllQuery returns all result to the callee and then the callee filters > these (and can I think of the callee as a node, a shard or a Lucene > instance)? No, the query execution is done per shard. A query can be a filtered query, and then it will apply a filter to a query, but it will still execute on the "shard" level. > 1. I will read further about Lucene > > Thanks for any further comments. > > Best regards Trym ---
**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, 3:53am UTC](https://discuss.elastic.co/t/mapping-between-index-and-search-analyzer/5451/7 "2017-07-06T03:53:11Z")