Presumably, it is because deepCopy does not begin with the prefix copy. So you may want to change to something like copyWithDeepCopiedValues (or something like that), and then see if the analyzer flags that. Update As Alexsander noted, you can use attributes to denote reference counting intent. This should (IMO) be the exception to the … Read more
Updated answer for Hibernate Search 6 With Hibernate Search 6, you can define a second analyzer, identical to your “ngram” analyzer except that it does not have an ngram filter, and assign it as the searchAnalyzer for your field: public class Hospital { // … @FullTextField(analyzer = “ngram”, searchAnalyzer = “my_analyzer_without_ngrams”) private String name = … Read more
“my_field2”: { “properties”: { “title”: { “type”: “string”, “index”: “not_analyzed” } } } Check you here, https://www.elastic.co/guide/en/elasticsearch/reference/1.4/mapping-core-types.html, for further info.
This is an interesting use case. Here’s my take: { “settings”: { “analysis”: { “analyzer”: { “my_ngram_analyzer”: { “tokenizer”: “my_ngram_tokenizer”, “filter”: [“lowercase”] }, “my_edge_ngram_analyzer”: { “tokenizer”: “my_edge_ngram_tokenizer”, “filter”: [“lowercase”] }, “my_reverse_edge_ngram_analyzer”: { “tokenizer”: “keyword”, “filter” : [“lowercase”,”reverse”,”substring”,”reverse”] }, “lowercase_keyword”: { “type”: “custom”, “filter”: [“lowercase”], “tokenizer”: “keyword” } }, “tokenizer”: { “my_ngram_tokenizer”: { “type”: “nGram”, “min_gram”: … Read more