Re: [hibernate-dev] [HV/HSEARCH] Free form

@hibernate.org>: > > Your prototype is very Hibernate Search tainted. I wonder how or whether > we want it reusable across Hibernate Validator, Search and possibly more. > > > > Have you captured somewhere the discussion about the new document > builder so I could get a

Re: [hibernate-dev] Hibernate Commons project

On 30 January 2017 at 13:58, Guillaume Smet wrote: > Note that the current version of hibernate-commons-annotations is > org.hibernate.common (without the s at the end, not org.hibernate as Yoann > stated it). > You're right. Wouldn't the simplest solution be to use

Re: [hibernate-dev] Hibernate Commons project

Everything you said seems to make sense to me, so +1. We can see later whether we agree on the other common projects we could add (checkstyle rules, test utils, ...), but I think there won't be many arguments *against* them as long as there is no transitive dependency to these projects for end

Re: [hibernate-dev] [HV/HSEARCH] Free form

Hi, Did the same this week-end, and adapted your work to match the bigger picture of what we discussed on Friday. Basically the "StructureTraverser" is now called "ValueProcessor", because it's not responsible for exposing the internals of a structure anymore, but only to process a structure

Re: [hibernate-dev] NoORM - New groupId and relocation artifacts

One benefit we always get by being consistent is that it's easier for a newcomer to switch from project to project... If it doesn't require more work, we may as well be consistent. Anyway, thanks Guillaume, I added this piece of information to the HSearch ticket:

[hibernate-dev] Hibernate Search 5.6.0.Final and 5.7.0.CR1 released

Hello, We just released Hibernate Search 5.6.0.Final, the first stable release featuring experimental support for Elasticsearch (2.x). We also started the candidate release phase for Hibernate Search 5.7 by releasing version 5.7.0.CR1, with support for ORM 5.2.7 and newer (but not older, see the

[hibernate-dev] [SEARCH] Integration of Mincong's work on adding JSR-352 support

Hello, Following our recent (and successful) efforts to fix blocking issues on https://github.com/mincong-h/gsoc-hsearch/, I recently added a branch on my repo which contains the Hibernate Search codebase, with the addition of a JSR-352 submodule. You can find the branch at [1]. The build is

[hibernate-dev] Hibernate Search 5.7.0.Final and 5.6.1.Final released

Hello everyone, We just released Hibernate Search 5.7.0.Final, compatible with Hibernate ORM 5.2.8. As 5.7 is not compatible with Hibernate ORM 5.0/5.1 anymore, we also released a bugfix version for 5.6 with several backports: Hibernate Search 5.6.1.Final. Be sure to check out our blog for more

Re: [hibernate-dev] Add entity with InheritanceType.JOINED to native query

Hi, I'll let it to actual Hibernate ORM developers (which I'm not) to give you a proper answer (if they have one), but this seems like a bug to me. You best course of action may be to provide a test case and provide it as part of a ticket on JIRA: https://hibernate.atlassian.net/ . If you really

Re: [hibernate-dev] OpenJDK proposal: JDK 9 modules and reflection

I'll try to jump in. I'm mainly providing an external point of view though, since I didn't seriously follow the progress of Java 9. If I understood correctly, modules containing entities would not need to be weak; they *could* be, as a quick solution to migrating to Java 9, but ultimately the

Re: [hibernate-dev] [OGM] Issue with a test and the new operation grouping infrastructure

