[jboss-jira] [JBoss JIRA] (WFLY-10329) Have JipiJapa enable Hibernate Search backward compatibility properties

Sanne Grinovero (JIRA) issues at jboss.org
Thu May 17 19:09:00 EDT 2018


    [ https://issues.jboss.org/browse/WFLY-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578625#comment-13578625 ] 

Sanne Grinovero commented on WFLY-10329:
----------------------------------------

I believe this was resolved by https://github.com/wildfly/wildfly/pull/11234 as I see the property is set, but I'm not sure if there is a test for it. Should we mark it resolved?

> Have JipiJapa enable Hibernate Search backward compatibility properties
> -----------------------------------------------------------------------
>
>                 Key: WFLY-10329
>                 URL: https://issues.jboss.org/browse/WFLY-10329
>             Project: WildFly
>          Issue Type: Task
>            Reporter: Sanne Grinovero
>            Assignee: Scott Marlow
>
> For Hibernate Search 5.10.x to be fully backwards compatible with the previous versions included in WildFly, we need the following property to be set by default among the Hibernate ORM configuration properties:
> {code}
> hibernate.search.index_uninverting_allowed=true
> {code}
> When set to true and the mapping actually makes use of this feature, a warning will be logged.
> We probably will want to document this as well: recommend users to set it to "false" explicitly, as relying on this feature has a performance penalty, yet no relying on it requires mapping changes.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list