April 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-12104) @Where clause is ignored when eagerly loading ManyToOne association

by Damian Nardelli (JIRA)

Damian Nardelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d43070... ) *commented* on HHH-12104 ( https://hibernate.atlassian.net/browse/HHH-12104?atlOrigin=eyJpIjoiNWY1ZG... ) Re: @Where clause is ignored when eagerly loading ManyToOne association ( https://hibernate.atlassian.net/browse/HHH-12104?atlOrigin=eyJpIjoiNWY1ZG... ) FYI - I ran into this issue also for @ManyToMany . I filed a bug in https://hibernate.atlassian.net/browse/HHH-13530 but no one answered me. I ran into the same issue again this week… ( https://hibernate.atlassian.net/browse/HHH-12104#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-12104#add-comment?atlOrigin=ey... ) 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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:84eb093 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3900) drop-and-create strategy is not working at app. startup when "hibernate.search.autoregister_listeners" is set to false. And if true, startup index creation thread are not released, sending the app in out of memory.

by Ronak S (JIRA)

Ronak S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ea56c8... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiZTI0YTg5... ) / Bug ( https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiZTI... ) HSEARCH-3900 ( https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiZTI... ) drop-and-create strategy is not working at app. startup when "hibernate.search.autoregister_listeners" is set to false. And if true, startup index creation thread are not released, sending the app in out of memory. ( https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiZTI... ) Change By: Ronak S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ea56c8... ) Summary: drop-and-create strategy is not working at app. startup when "hibernate.search.autoregister_listeners" is set to false. And if true, startup index creation thread are not released , sending the app in out of memory. ( https://hibernate.atlassian.net/browse/HSEARCH-3900#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3900#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:84eb093 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3900) drop-and-create strategy is not working at app. startup when "hibernate.search.autoregister_listeners" is set to false. And if true, startup index creation thread are not released.

by Ronak S (JIRA)

Ronak S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ea56c8... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiNGEyNTI0... ) / Bug ( https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiNGE... ) HSEARCH-3900 ( https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiNGE... ) drop-and-create strategy is not working at app. startup when "hibernate.search.autoregister_listeners" is set to false. And if true, startup index creation thread are not released. ( https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiNGE... ) Issue Type: Bug Affects Versions: 5.11.5.Final Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: backend-lucene Created: 26/Apr/2020 04:35 AM Environment: Hibernate 5.4.12, Hibernate search 5.11.5 Labels: hibernate performance Priority: Critical Reporter: Ronak S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ea56c8... ) We have upgraded our system hibernate to 5.4.12 and hibernate search ORM to 5.11.5 with app server Websphere 8.5.5.16. We are using Elastic Search 5.6.10. *Issue:* On initial startup we saw lots of threads been created for refreshing the indexes on elastic side. But we do not want this to happen, we searched and found out the property to stop this and that was "hibernate.search.autoregister_listeners". Setting this property to false, stopped creation of all these index refreshing threads. But now we had other issue. Now we were unable to perform the dropping and creation of indexes at server startup. By using "hibernate.search.default.elasticsearch.index_schema_management_strategy" as drop-and-create. Due to the setting of "hibernate.search.autoregister_listeners" to false, this does not works anymore. So the question arises, why in the first place we introduced this property("hibernate.search.autoregister_listeners"), answer to that we got on the official documentation side and that reads: "The good news is that Hibernate Search is enabled out of the box when detected on the classpath by Hibernate ORM. If for some reason you need to disable it set hibernate.search.autoregister_listeners to false. Note that there is no performance penalty when the listeners are enabled but no entities are annotated as indexed." But what if we have the entities as @Indexed, this fails. If we have hibernate.search.autoregister_listeners settings as false then while executing fullTextEntityManager.createIndexer().startAndWait() am receiving org.hibernate.search.exception.SearchException: HSEARCH000222: The SearchFactory was not initialized. Why do I suspect the whole meaning of hibernate search ORM usage under a hibernate project is lost with this new version. If hibernate.search.autoregister_listeners is false I can not use the hibernate search at all and if its true than I've the performance issue at startup. We strongly feel this to be a bug in new version as this functionality of drop-and-create and the mass indexer was working as expected under the older versions without this new property. Though we are sure Hibernate community must have provided this with a thought. But again this is not working as expected keeping the other functionalities of hibernate search in mind. *hibernate.cfg.xml* <property name= "hibernate.search.autoregister_listeners" > true </property> <property name= "hibernate.search. default.indexmanager" >elasticsearch</property> <property name= "hibernate.search. default.elasticsearch.host" >http: //ip:9400</property> <property name= "hibernate.search. default.elasticsearch.index_schema_management_strategy" >drop-and-create</property> <property name= "hibernate.search. default.elasticsearch.required_index_status" >yellow</property> <property name= "hibernate.search. default.indexwriter.infostream" > true </property> Please look into this and share your thoughts. ( https://hibernate.atlassian.net/browse/HSEARCH-3900#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3900#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:84eb093 )