(Don't know what's the status of this, since it's been discussed on IRC, but jumping in just in case) I tend to agree with Gunnar that storing the association on the owning side of the association seems like a good idea. At least with an external point of view, it seems like the right choice, but

[hibernate-dev] HSEARCH-2358 "fields" attribute in Elasticsearch search results is being ignored

Hi, I wanted to start a discussion about this issue. It's about stored field retrieval. When searching, Elasticsearch can return field values two different ways: * through the "_source" attribute [1], which basically provides a copy-paste of the JSON that was submitted when indexing * or

Re: [hibernate-dev] [OGM] Neo4j integration dependencies

Is there any particular reason why we would not want to create three artifacts, besides backward compatibility? It seems the obvious and ideal solution, but I might be missing something. If there is common code, we can always create a fourth -neo4j-core artifact that would have no interest to

Re: [hibernate-dev] [OGM] Neo4j integration dependencies

On 21 October 2016 at 12:20, Guillaume Smet wrote: > I always prefer to migrate early to the right solution when there is a > compelling reason to do so and a clear logic in it. I totally agree with that, but I think it's more about what we promised to users than

[hibernate-dev] Hibernate Search and Elasticsearch 5 support

Hello, I just finished assessing the required changes for supporting Elasticsearch 5.0. I put the details in this ticket: https://hibernate.atlassian.net/browse/HSEARCH-2434 Here is a quick summary: - Some (non-breaking) changes are required in Jest [1] - We'll have to update the way we

[hibernate-dev] [Hibernate Search] Added a test utility to assert produced log

Hi team, Just so you know, if you ever need to assert that a certain log is produced in your JUnit tests, there's now a tool to do just that in Hibernate Search: org.hibernate.search.test.util.impl.ExpectedLog4jLog [1] You may use it much like you would use the ExpectedException rule: public

Re: [hibernate-dev] Hibernate Search and Elasticsearch 5 support

On 2 November 2016 at 12:59, Guillaume Smet wrote: > The other important point (mentioned in the issue but I think it's > important to outline it here) concerning the analyzers is that they are now > defined per index: there are no global analyzers, you have to define

[hibernate-dev] [SEARCH] Translating analyzer definitions from HSearch to Elasticsearch

Hello everyone, I'm currently working on HSEARCH-2219, "Define analyzers via the REST API", whose purpose is to automatically translate @AnalyzerDefs in Hibernate Search to settings in Elasticsearch, removing the need for users to configure analyzers separately in their Elasticsearch instance.

Re: [hibernate-dev] [OGM] Keeping the order of the collection of elements in MongoDB

lly want to have a clear contract, it means we have to explicitly state somewhere that ordering is undefined unless one is using @OrderColumn / @OrderBy. If we really want to do this, we may as well add "unless you're using a document database" or something like this? Yoann Rodière &

Re: [hibernate-dev] [OGM] Keeping the order of the collection of elements in MongoDB

> > I think it's a reasonable expectation, as long as we're talking > specifically about mapping a *List* and not just a generic Collection. > Ah, this topic again :) I know I'll be all lone, but I'll try anyway! If we do it for List, and unless there are technical issues that prevent us from

Re: [hibernate-dev] [OGM] Keeping the order of the collection of elements in MongoDB

acting with the model that ignoring the order is acceptable. > > BTW I suspect mapping things as a generic Collection is a very unusual > (or lazy) choice; I don't remember ever using it as it's quite > ambiguous, and there's no way any specification diagram will lead you > to recommend using a

[hibernate-dev] Hibernate Search 5.6.0.Beta4 and 5.7.0.Beta1 released

Hello everyone, We just released Hibernate Search 5.6.0.Beta4 and 5.7.0.Beta1, with the latest bugfixes and previously missing features for our experimental Elasticsearch integration. For more information, please see our blog:

Re: [hibernate-dev] ScrollableResults and 6.0

st suggesting making that consistent. > > On Mon, Jan 2, 2017 at 2:36 AM Yoann Rodiere <yo...@hibernate.org> wrote: > >> For what it's worth, changing the signature indeed seems appropriate to >> me: the fewer object arrays, the better. >> Your proposal would require

Re: [hibernate-dev] CI Jenkins upgraded to version 2.38

), but maybe the difference between OGM and Search lies there? Anyway... I'm going for today, maybe I'll see something obvious tomorrow morning! Cheers, Yoann Rodière <yo...@hibernate.org> Hibernate NoORM Team On 3 January 2017 at 18:22, Yoann Rodiere <yrodi...@redhat.com> wrot

[hibernate-dev] [SEARCH] Query-only analyzers with Elasticsearch - new annotation?

Hello team, I'm currently working on HSEARCH-2534, "Query-only analyzer definitions are never added to the index settings with Elasticsearch". This issue is about using analyzers only when querying with Elasticsearch. It is already possible with Lucene, but not in Elasticsearch, because we assume

