Hello Leandro Freitas, Thanks for this report. First, please note that the DataType enum you mentioned is in an implementation package: you should not use it. Second, the Elasticsearch integration currently does not allow using any of the datatypes that are not supported in the Lucene integration. The main reason is that until now, we concentrated on getting the same level of feature coverage in the Elasticsearch integration as in the Lucene integration. We are currently starting the work on the next major version of Hibernate Search (6), and we expect that version to be easier to configure for non-Lucene integrations, so we could introduce non-Lucene data types in that release. But I won't lie to you: it's highly unlikely to happen in the 5.x branch, mainly because the APIs are very Lucene-oriented, which makes it difficult to introduce Elasticsearch-specific concepts. In the meantime, if you need completion features, you can achieve similar results with an index field whose analyzer includes an edgeNGram token filter. Cheers, |