January 2023 - hibernate-issues - Jboss List Archives

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-11936 ( https://hibernate.atlassian.net/browse/HHH-11936?atlOrigin=eyJpIjoiYmEzMj... ) Re: Stabilize "empty composites" feature ( https://hibernate.atlassian.net/browse/HHH-11936?atlOrigin=eyJpIjoiYmEzMj... ) Well maybe. Actually I would say it’s much more likely that it’s a class-level thing because either an instance of the class X with all null properties makes sense or it doesn't. I don't really see a usecase where in some contexts but not others you can have a meaningful all-null X. Whether the fields of X can all be null is fundamentally a characteristic of X itself and what it represents. But of course I’m not against letting this stuff be set at the property level. That’s a sort of flexibility we generally allow for embeddables, and there’s no specific reason to not allow it here. What it can’t possibly be is a global setting. A MonetaryAmount with all null fields is never a meaningful monetary value no matter what “global” characteristics your program has. And indeed it seems to me that the default behavior is always better and more correct for at least the majority of embeddable classes in a program. I mean, TBH, I really struggle to come up with even a single legit usecase for a class with everything null, and nobody so far has ever been able to show me one. For every concrete example I can think of, the default behavior is more correct. Perhaps you have a convincing example that would help me understand the motivation for this? I admit that I sometimes fall short on imagination. Even if you can think of an couple of great motivating cases, I still insist that such cases will always be exceptional cases in every program. ( https://hibernate.atlassian.net/browse/HHH-11936#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-11936#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#100214- sha1:d3cc1a2 )

1 year, 11 months

1
0
0 / 0

[JIRA] (HHH-11936) Stabilize "empty composites" feature

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-11936 ( https://hibernate.atlassian.net/browse/HHH-11936?atlOrigin=eyJpIjoiOTcwYz... ) Re: Stabilize "empty composites" feature ( https://hibernate.atlassian.net/browse/HHH-11936?atlOrigin=eyJpIjoiOTcwYz... ) > > > > If anything, it’s something that should be available at a more granular > level, at the level of a given embeddable class. > > Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) More at the property level, where the @Embedded annotation is. This is about having properties populated with empty composites instead of null , so I don’t see why specifying this at the embeddable class level would make sense. And if your application is written in such a way that you always expect embedded properties to be non-null, then it does make sense to set this globally. ( https://hibernate.atlassian.net/browse/HHH-11936#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-11936#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#100214- sha1:d3cc1a2 )

1 year, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3322) Async, reactive-friendly methods for simple search and indexing

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMmI4MGVi... ) / New Feature ( https://hibernate.atlassian.net/browse/HSEARCH-3322?atlOrigin=eyJpIjoiMmI... ) HSEARCH-3322 ( https://hibernate.atlassian.net/browse/HSEARCH-3322?atlOrigin=eyJpIjoiMmI... ) Async, reactive-friendly methods for simple search and indexing ( https://hibernate.atlassian.net/browse/HSEARCH-3322?atlOrigin=eyJpIjoiMmI... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) For now, just implement reactive ways to execute indexing operations (indexer) and queries (SearchQuery interface). Don’t worry about the rest for now. In particular, let’s not consider scrolls yet. The current APIs seem to mostly do the job, returning {{CompletableFuture}} for indexing works. For search queries, we could add {{fetchAsync()}} methods. Scrolling, or multi-result operations in general, will be another story. We may have to implement Flow.Publisher, but that requires Java 9 at least. So, as I said above... let's not worry about that for now. Note: it would be interesting to introduce some tests using the stub backend, maybe the POJO mapper, and ~~ - RxJava2 ~~ - Mutiny See branch f2f-2018: [https://github.com/hibernate/hibernate-search-6-poc/commit/fb66f9c4196bc0...] ( https://hibernate.atlassian.net/browse/HSEARCH-3322#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3322#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#100214- sha1:d3cc1a2 )

1 year, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2023