Re: [hibernate-dev] [SEARCH] Query-only analyzers with Elasticsearch - new annotation?

clearly make such discrimination then this should > be made very clear to our users too, so I'd prefer if we could avoid > introducing new concepts for people to learn.. unless there's strong > need of course. > > Is this issue relating to a specific user request? > > Thanks, &g

Re: [hibernate-dev] [SEARCH] Query-only analyzers with Elasticsearch - new annotation?

but that basically amounts to solution 3 "don't do it". Which is fine as long as we plan to fix it later. Also note we'd still have to explain users that query-only analyzer definitions are not supported with Elasticsearch. Yoann Rodière <yo...@hibernate.org> Hibernate NoORM Tea

[hibernate-dev] [SEARCH] Remove support for (or deprecate) date/calendar resolution?

Hi, That's a catchy subject, now I'm sure I got Guillaume's (angry) attention :) Sanne wanted us to think about feature removal... Here's a proposal. The feature I'd like to deprecate/remove: automatic truncation of date/calendars to a given resolution. It's used like that: @Field

Re: [hibernate-dev] [SEARCH] Remove support for (or deprecate) date/calendar resolution?

January 2017 at 12:53, Guillaume Smet <guillaume.s...@gmail.com> wrote: > Hi, > > On Thu, Jan 5, 2017 at 5:20 PM, Yoann Rodiere <yo...@hibernate.org> wrote: > >> That's a catchy subject, now I'm sure I got Guillaume's (angry) attention >> :) >> >> Sanne want

[hibernate-dev] Hibernate Search 5.5.6.Final released

Hello everyone, We just released Hibernate Search 5.5.6.Final with the latest bugfixes. For more information, please see our blog: http://in.relation.to/2017/01/09/hibernate-search-5-5-6-Final/ Yoann Rodière Hibernate NoORM Team

[hibernate-dev] Hibernate Search 5.6.0.CR1 and 5.7.0.Beta2 released

Hello everyone, We just released Hibernate Search 5.6.0.CR1 and 5.7.0.Beta2, with the latest bugfixes and previously missing features for our experimental Elasticsearch integration. This is the last step before 5.6 is released, so be sure to check it out so you can share your thoughts with us

Re: [hibernate-dev] [OGM] Hibernat OGM contrib repository

Hi, I've moved the contributed dialect for OGM in this repository: > https://github.com/DavideD/hibernate-ogm-contrib Great, thanks :) Which group id should we use? At the moment it is still > org.hibernate.ogm but Iw odul opt for org.hibernate.ogm.contrib > +1 for org.hibernate.ogm.contrib.

[hibernate-dev] [SEARCH] 6.0: what if we flipped our metadata definition upside down?

Hello, Currently, the medata definition mechanisms in Search work this way: - the primary way to define metadata is using annotations - the secondary way to define metadata is programmatic, *but it only instantiates annotations,* simulating annotated entities - classes needing to

Re: [hibernate-dev] [SEARCH] 6.0: what if we flipped our metadata definition upside down?

making the API intuitive for people who wish they could have added the > annotation, but can't for some reason and have to fallback to this > API: the picture they have in mind about their task is still similar > to "add this annotation over there". > > I concur that the strategy to &q

Re: [hibernate-dev] JIRA usage for OGM

Isn't marking those as "New feature" enough? Or, if necessary, tagging them? I obviously can't tell how others use JIRA, but personally I don't dive into old tickets every day. Most of the time I only check the new (incoming) tickets and those assigned to the next release. So, those extra tickets

[hibernate-dev] Hibernate Search 5.8.0.CR1 released

Hello, We just released Hibernate Search 5.8.0.CR1, with performance improvements and various bugfixes. This is the last step before 5.8 is released. Be sure to check it out so you can share your thoughts with us before the release! You can find more information about 5.8.0.CR1 on our blog:

[hibernate-dev] Hibernate Search 5.8.0.Beta4 released

Hello, We just released Hibernate Search 5.8.0.Beta4, with AWS integration and various bugfixes. We expect this to be the last 5.8.0 Beta, so be sure to check it out and give us some feedback before the feature freeze! You can find more information about 5.8.0.Beta4 on our blog:

