# Dialect is null. What dialect we use for ElasticSearch

**URL:** <https://discourse.hibernate.org/t/dialect-is-null-what-dialect-we-use-for-elasticsearch/4680>\
**Category:** Hibernate ORM\
**Created:** [October 21, 2020, 4:20pm UTC](https://discourse.hibernate.org/t/dialect-is-null-what-dialect-we-use-for-elasticsearch/4680 "2020-10-21T16:20:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![yrodiere](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.hibernate.org/yrodiere/32/1760_2.png) [@yrodiere](https://discourse.hibernate.org/u/yrodiere)\
**Post date:** [October 21, 2020, 4:29pm UTC](https://discourse.hibernate.org/t/dialect-is-null-what-dialect-we-use-for-elasticsearch/4680/2 "2020-10-21T16:29:50Z")

</div>

Moving to Hibernate ORM.

Even though you’re using Hibernate Search, this error clearly is related to Hibernate ORM, and Hibernate Search does not care (at all) what dialect you use to communicate with your database.

Regarding your error… I would bet on a configuration problem in Spring Boot.

Make sure you don’t create the `EntityManagerFactory`/`SessionFactory` yourself, but leave that to Spring Boot. You mentioned [here](https://discourse.hibernate.org/t/error-creating-bean-with-name-entitymanagerfactory-defined-in-class-path-resource/4675/2) that you declared an `EntityManagerFactory` bean, and I’m almost certain this wasn’t a good idea.

See [my answer](https://discourse.hibernate.org/t/error-creating-bean-with-name-entitymanagerfactory-defined-in-class-path-resource/4675/3) to solve the problem you had before declaring that bean.

---

_[View the full topic](https://discourse.hibernate.org/t/dialect-is-null-what-dialect-we-use-for-elasticsearch/4680)._