March 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-3851) Entities whose indexing failed are not reported when even just one document ID cannot be converted

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiNmFmYjE0... ) / Bug ( https://hibernate.atlassian.net/browse/HSEARCH-3851?atlOrigin=eyJpIjoiNmF... ) HSEARCH-3851 ( https://hibernate.atlassian.net/browse/HSEARCH-3851?atlOrigin=eyJpIjoiNmF... ) Entities whose indexing failed are not reported when even just one document ID cannot be converted ( https://hibernate.atlassian.net/browse/HSEARCH-3851?atlOrigin=eyJpIjoiNmF... ) Issue Type: Bug Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: mapper-orm, mapper-pojo Created: 03/Mar/2020 07:56 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%... ) See https://discourse.hibernate.org/t/indexation-post-treatment/3753/12?u=yro... The problem is that, when the indexing of multiple entities failed, we give up on reporting *all* failing entities when even just *one* document ID cannot be converted back to an entity ID, but all other document IDs can. Ideally we'd just log the failure to convert the document ID somewhere, and still report the other entity IDs. ( https://hibernate.atlassian.net/browse/HSEARCH-3851#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3851#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#100121- sha1:a532aba )

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3849) Create-or-validate schema management by default

by Yoann Rodière (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3759) Initialization options and APIs

by Yoann Rodière (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3850) Expose a tool to build property keys

by Alexis CUCUMEL (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3850) Expose a tool to build property keys

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiY2MxZmE2... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-3850?atlOrigin=eyJpIjoiY2M... ) HSEARCH-3850 ( https://hibernate.atlassian.net/browse/HSEARCH-3850?atlOrigin=eyJpIjoiY2M... ) Expose a tool to build property keys ( https://hibernate.atlassian.net/browse/HSEARCH-3850?atlOrigin=eyJpIjoiY2M... ) Issue Type: Improvement Assignee: Unassigned Components: engine Created: 03/Mar/2020 03:59 AM Fix Versions: 6.0.0-Bonus-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Property keys for backends and indexes are a bit awkward to use right now, because they require concatenating strings: the "hibernate.search." prefix, the backend name, the radical. It would be nice to expose a tool to build property keys more easily. For example: // hibernate.search.backends.myBackendName.version BackendSettings.backendKey( "myBackendName" , ElasticsearchBackendSettings.VERSION ) // hibernate.search.backends.myBackendName.index_defaults.lifecycle.strategy IndexSettings.indexDefaultsKey( "myBackendName" , ElasticsearchIndexSettings.LIFECYCLE_STRATEGY ) // hibernate.search.backends.myBackendName.indexes.myIndexName.lifecycle.strategy IndexSettings.indexKey( "myBackendName" , "myIndexName" , ElasticsearchIndexSettings.LIFECYCLE_STRATEGY ) ( https://hibernate.atlassian.net/browse/HSEARCH-3850#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3850#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#100121- sha1:a532aba )

4 years, 3 months

1
0
0 / 0

[JIRA] (HHH-13886) columnDefinition broken for audit mappings

by JiraAccount (JIRA)

JiraAccount ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5e25e... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzE1OTBmZTdm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-13886?atlOrigin=eyJpIjoiMzE1OT... ) HHH-13886 ( https://hibernate.atlassian.net/browse/HHH-13886?atlOrigin=eyJpIjoiMzE1OT... ) columnDefinition broken for audit mappings ( https://hibernate.atlassian.net/browse/HHH-13886?atlOrigin=eyJpIjoiMzE1OT... ) Issue Type: Bug Affects Versions: 5.4.11, 5.4.12 Assignee: Chris Cranford ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-envers Created: 03/Mar/2020 01:51 AM Priority: Major Reporter: JiraAccount ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5e25e... ) HHH-10844 ( https://hibernate.atlassian.net/browse/HHH-10844 ) Closed should be fixed with version 5.4.11, but now a column definition like @Column(name = "text", columnDefinition = "mediumtext") private String text; or @Column(name = "foo", columnDefinition = "char(40)") private String foo; no longer works with envers. It will result in the following log messages > Column [text] uses a column-definition of [mediumtext] , resolved sql-type as [varchar(255)]. > Column [foo] uses a column-definition of [char(40)] , resolved sql-type as [varchar(255)]. and exceptions like this: > Schema-validation: wrong column type encountered in column [foo] in table [bar] ; found char (Types#CHAR) ( #CHAR) ) , but expecting varchar(255) (Types#VARCHAR) ( #VARCHAR) ) I think this behaviour was added by this commit: https://github.com/hibernate/hibernate-orm/commit/38f01311602f115ccec23f9... ( https://hibernate.atlassian.net/browse/HHH-13886#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13886#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#100121- sha1:a532aba )

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3849) Create-or-validate schema management by default

by Yoann Rodière (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3849) Create-or-validate schema management by default

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMzJlMmQx... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-3849?atlOrigin=eyJpIjoiMzJ... ) HSEARCH-3849 ( https://hibernate.atlassian.net/browse/HSEARCH-3849?atlOrigin=eyJpIjoiMzJ... ) Create-or-validate schema management by default ( https://hibernate.atlassian.net/browse/HSEARCH-3849?atlOrigin=eyJpIjoiMzJ... ) Issue Type: Improvement Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Created: 03/Mar/2020 00:57 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%... ) The current default strategy, create , won't do anything if indexes exist. This has resulted in a lot of confusion in the past from users who didn't think about upgrading their Elasticsearch schema when they change their Hibernate Search mapping. Let's introduce a create-or-validate strategy and make it the default, so that users are reminded when something is missing. ( https://hibernate.atlassian.net/browse/HSEARCH-3849#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3849#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#100121- sha1:a532aba )

4 years, 3 months

1
0
0 / 0

[JIRA] (WEBSITE-575) Broken link: http://hibernate.org/xsd/orm/hbm

by Yoann Rodière (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (WEBSITE-405) log file

by Yoann Rodière (JIRA)

4 years, 3 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 March 2020