Re: [hibernate-dev] Stuck build on CI

> This build on CI seems stuck since yesterday: Yes, there was a race condition that I fixed before leaving on Friday. Sorry I didn't realize this build was still running. > Also I noticed a huge amount of log output: "121,741 KB". Do you really > need all that output for each build? Esp. given

Re: [hibernate-dev] Hibernate Search: Adding more "hidden" fields to the index

ernate NoORM Team yo...@hibernate.org On 27 April 2017 at 15:59, Yoann Rodiere <yrodi...@redhat.com> wrote: > I wonder, what's the benefit for HSEARCH-2616? Do you want to have that > field so that we can just use AddLuceneWorks everywhere, and run targeted > delete operatio

Re: [hibernate-dev] Hibernate Search: Adding more "hidden" fields to the index

the discussion on JIRA. Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 27 April 2017 at 18:19, Sanne Grinovero <sa...@hibernate.org> wrote: > On 27 April 2017 at 15:11, Yoann Rodiere <yo...@hibernate.org> wrote: > > I wonder, what's the benefit for HSEARCH-2616? Do yo

Re: [hibernate-dev] Questions on HS + ES

Hi, > * Can we have multiple indexes for the same entity, with different > fields, geared towards different use cases? No, it's not currently possible. Each entity is mapped to a single index. But you can map each property of your entity to multiple index "properties", so you can actually handle

[hibernate-dev] [SEARCH] Master nodes without class definitions

Hello, In our roadmap for 5.8, we have this: Removal of class definitions from master nodes > The integration of a "master node" needs to be simplified, both in terms > of user configuration and implementation. We plan to not need user classes > (entities) on such a node, so that in future it

[hibernate-dev] Hibernate Search 5.8.0.Beta2 released

Hello, We just released Hibernate Search 5.8.0.Beta2, bringing us that much closer to the final release. You can find more information about 5.8 in general and the Beta2 specifically on our blog: http://in.relation.to/2017/05/11/hibernate-search-5-8-0-Beta2/ Yoann Rodière Hibernate NoORM Team

Re: [hibernate-dev] "rebranding" the Hibernate Search "ram" directory

Sanne, the confusions you pointed out were: - Thinking it's more efficient than other providers (it's not) - Thinking it's integrated to replicated in-memory datastores such as Infinispan (it's not) So you'd want a name that says "it's not persistent" and probably "it's easy to set up"

Re: [hibernate-dev] Introducing a new API in Hibernate Search to "sign" HTTP requests to Elasticsearch

> > Did you instead consider to just let users provide their custom > instance of org.elasticsearch.client.RestClient? It's still leaking an > implementation detail of Hibernate Search, but at least it's one > indirection less. The only way to add AWS authentication to the RestClient is to use

Re: [hibernate-dev] Introducing a new API in Hibernate Search to "sign" HTTP requests to Elasticsearch

What if new options get added to > RestClientBuilder? What's the benefit of this catch-up game? > > > > > 2017-06-02 14:47 GMT+02:00 Yoann Rodiere <yo...@hibernate.org>: > >> There's no exposure of HTTP Client in this SPI. Yes, if people need to > >> customize the HTTP clien

Re: [hibernate-dev] Introducing a new API in Hibernate Search to "sign" HTTP requests to Elasticsearch

Hibernate NoORM Team yo...@hibernate.org On 2 June 2017 at 14:47, Yoann Rodiere <yo...@hibernate.org> wrote: > > There's no exposure of HTTP Client in this SPI. Yes, if people need to > > customize the HTTP client to be used by the returned RestClient > > instance,

Re: [hibernate-dev] Introducing a new API in Hibernate Search to "sign" HTTP requests to Elasticsearch

really matters, right? Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 2 June 2017 at 14:25, Gunnar Morling <gun...@hibernate.org> wrote: > 2017-06-02 12:49 GMT+02:00 Yoann Rodiere <yo...@hibernate.org>: > >> There's an important difference: one exposes Apac

Re: [hibernate-dev] Introducing a new API in Hibernate Search to "sign" HTTP requests to Elasticsearch

