[hibernate-issues] [JIRA] (HSEARCH-3950) Simpler configuration syntax for single-backend applications

[Yoann Rodière (JIRA)]

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A58fa1ced-171a-4c00-97e8-5d70d442cc4b ) *created* an issue

Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMjI3ZWIxMjFhOTE5NDdmYmJhOWYwMWQ0NTE3ZjQ5ZDgiLCJwIjoiaiJ9 ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-3950?atlOrigin=eyJpIjoiMjI3ZWIxMjFhOTE5NDdmYmJhOWYwMWQ0NTE3ZjQ5ZDgiLCJwIjoiaiJ9 ) HSEARCH-3950 ( https://hibernate.atlassian.net/browse/HSEARCH-3950?atlOrigin=eyJpIjoiMjI3ZWIxMjFhOTE5NDdmYmJhOWYwMWQ0NTE3ZjQ5ZDgiLCJwIjoiaiJ9 ) Simpler configuration syntax for single-backend applications ( https://hibernate.atlassian.net/browse/HSEARCH-3950?atlOrigin=eyJpIjoiMjI3ZWIxMjFhOTE5NDdmYmJhOWYwMWQ0NTE3ZjQ5ZDgiLCJwIjoiaiJ9 )

Issue Type: Improvement Assignee: Unassigned Components: engine Created: 17/Jun/2020 01:02 AM Fix Versions: 6.0.0.Beta-backlog-high-priority Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A58fa1ced-171a-4c00-97e8-5d70d442cc4b )

Currently, a single-backend application will need to do this:

hibernate.search.default_backend = myBackend
hibernate.search.backends.myBackend.foo = ...
hibernate.search.backends.myBackend.bar = ...
hibernate.search.backends.myBackend.foobar = ...

We could simplify it to this:

hibernate.search.backend.foo = ...
hibernate.search.backend.bar = ...
hibernate.search.backend.foobar = ...

This would be consistent with how datasources ( https://quarkus.io/guides/datasource ) are configured in Quarkus, but unfortunately not with how Hibernate Search backends ( https://quarkus.io/guides/hibernate-search-elasticsearch ) are configured in Quarkus.

A few details:

* We would have to give a name to this default backend. default , maybe? In that case we should forbid the use of that name for named backends.
* Existing applications relying on default_backend should continue to work, but maybe we should deprecate this configuration property. People who really need
* We should still allow the definition of named backends, but they will only be used when explicitly referenced.
* We should use the default backend wherever possible in tests and documentation, and add separate tests and documention for named backends.
* In examples for setting configuration properties, we should *only* include an example for the default backend. We'll just mention in the section about named backends how the prefix changes for those.

( https://hibernate.atlassian.net/browse/HSEARCH-3950#add-comment?atlOrigin=eyJpIjoiMjI3ZWIxMjFhOTE5NDdmYmJhOWYwMWQ0NTE3ZjQ5ZDgiLCJwIjoiaiJ9 ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3950#add-comment?atlOrigin=eyJpIjoiMjI3ZWIxMjFhOTE5NDdmYmJhOWYwMWQ0NTE3ZjQ5ZDgiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100129- sha1:dd5aa75 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20200617/63bd1c97/attachment.html