June 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-4866) Deprecate hibernate.search.automatic_indexing.enable_dirty_checks for removal

by Yoann Rodière (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4865) Upgrade build dependencies to the latest version in Search 6.2.0.CR1

by Yoann Rodière (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4845) Have a dedicated docvalue field for the root document id in the Lucene backend's document

by Yoann Rodière (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16747) interpretation of queries with no 'select', multiple elements in 'from', and no explicit result class

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16747 ( https://hibernate.atlassian.net/browse/HHH-16747?atlOrigin=eyJpIjoiYjRlZm... ) Re: interpretation of queries with no 'select', multiple elements in 'from', and no explicit result class ( https://hibernate.atlassian.net/browse/HHH-16747?atlOrigin=eyJpIjoiYjRlZm... ) Honestly, going forward, I think we should just deprecate the use of implicit select for queries with more than one identification variable, and then eventually start rejecting some of these ambiguous cases. It was only backward compatibility concerns which motivated me to want to keep allowing it in 6, and so if there are cases where we break compatibility, I would prefer to just reject those cases altogether. ( https://hibernate.atlassian.net/browse/HHH-16747#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16747#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#100225- sha1:4a1ccf9 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16286) NullPointerException: Cannot invoke "EntityInitializer.getNavigablePath()" because "firstEntityInitializer" is null

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16286 ( https://hibernate.atlassian.net/browse/HHH-16286?atlOrigin=eyJpIjoiNmZkYz... ) Re: NullPointerException: Cannot invoke "EntityInitializer.getNavigablePath()" because "firstEntityInitializer" is null ( https://hibernate.atlassian.net/browse/HHH-16286?atlOrigin=eyJpIjoiNmZkYz... ) Markus Heiden ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6149cfc... ) Alright… I guess there’s still hope that your problem and the reproducer in https://hibernate.atlassian.net/browse/HHH-16740 rely on common internals and that the bug is there. We’ll see when that other issue is fixed, maybe you’ll be able to test Hibernate ORM with that fix and we’ll have a pleasant surprise. ( https://hibernate.atlassian.net/browse/HHH-16286#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16286#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#100225- sha1:4a1ccf9 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4864) Add fuzzy query in Hibernate Search 6

by Yoann Rodière (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4864) Add fuzzy query in Hibernate Search 6

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4864 ( https://hibernate.atlassian.net/browse/HSEARCH-4864?atlOrigin=eyJpIjoiZDZ... ) Re: Add fuzzy query in Hibernate Search 6 ( https://hibernate.atlassian.net/browse/HSEARCH-4864?atlOrigin=eyJpIjoiZDZ... ) Thanks for opening this. > > > > because Elasticsearch do not allow for match query with fuzziness with > Ngram token > > That seems suspicious as I wouldn’t expect the origin of tokens to matter. But as I’m not familiar with the problem, I can’t really tell for sure. Regardless, I’m not sure it will be as useful as you seem to think. From what I can see the fuzzy predicate in Elasticsearch ( https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl... ) only accepts one term, and I don’t think it performs analysis. In general I would say fuzziness in the match / simpleQueryString predicates is more useful, but then I don’t know about your exact use case, so maybe in your specific case it isn’t? 🤷‍♂️ > > > > Will there be support for fuzzy query in the future? > > There already is if you’re willing to resort to native features ( https://docs.jboss.org/hibernate/stable/search/reference/en-US/html_singl... ) , i.e. to write your fuzzy predicate as JSON: String fieldName = "title_ngram"; String term = "robot"; JsonObject fuzzyPredicate = new JsonObject(); JsonObject fieldJson = new JsonObject(); fuzzyPredicate.add("fuzzy", fieldJson); JsonObject innerJson = new JsonObject(); fieldJson.add(fieldName, fieldJson); innerJson.addProperty("value", term); innerJson.addProperty("fuzziness", 1); List<Book> hits = searchSession.search( Book.class ) .extension( ElasticsearchExtension.get() ) .where( f -> f.fromJson( fuzzyPredicate ) ) .fetchHits( 20 ); Otherwise, someone can always consider contributing the feature themself. You can look at the following PRs that added support for other predicates to get hints as to where to add code, how to test it, etc.: * https://github.com/hibernate/hibernate-search/pull/2532/files * https://github.com/hibernate/hibernate-search/pull/2486/files ( https://hibernate.atlassian.net/browse/HSEARCH-4864#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4864#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#100225- sha1:4a1ccf9 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16749) FunctionTypeResolver does not have access to CustomType

by Jan-Willem Gmelig Meyling (JIRA)

Jan-Willem Gmelig Meyling ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYWQyY2NjZGYx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16749?atlOrigin=eyJpIjoiYWQyY2... ) HHH-16749 ( https://hibernate.atlassian.net/browse/HHH-16749?atlOrigin=eyJpIjoiYWQyY2... ) FunctionTypeResolver does not have access to CustomType ( https://hibernate.atlassian.net/browse/HHH-16749?atlOrigin=eyJpIjoiYWQyY2... ) Issue Type: Bug Assignee: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Created: 05/Jun/2023 04:35 AM Priority: Major Reporter: Jan-Willem Gmelig Meyling ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I'm struggeling to get the CustomType instance from a DynamicParameterizedType through an argument expression in a FunctionTypeResolver. The CustomType is replaced by the AttributeFactory by context.resolveBasicType( typeContext.getJpaBindableType). This is problematic for CustomTypes and in particular DynamicParamererizedTypes. Instead of the (parameterized) custom type instance, you get the basic type from the registry, which defaults to BasicTypeImpl(SerializableJavaType) which has lost all the custom type / parameterized data. In final DomainType<Y> metaModelType = determineSimpleType( singularAttributeMetadata.getValueContext(), metadataContext ); Why is: final DomainType<Y> metaModelType = singularAttributeMetadata.getPropertyMapping().getType() instanceof DomainType ? (DomainType<Y>) singularAttributeMetadata.getPropertyMapping().getType() : determineSimpleType( singularAttributeMetadata.getValueContext(), metadataContext ); Not considered? CustomType<X> implements DomainType<X>}}through {{ConvertedBasicType<X> , however currently the metamodel instead represents the attribute as a BasicTypeImpl(SerializableJavaType) Use case : custom functions that operate on custom types that get its typing from a generic bound. For example: LOWER(<range>) which operates on a Range<LocalDateTime> should return the basic type of LocalDateTime. In Hibernate 5 it was possible to extract the generic bound from the custom type, but in 6.x this custom type is shadowed by a basic type for the raw class. ( https://hibernate.atlassian.net/browse/HHH-16749#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16749#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#100225- sha1:4a1ccf9 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HBX-2531) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_6_2 to version 6.2.4.Final

by Koen Aers (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HBX-2530) Update version identifier to 6.2.5-SNAPSHOT

by Koen Aers (JIRA)

2 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2023