lt;gun...@hibernate.org> wrote: > I reckon you are making fun of me. Anyways, I've had my say :) > > 2017-06-02 15:03 GMT+02:00 Yoann Rodiere <yo...@hibernate.org>: > >> What's the benefit of this catch-up game? > > > > Not tainting our SPI with RestClient :) &

Re: [hibernate-dev] Let's avoid @hsearch.experimental javadoc tags in SPI

Hi, Answers below. Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 6 June 2017 at 18:48, Sanne Grinovero wrote: > == SPI have very long guarantees, anyway > > Considering that an SPI contract has relatively low SLAs I'd like to > be way more "aggressive" in the

[hibernate-dev] Hibernate Search 5.8.0.Beta3 released

Hello, We just released Hibernate Search 5.8.0.Beta3, with easier analyzer configuration, AWS compatibility and DI integration. You can find more information about 5.8.0.Beta3 on our blog: http://in.relation.to/2017/06/13/hibernate-search-5-8-0-Beta3/ Yoann Rodière Hibernate NoORM Team

Re: [hibernate-dev] [Search and more] What is new in a give release

gt; >> On 13 September 2017 at 10:51, Yoann Rodiere <yo...@hibernate.org> wrote: >> >>> It's more the number of columns, what if you add more version, should I >>>> scroll horizontally? Also releeases tend to be shown vertically with >>>

Re: [hibernate-dev] [Search and more] What is new in a give release

to have this as part of the > > series info > > > > I think the individual series pages are missing a key piece of > > information... the "synopsis" of that series. I guess partially this > fits > > under "what's new" > > > > Other tha

Re: [hibernate-dev] [Search and more] What is new in a give release

No answer? So I guess I can merge it whenever I want? :-) Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 19 September 2017 at 08:36, Yoann Rodiere <yo...@hibernate.org> wrote: > So, following the comments and a discussion on Hangouts on Friday, I > worked a bit more

[hibernate-dev] Hibernate Search 5.8.0.Final released

Hello everyone, We just released Hibernate Search 5.8.0.Final. Hibernate Search now integrates with all version of Elasticsearch from 2.0 to 5.6! Check out our blog for more information about this release: http://in.relation.to/2017/09/14/hibernate-search-5-8-0-Final/ Yoann Rodière Hibernate

Re: [hibernate-dev] [Search and more] What is new in a give release

Ok, this will never end... It was good to merge less than 24h ago and now you're arguing against the very point of this work: provide users with more information regarding each series, so that they know what's new. (see the first email by Emmanuel) Please make concrete, exhaustive proposals. From

[hibernate-dev] Hibernate Search 5.8.0.Final released

Hello everyone, We just released Hibernate Search 5.8.1.Final, with several Elasticsearch-related fixes. Check out our blog for more information about this release: http://in.relation.to/2017/10/04/hibernate-search-5-8-1-Final/ Yoann Rodière Hibernate NoORM Team yo...@hibernate.org

Re: [hibernate-dev] Hibernate Search 5.8.0.Final released

As you may have understood, the subject of the previous email was wrong. The version we just released is indeed 5.8.1.Final and not 5.8.0.Final. Apologies for the confusion. Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 4 October 2017 at 09:31, Yoann Rodiere <yo...@hibernate.

Re: [hibernate-dev] New layout for in.relation.to

Hush, it's a sensitive topic :) Let's just say it's on purpose, and it could have been... harsher. The current style is already a compromise. Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 4 October 2017 at 13:22, Hardy Ferentschik wrote: > Hi, > > I like the

Re: [hibernate-dev] [Search and more] What is new in a give release

recently, and was not done on the grounds that it gets out of >> date quickly. >> Still users badly need it so unless someone has a better idea, let's >> agree on trying to keep it up to date manually. Let's try structure it >> in such a way that it won't need to be updated for e

Re: [hibernate-dev] [Search and more] What is new in a give release

