[hibernate-issues] [JIRA] (HSEARCH-4720) Throw exceptions instead of logging warnings for failures to configure association inverse path resolution

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiZDZlODUy... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4720?atlOrigin=eyJpIjoiZDZ... ) HSEARCH-4720 ( https://hibernate.atlassian.net/browse/HSEARCH-4720?atlOrigin=eyJpIjoiZDZ... ) Throw exceptions instead of logging warnings for failures to configure association inverse path resolution ( https://hibernate.atlassian.net/browse/HSEARCH-4720?atlOrigin=eyJpIjoiZDZ... ) Issue Type: Improvement Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: mapper-orm, mapper-pojo-base Created: 13/Oct/2022 09:40 AM Fix Versions: 7.0-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) For my work on https://hibernate.atlassian.net/browse/HSEARCH-4708 ( https://hibernate.atlassian.net/browse/HSEARCH-4708 ) , I’ve been extra careful not to fail, and as a result I decided to log warnings whenever anything goes wrong on the features I added to fix that bug. Whenever we can (and if we can), we should break backwards compatibility and simply throw exceptions instead of logging warnings. See occurrences of this ticket’s key in the source code. ( https://hibernate.atlassian.net/browse/HSEARCH-4720#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4720#add-comment?atlOrigin... ) 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.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100208- sha1:492d0ce )