4 years, 4 months

1
0
0 / 0

[JIRA] (OGM-1573) Update Neo4j to version 3.4.11

by Markus Gritsch (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (OGM-1573) Update Neo4j to version 3.4.11

by Markus Gritsch (JIRA)

Markus Gritsch ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e9eef3... ) *created* an issue Hibernate OGM ( https://hibernate.atlassian.net/browse/OGM?atlOrigin=eyJpIjoiYTk2NzVkOTQ3... ) / Task ( https://hibernate.atlassian.net/browse/OGM-1573?atlOrigin=eyJpIjoiYTk2NzV... ) OGM-1573 ( https://hibernate.atlassian.net/browse/OGM-1573?atlOrigin=eyJpIjoiYTk2NzV... ) Update Neo4j to version 3.4.11 ( https://hibernate.atlassian.net/browse/OGM-1573?atlOrigin=eyJpIjoiYTk2NzV... ) Issue Type: Task Affects Versions: 5.4.2.Final Assignee: Markus Gritsch ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e9eef3... ) Components: neo4j, tests Created: 25/Apr/2020 12:54 PM Priority: Minor Reporter: Markus Gritsch ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e9eef3... ) With upgrading the neo4j dependency version from 3.4. *10* to 3.4. *11* , *four* unit-tests are failing. * DuplicateIdDetectionTest * JtaRollbackTest * ResourceLocalRollbackTest * CompensationSpiTest Comparing the neo4j git tags to see what has changed among those version numbers, it seems a change was introduced, how building the "cause chain" for the exception query-execution. The git diff of neo4j version 3.4.10 - 3.4.11 is https://github.com/neo4j/neo4j/compare/3.4.10...3.4.11 The isolated commits which had changed the behavior * https://github.com/neo4j/neo4j/commit/25bd77e8524bcd60ae8418f96da46d840e1... * https://github.com/neo4j/neo4j/commit/aa0ab5548b8279949b7881505208484e81f... * https://github.com/neo4j/neo4j/commit/a14accb8ef658250de2d7b8cb055cf660b1... To enable compatibility with neo4j 3.4.11 the class *EmbeddedNeo4jDialect* has to be modified. *The exception has to get changed from "UniquePropertyValueValidation" to "IndexEntryConflict."* ( https://hibernate.atlassian.net/browse/OGM-1573#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/OGM-1573#add-comment?atlOrigin=eyJ... ) 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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:84eb093 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-13981) Upgrade to Jandex 2.1.3.Final

by Sanne Grinovero (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-13981) Upgrade to Jandex 2.1.3.Final

by Sanne Grinovero (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-1050) HQL Unions

by Steve Ebersole (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-10992) Extend support for integrator-contributed domain and relational objects

by Steve Ebersole (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-3949) Intrumentated to one relations can not be join fetched

by Steve Ebersole (JIRA)

4 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2020