hibernate-search | Hibernate Search : full-text search for domain model | Object-Relational Mapping library

 by   hibernate Java Version: 5.11.11.Final License: Non-SPDX

kandi X-RAY | hibernate-search Summary

kandi X-RAY | hibernate-search Summary

hibernate-search is a Java library typically used in Utilities, Object-Relational Mapping, Hibernate applications. hibernate-search has no bugs, it has no vulnerabilities, it has build file available and it has high support. However hibernate-search has a Non-SPDX License. You can download it from GitHub, Maven.

Hibernate Search automatically extracts data from Hibernate ORM entities to push it to local Apache Lucene indexes or remote Elasticsearch indexes.

            kandi-support Support

              hibernate-search has a highly active ecosystem.
              It has 466 star(s) with 241 fork(s). There are 36 watchers for this library.
              It had no major release in the last 12 months.
              hibernate-search has no issues reported. There are 2 open pull requests and 0 closed requests.
              It has a positive sentiment in the developer community.
              The latest version of hibernate-search is 5.11.11.Final

            kandi-Quality Quality

              hibernate-search has 0 bugs and 0 code smells.

            kandi-Security Security

              hibernate-search has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              hibernate-search code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              hibernate-search has a Non-SPDX License.
              Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

            kandi-Reuse Reuse

              hibernate-search releases are available to install and integrate.
              Deployable package is available in Maven.
              Build file is available. You can build the component from source.
              Installation instructions, examples and code snippets are available.
              hibernate-search saves you 91556 person hours of effort in developing the same functionality from scratch.
              It has 99806 lines of code, 9489 functions and 1420 files.
              It has medium code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi has reviewed hibernate-search and discovered the below as its top functions. This is intended to give you an instant insight into hibernate-search implemented functionality, and help decide if they suit your requirements.
            • Initializes the search state
            • Creates the default backend factory
            • Creates backend instances
            • Creates a backend with the given name
            • Gets the index field type
            • Gets the field type
            • Gets the term vector
            • Returns the index field type
            • Resolve the normalization values
            • In JsonQuery
            • Builds MPB
            • Start the outbox strategy
            • Indexed embedded objects
            • Called when the entity is dirty
            • Get the GeoPointFieldType
            • Returns the Lucene index field type
            • Executes the pulse
            • Returns the options for the given type
            • Start the downloader
            • Count all documents
            • Creates a partition plan
            • Pushes a heartbeat
            • Create Elasticsearch implementation
            • Initialize the reader
            • Resolves the value
            • Loads the entities
            Get all kandi verified functions for this library.

            hibernate-search Key Features

            No Key Features are available at this moment for hibernate-search.

            hibernate-search Examples and Code Snippets

            No Code Snippets are available at this moment for hibernate-search.

            Community Discussions


            Unable to find TermRangeQuery in hibernate-search 6
            Asked 2022-Feb-22 at 14:59

            I am not able to find below class in hibernate-search 6

            import org.apache.lucene.search.TermRangeQuery;

            is there any similar class available?



            Answered 2022-Feb-22 at 14:59

            This is an Apache Lucene class, not a Hibernate Search class. And this class still exists in the version of Lucene (8) used by Hibernate Search 6, so I don't understand what your problem is exactly.

            In any case... you should probably use the Hibernate Search DSL, and the range predicate.

            Source https://stackoverflow.com/questions/71222723


            Types cannot be provided in put mapping requests, unless the include_type_name parameter is set to true [JAVA]
            Asked 2022-Feb-15 at 11:33

            We have a java application (spring boot + hibernate search + elastic search). Application is working fine on elastic search version 6.8

            Recently, we have created a new cluster in aws with version 7.10.2 and updated elastic search endpoint in my java application.

            After updating the elastic search endpoint I am getting error Can't update put mapping Types cannot be provided in put mapping requests, unless the include_type_name parameter is set to true and due to this unable to start the server.

            I am not sure where to set include_type_name=true because all the indexes gets created automatically with @Indexed.

            Can someone please let us know how can we fix this issue ?

            Thanks @yrodiere for your response.

            I tried to upgrade below dependencies version but unfortunately not able to fix it.

            Previous Version:



            Answered 2022-Feb-14 at 15:25

            You're probably using Hibernate Search 5.x. In Hibernate Search 5.x, the Elasticsearch integration was experimental and only compatible with Elasticsearch up to version 5.6.

            The fact that your application was working fine with Elasticsearch 6.8 was pure luck: Hibernate Search 5.x was never intended to work with Elasticsearch 6+.

            To upgrade to a more recent version of Elasticsearch, you must upgrade to Hibernate Search 6.0 (or later). The API is different, but there is a very detailed migration guide, and at least you will get production-ready (non-experimental) Elasticsearch integration (plus tons of improvements).

            Note that Hibernate Search 6.x also requires upgrading to Hibernate ORM 5.4; see this compatibility matrix.

            Source https://stackoverflow.com/questions/71113997


            org.hibernate.search.SearchException: Unable to create index directory: /data/index
            Asked 2021-Dec-06 at 12:20

            I am having a problem starting my project. The project compiles though however when starting the server I get this error here:



            Answered 2021-Dec-06 at 12:20

            My guess would be that the user running your application isn't allowed to create directory /data/index. You should probably create it before starting your application, and make sure it's accessible to the user running your application.

            Source https://stackoverflow.com/questions/70245197


            How to match numeric and boolean values in a lucene query
            Asked 2021-Nov-15 at 19:47

            I am using hibernate search to construct a lucene query that returns string values that contain (part of) the search string. Next to that the query must only return the string values if the language id matches as well and if the deleted flag isn't set to true. I've made the below code for this. But the problem is that it doesn't return anything.



            Answered 2021-Nov-15 at 07:57

            Booleans are still indexed as strings in Hibernate Search 5. See org.hibernate.search.bridge.builtin.BooleanBridge. So boolean fields are not part of the problem here.

            If you really want to create numeric queries yourself, in Hibernate Search 5 you will have to use numeric range queries, e.g.:

            Source https://stackoverflow.com/questions/69948399


            NoSuchMethodError when using HibernateSearch 6.0.6 with ElasticSearch 5.6
            Asked 2021-Aug-09 at 08:49

            I am trying to add HibernateSearch 6.0.6.Final to a project currently using ElasticSearch 5.6, using https://docs.jboss.org/hibernate/stable/search/reference/en-US/html_single/ as a guide.

            Since the whole process of replacing/removing the direct calls to the ElasticSearch API from our code seems a little intimidating, I wanted to proceed iteratively, step by step.

            First, I just added the dependencies for HibernateSearch 6.0.6.Final to our Maven pom.xml file, but left the ElasticSearch 5.6. dependencies in there (because of the tons of Java code still calling ElasticSearch 5.6. classes and methods directly), so the pom looks something like this:



            Answered 2021-Aug-09 at 08:49

            As explained here, the compatibility matrix gives you the compatibility of Hibernate Search with Elasticsearch server.

            Elastic seems completely fine with introducing breaking changes in their client JARs; sometimes even in minor versions. As a result, any library that depends on these JARs (e.g. Hibernate Search) needs to target one and only one version of these JARs. Hibernate Search cannot be made compatible with multiple client JARs whose method definitions are different; at least not without a significant maintenance burden that I'm not ready to accept.

            Long story short: don't try to override the version of the client JAR used by Hibernate Search; that can't end well. It would be like savagely downgrading your application to JPA 1.0 JARs; it's unlikely to work.

            That being said, the new low-level REST client JARs are compatible with older Elasticsearch server versions. So you can use Elasticsearch low-level REST Client 7.10 with Elasticsearch server 5.6.

            So you can migrate this way:

            1. Upgrade the client in your application to version 7.10 (while staying on Elasticsearch server 5.6).
            2. Add Hibernate Search 6.0 to your application.
            3. Some time later, upgrade to Elasticsearch server 7.10. Preferably soon, because Elasticsearch 5.6 has reached end-of-life a long time ago.

            If you're using the high-level client JARs, though... it's only compatible with the same version of the Elasticsearch server, so you will have to migrate to Elasticsearch server 7.10 before you can migrate to Hibernate Search.

            Source https://stackoverflow.com/questions/68708771


            Impossible to configure my own analyzer in spring boot Hibernate Search Elasticsearch
            Asked 2021-Jun-22 at 06:46

            Please help. It's many days i try to configure an elasticsearch indexation in my Spring Boot application, certainly i missed something in the documentation but i dont find what.

            I am relatively new with spring, days from days i found it very powerful, and it is my first very long problem.

            Description of the problem I have a simple object Book indexed with a @FullTextField on my own analyzer



            Answered 2021-Jun-22 at 06:46

            application.properties is a Spring Boot configuration file, not a Hibernate Search configuration file. You cannot just dump Hibernate Search properties in there.

            Instead, prefix your Hibernate Search properties with spring.jpa.properties., so that Spring Boot passes along the properties to Hibernate ORM, which will pass them along to Hibernate Search. For example:

            Source https://stackoverflow.com/questions/68066491


            Hibernate envers + hibernate-search : Reading audit information over Lucene/Elasticsearhc indexes
            Asked 2021-Jun-09 at 13:46

            I'm using hibernate-envers for audit purposes in an application. I'm also using hibernate-search in order to search/read the information of JPA entities in the application.

            I was wondering if there's any kind of configuration/integration that can make hibernate-envers work with the audit enties/tables, over indexes too, in order to read with hibernate -search that information from the indexes.

            I would like to avoid doing it "manually", for example, using envers event listeners in order to create/manipulate a new index manually for the audited entity, using a new JPA Entity modelling the Audit entity information including @Indexed annotation, fields etc.).

            Ideally was wondering if there's support for envers/search integration out of the box, without custom development, to achieve storing all audit information in new _aud indexes.

            Thanks in advance, any piece of advice is appreciated.



            Answered 2021-Jun-09 at 13:46

            It's certainly not possible out of the box.

            If it ever becomes possible, you won't benefit from all the Envers features such as "get me this entity at this revision". You will simply index all the revisions of each entity, and you will only be able to query (and retrieve) these revisions. That would be queries such as "get all revisions of the entity with id 1 where name contained "some text".

            Also, this will not remove the need for audit tables. The indexes will exist in addition to the audit tables.

            That being said, I just gave it a try and we could make it possible in Hibernate Search 6 with just a few changes. If you're still interested, you can have a look there: https://hibernate.atlassian.net/browse/HSEARCH-4238

            Source https://stackoverflow.com/questions/67901520


            Kotlin 1.5.10, Gradle 7.0.2_2 - Could not find method testCompile() group=org.junit.jupiter, name=junit-jupiter-api, version=5.7.2
            Asked 2021-May-27 at 17:51

            After following: https://youtrack.jetbrains.com/issue/KT-46090

            I'm still issues with:

            Configure project : POM relocation to an other version number is not fully supported in Gradle : xml-apis:xml-apis:2.0.2 relocated to xml-apis:xml-apis:1.0.b2. Please update your dependency to directly use the correct version 'xml-apis:xml-apis:1.0.b2'. Resolution will only pick dependencies of the relocated element. Artifacts and other metadata will be ignored.

            FAILURE: Build failed with an exception.

            • Where: Build file '/Users/NOTiFY/IdeaProjects/GoStopHandle/build.gradle' line: 53

            • What went wrong: A problem occurred evaluating root project 'GoStopHandle'.

            Could not find method testCompile() for arguments [{group=org.junit.jupiter, name=junit-jupiter-api, version=5.7.1}] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.




            Answered 2021-May-27 at 17:51

            May 19, 2021 upgrade JUnit with 5.7.2_1 still get:

            Source https://stackoverflow.com/questions/67545818


            How to fix Hibernate Search createClient error?
            Asked 2021-Apr-28 at 06:21

            I'm making online shop with Spring and I decided to add text-search there. I tried Hibernate Search using this guide https://reflectoring.io/hibernate-search/ and got an error while starting the app.

            Here's what I have (error) + my code below:


            An attempt was made to call a method that does not exist. The attempt was made from the following location:



            Answered 2021-Apr-28 at 06:21

            You are using Hibernate Search 5, which is old, with a recent version of Spring.

            Hibernate Search 5, being old, depends on an old version of the Elasticsearch client JARs.

            Your version of Spring depends on a newer, incompatible version of the Elasticsearch client JARs.

            Two solutions:

            1. Upgrade to the newer Hibernate Search 6, which will most likely depend on a version of Elasticsearch that is compatible with the one bundled with Spring. Note that just changing the version won't be enough: group IDs, artifact IDs and APIs are different. See the migration guide.

            2. OR try to downgrade to an older version of the Elasticsearch client. For example, with Spring Boot:

            Source https://stackoverflow.com/questions/67287169


            Hibernate search quarkus compatibility questions
            Asked 2021-Apr-06 at 14:22

            Im working in a quarkus project, I have to connect to an elasticsearch clusert and in production exists a mysql database with data. Im thinking about using Hibernate Search but I have some questions.

            1-Which version of hibernate search use quarkus? In the pom is not specified. Is 6?



            Answered 2021-Apr-06 at 14:22
            1. It's Hibernate Search 6 - in Quarkus 1.13, 6.0.2.Final
            2. Yes, it should be. Our main testing is now against the latest Open Source version of Elasticsearch but we are still testing 7.11.
            3. Hibernate Search handles reads/writes and also hydrate your search data from the database so you should have the MySQL database around. If you are only doing read-only stuff AND only using projections, maybe not having the database around is possible but I don't think it's a supported use case
            4. Yes.
            5. You will have to implement it yourself, there's nothing built-in.

            Source https://stackoverflow.com/questions/66970312

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install hibernate-search

            A getting started guide is available in the reference documentation.
            Available versions and compatibility matrix
            Reference documentation for all versions (current and past)


            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone hibernate/hibernate-search

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Consider Popular Object-Relational Mapping Libraries

            Try Top Libraries by hibernate


            by hibernateJava


            by hibernateJava


            by hibernateJava


            by hibernateJava


            by hibernateJava