inor suggestions: >> - could the two links we have for each release on search/releases/ on >> two separate lines? Or something else to make it clear that there are >> two linkes. >> - Regarding the "Compatibility matrix", the header line (the one in >> blac

Re: [hibernate-dev] [Search and more] What is new in a give release

e > describing the family? > > Thanks, > Sanne > > > On 8 September 2017 at 13:53, Yoann Rodiere <yo...@hibernate.org> wrote: > > Hey, > > > > I pushed an update to staging. I only converted the "Search" part for > now. > > What ch

Re: [hibernate-dev] [Search and more] What is new in a give release

Hibernate NoORM Team yo...@hibernate.org On 8 September 2017 at 16:44, Yoann Rodiere <yo...@hibernate.org> wrote: > Steve, > > If I understood correctly, the main difference between what I did and what > you want is you don't want a "hub" pointing to different versions,

Re: [hibernate-dev] [Search and more] What is new in a give release

Hey, About Search, true, the information is somewhat hidden in many blog posts. I'm not sure the roadmap is the right place, though, since we probably want the format to be different for past and future releases: information for past releases is typically more precise and more verbose, with code

[hibernate-dev] [SEARCH] Code style - imports

Hello all, I just noticed that our IDEA codestyle configuration files have specific rules about how to organize imports, whereas the Eclipse ones don't. The most noticeable difference: organizing imports in Eclipse puts static imports at the top, while in IDEA they end up at the bottom. But there

Re: [hibernate-dev] [Search and more] What is new in a give release

7 at 11:48, Sanne Grinovero <sa...@hibernate.org> wrote: > On 13 September 2017 at 10:41, Emmanuel Bernard <emman...@hibernate.org> > wrote: > > On Tue 17-09-12 13:50, Yoann Rodiere wrote: > >>> > >>> > >>> - Releases speaks less tha

Re: [hibernate-dev] [Search and more] What is new in a give release

t; proposed makes it more neutral. You could even just name them Series > - The migration guide should probably be referenced from each individual > series page. > - the matrix does not scale very well to that many versions. > - in the dedicated series page, "Reference" i

Re: [hibernate-dev] [SEARCH] Code style - imports

September 2017 at 11:45, Sanne Grinovero <sa...@hibernate.org> wrote: > On 12 September 2017 at 10:42, Yoann Rodiere <yo...@hibernate.org> wrote: > >> Fundamentally no IDE will ever produce exactly the same code so you > >> need to learn control your primal lust for

Re: [hibernate-dev] [SEARCH] Code style - imports

;> base to satisfy aesthetics. >> >> Perhaps we could have separate sets of rules, some stricter to be >> applied on new modules; their impact would be limited but even having >> one module with strict rules would encourage people to reconfigure >> their IDE in &quo

Re: [hibernate-dev] [Search and more] What is new in a give release

Aaaand it's merged. I tried to clean up release YAML files as much as possible for every project, adding missing files as necessary. You may want to add some content to each project, most notably to the "what's new" section of each series, but also to the compatibility matrix of each series. I

Re: [hibernate-dev] ORM release process

Hi, Thanks Guillaume for stepping up to explain this. I should have done it but I guess I forgot :) > You just need to create it for a major. > It's this page: http://hibernate.org/orm/releases/5.2/ presenting the > whole > major. I think there's a confusion between major, minor an micro

Re: [hibernate-dev] New layout for in.relation.to

eam yo...@hibernate.org On 2 October 2017 at 11:12, Guillaume Smet <guillaume.s...@gmail.com> wrote: > On Mon, Oct 2, 2017 at 9:12 AM, Yoann Rodiere <yo...@hibernate.org> wrote: > > Add a button to display the menu on mobile > > I don't think it has much value on in.r

Re: [hibernate-dev] Website - Remove the Google+ links

+1. Either we properly mirror our tweets/blog posts to G+, or we stop advertising that account. Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 28 September 2017 at 11:51, Guillaume Smet wrote: > Hi, > > We have a couple of Google+ links here and there on

Re: [hibernate-dev] [Search and more] What is new in a give release

What's in the matrix is up to each project. You can remove content by editing the .yml file for each series, and removing elements from site.yml under projects.orm.integrations. I'd argue that moving away from the matrix for ORM just because Java compatibility is "not enough" will force us to add

Re: [hibernate-dev] [Search and more] What is new in a give release

ersion. > > Say we want to prune 5.7 - not being in your above list - people will > still want to be able to find it when upgrading from 5.6 -> 5.8 > > Thanks, > Sanne > > > > > BTW tools has a Downloads link, not Releases. > > > > Emmanuel > > >

