Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

'hibernate.search.backend.uris' recognized as an invalid property

Description

Hello,

Looks like “hibernate.search.backend.uris” property is not recognized as a valid one anymore (since 6.1) though it seems that it still takes effect when used:

“HSEARCH000568: Invalid configuration passed to Hibernate Search: some properties in the given configuration are not used. There might be misspelled property keys in your configuration. Unused properties: [hibernate.search.backend.uris]. To disable this warning, set the property 'hibernate.search.configuration_property_checking.strategy' to 'ignore'.”

Also, the documentation still mentions that property.

Is the usage of “hibernate.search.backend.uris” property discouraged going forward?

Thanks!

Activity

Show:

Yoann Rodière October 23, 2023 at 12:15 PM

Closing due to lack of reproducer.
If you manage to reproduce this, feel free to comment on this issue or open a new issue.

Yoann Rodière September 25, 2023 at 3:58 PM

Hey , any news on this?

Ivan Kotev September 29, 2022 at 9:39 AM

Hey Yoann,

Sorry I wasn’t able to work on a reproducer though I have a theory why this warning might show up. In my project we connect to 2 different databases (hence multiple entity managers) and for only one of them we have enabled Hibernate Search.

I’ll try to confirm if this really is the case.

Yoann Rodière September 29, 2022 at 9:30 AM

Hey , did you manage to write a reproducer in the end?

Ivan Kotev January 19, 2022 at 2:55 PM

Thanks for taking a look, Yoann.

Indeed, I am not able to reproduce it in the hibernate-test-case-templates project.

Wondering if it has something to do with Spring Boot (which my project is based on) and which passes the properties down to Hibernate ORM using the spring.jpa.properties prefix. I’ll try to make such a test case.

Cannot Reproduce

Details

Assignee

Reporter

Components

Affects versions

Priority

Created January 19, 2022 at 11:48 AM
Updated October 23, 2023 at 12:15 PM
Resolved October 23, 2023 at 12:15 PM