Simpler configuration syntax for single-backend applications

Description

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

We could simplify it to this:

This would be consistent with how datasources are configured in Quarkus, but unfortunately not with how Hibernate Search backends 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 to define the default backend at deployment time can use the programmatic mapping.

  • 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.

Environment

None

Assignee

Yoann Rodière

Reporter

Yoann Rodière

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Components

Fix versions

Priority

Major
Configure