Re: [hibernate-dev] [website] Specific series page

at the top ;) Anyone against it? Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 28 September 2017 at 09:42, Yoann Rodiere <yrodi...@redhat.com> wrote: > So the order would be: > > * Compatibility > * Documentation > * How to get it > * What's new > * Migrate >

[hibernate-dev] Bugfix releases for Hibernate Search 5.5, 5.6 and 5.7

Hi all, We just published three bugfix releases of Hibernate Search: 5.5.8.Final, 5.6.3.Final and 5.7.2.Final. Please see the blog for more details: http://in.relation.to/2017/08/24/hibernate-search-5-5-8-and-5-6-3-and-5-7-2/ Thanks, Yoann Rodière Hibernate NoORM Team yo...@hibernate.org

Re: [hibernate-dev] ETA Hibernate-ORM 5.2.11 release?

Hi Gail, We have a fix on the Hibernate Search side and I confirmed the fix should not involve any retro-compatibility issue, so we can treat this issue as non-blocking for the ORM release. Thanks, Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 4 September 2017 at 14:23, Guillaume

[hibernate-dev] Hibernate Search 5.9.0.Beta1 released

Hello, We just released Hibernate Search 5.9.0.Beta1, with a new JSR 352 integration adding a mass indexing job with a resume-after-failure feature ! Check out our blog for more information about this release: http://in.relation.to/2017/11/27/hibernate-search-5-9-0-Beta1/ Yoann Rodière

Re: [hibernate-dev] JPA Compliance

> I think we should just change the behavior of calling EMF#close on a closed EMF. > Any application that happens to be relying on us no-op'ing > this call can easily change that to protect the call with an `#isOpen` check. Mentioning this just in case: the javadoc for the AutoCloseable interface

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

t happened to the 2.0 CDI artifact on Maven Central? >>>>>> It was there last week, but is no longer there... >>>>>> >>>>>> On Thu, Dec 14, 2017 at 5:54 AM Steve Ebersole <st...@hibernate.org> >>>>>> wrote: >>>>>> >>>>>>

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

> On Thu, Dec 14, 2017 at 7:44 AM Steve Ebersole <st...@hibernate.org> > wrote: > >> But your answer above does not answer my question ;) >> >> I still have no idea how to go from name+Class -> bean. >> >> >> On Thu, Dec 14, 2017 at 7:41 AM Yoann

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

en Central? It >>>> was there last week, but is no longer there... >>>> >>>> On Thu, Dec 14, 2017 at 5:54 AM Steve Ebersole <st...@hibernate.org> >>>> wrote: >>>> >>>>> Thanks for the replies. So unless we hear otherwise from anyon

Re: [hibernate-dev] Killing hibernate-jpa-api ?

Seems like the right thing to do. I'm just concerned about the license. Is it identical? Some people might be upset to get a new dependency pulled "automatically" if it has a stricter license... Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 13 December 2017 at 13:10, Sanne Grinovero

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

Same here, compositions don't seem to be a reasonable use case. And even if users provide a custom bean registry, they could just implement their specific behavior for a few specific case, then retrieve another implementations on their own and delegate to it however they want. Overriding the

Re: [hibernate-dev] [Search] Providing an alias for the indexed type

Indeed it would make sense to allow custom type names, in particular in ES 5 and below. In Elasticsearch 6, you can only have one type per index. The main impact is that we will have to choose between two solutions: 1. Either we continue as before (multiple types per index), but we somehow

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

