[hibernate-issues] [JIRA] (HSEARCH-3841) Offline startup

Yoann Rodière (JIRA) jira at hibernate.atlassian.net
Tue Feb 25 06:13:29 EST 2020


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=eyJpIjoiZjBhOTc3ZTdlMzYwNDJhZmJjZjJjMDFhZDEwMjllYTAiLCJwIjoiaiJ9 ) / New Feature ( https://hibernate.atlassian.net/browse/HSEARCH-3841?atlOrigin=eyJpIjoiZjBhOTc3ZTdlMzYwNDJhZmJjZjJjMDFhZDEwMjllYTAiLCJwIjoiaiJ9 ) HSEARCH-3841 ( https://hibernate.atlassian.net/browse/HSEARCH-3841?atlOrigin=eyJpIjoiZjBhOTc3ZTdlMzYwNDJhZmJjZjJjMDFhZDEwMjllYTAiLCJwIjoiaiJ9 ) Offline startup ( https://hibernate.atlassian.net/browse/HSEARCH-3841?atlOrigin=eyJpIjoiZjBhOTc3ZTdlMzYwNDJhZmJjZjJjMDFhZDEwMjllYTAiLCJwIjoiaiJ9 )

Issue Type: New Feature Assignee: Unassigned Components: backend-elasticsearch Created: 25/Feb/2020 03:13 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, even when the index lifecycle strategy is set to NONE, the Elasticsearch backend will send a request to the cluster on startup in order to check the version of the cluster.
This has two purposes:

* Check that the version of the cluster matches the version configured by the user (if any)
* Gather more precise information about the Elasticsearch version so as to pick the appropriate protocol dialect.

In some cases, it's desirable that no request is sent to the Elasticsearch cluster on startup. We should try to get rid of this version check:

* Maybe add a configuration option to disable it explicitly? This would require that the version provided by the user is precise enough to determine the protocol dialect.
* Maybe remove the check completely when a version is specified, and is precise enough to determine the protocol dialect? That would lead to complex, potentially surprising behavior, though...
* Something else?

See https://discourse.hibernate.org/t/manual-indexing-without-listeners/3790/3

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

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#100121- sha1:a269fed )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20200225/4486333e/attachment-0001.html 


More information about the hibernate-issues mailing list