; wrote: > >> Yoann, does this approach still need to do the injections >> (javax.enterprise.inject.spi.InjectionTarget)? >> >> >> On Thu, Dec 14, 2017 at 8:01 AM Yoann Rodiere <yo...@hibernate.org> >> wrote: >> >>> Here is how it should work from what I understand (adapted from an

[hibernate-dev] CDI integration in Hibernate ORM and the Application scope

Hello all, TL;DR: Application-scoped beans cannot be used as part of the @PreDestroy method of ORM-instantiated CDI beans, and it's a bit odd because they can be used as part of the @PostConstruct method. I've been testing the CDI integration in Hibernate ORM for the past few days, trying to

Re: [hibernate-dev] CDI integration in Hibernate ORM and the Application scope

messages. > > If that's not doable *or a priority* then all we can do is try to make > it clear enough that there will be limitations and hopefully describe > these clearly. Some of such limitations might be puzzling as you > describe. > > > > On 20 December 2017 at 12:50, Y

[hibernate-dev] Hibernate Search 5.10.0.Final released

, and Java 9 automatic module names. Check out our blog for more information about this release: http://in.relation.to/2018/05/17/hibernate-search-5-10-0-Final/ -- Yoann Rodiere yo...@hibernate.org / yrodi...@redhat.com Software Engineer Hibernate NoORM team

Re: [hibernate-dev] Disallow uncategorized topics

Done: users must now choose a category, and may use "Miscellaneous" if their topic really doesn't fit any category. On Tue, 22 May 2018 at 11:48 Sanne Grinovero <sa...@hibernate.org> wrote: > On 22 May 2018 at 10:30, Yoann Rodiere <yo...@hibernate.org> wrote: > >

Re: [hibernate-dev] Disallow uncategorized topics

n try naming it "Uncategorized", but there's already a "system" category with this name (only enabled if we don't enforce categories), so I'm not sure if Discourse will allow that. On Tue, 22 May 2018 at 11:22 Sanne Grinovero <sa...@hibernate.org> wrote: > On 22 May 2018

Re: [hibernate-dev] Disallow uncategorized topics

n particular, I see no value in a "Miscellaneous" category; it's not > like people are going to think "cool, Miscellaneous is exactly what I > was looking for". > > On 22 May 2018 at 09:43, Yoann Rodiere <yo...@hibernate.org> wrote: > > Hi, > > > >

Re: [hibernate-dev] Stride

ot; and "HipChat has issues but we don't know if they will be solved by > Stride". > > Note that my position is not "we should stay on HipChat forever" because we > can't as they will close the service at some point. My position is: > - I'm not sure the risk of mov

[hibernate-dev] Disallow uncategorized topics

monitor. Would anyone object to disallowing uncategorized topics? I can create a "Miscellaneous" category if you want, but I'd really like people to pick a category when they create a topic. -- Yoann Rodiere yo...@hibernate.org / yrodi...@redhat.com Software Engineer Hibernate

Re: [hibernate-dev] Changes to the JIRA "Pull request sent" status

a "In progress" status) and IMHO > it was a regression. > > If someone is against it and it was an intentional change, please speak up. > > -- > Guillaume > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org

Re: [hibernate-dev] Native SQL Queries and Parameters

er.java#L106 <https://github.com/hibernate/hibernate-search/blob/29c6861ac89c91ea03c4b97cd4e6225d10bb7464/jsr352/core/src/main/java/org/hibernate/search/jsr352/massindexing/impl/util/CompositeIdOrder.java#L106>* On Mon, 18 Jun 2018 at 09:44 Yoann Rodiere wrote: > If by "basic t

[hibernate-dev] Hibernate Search 5.10.1.Final, 5.9.2.Final and 5.6.5.Final released

Hello, We just published bugfix releases for the branches we actively maintain: 5.10, 5.9 and 5.6. Check out our blog for more information about these releases: http://in.relation.to/2018/05/29/hibernate-search-5-10-1-Final-5-9-2-Final-5-6-5-Final/ -- Yoann Rodiere yo...@hibernate.org / yrodi

[hibernate-dev] [NoORM] A simpler README.md?

implemented in Search; please let me know what you think. The PR: https://github.com/hibernate/hibernate-search/pull/1692 Preview of the README as seen from the GitHub web view: https://github.com/yrodiere/hibernate-search/blob/ae4d347fa4c647a3c5ddb6f43412cf3dce0e354e/README.md Cheers, -- Yoan

Re: [hibernate-dev] [NoORM] A simpler README.md?

onally have to update >> the README, and I don't think people will expect that a zip they keep >> in a drawer will be the better source of information if they happen to >> have access to hibernate.org >> >> Cheers, >> Sanne >> >> >> >> On 4 J

  1   2   3   4   >