Hi all,
the Infinispan/Hibernate integration test - which is run by the
Infinispan team and uses TeamCity instead of Jenkins - is failing with
the below cryptic error.
Did the ORM switch to using Git modules?
Error collecting changes for VCS repository
To be fair I would have mapped that differently.
Your Shipment arrives at a certain *point in time* (long, UTC based)
in a certain Port (mapped with Foreign Key).
A Port would have a reference to a local Timezone, and UI could decide
to use that (or a different one) for rendering, based on other
On 30 August 2016 at 10:09, Emmanuel Bernard wrote:
> I am not sure if that is still relevant but in the past, either HSEARCH
> or HV were keeping the ReflectionManager around to use it at runtime
> (either because metadata was loaded lazily or because of a reboot of the
>
so, is there a way we prefer to generate poll for the website or I
> can just rely on the comment?
Maybe make a poll on twitter?
https://blog.twitter.com/2015/introducing-twitter-polls
>
> This one looks nice: http://www.poll-maker.com/
>
> On Fri, Aug 26, 2016 at 1:48 PM, Sanne G
On 26 August 2016 at 12:35, Emmanuel Bernard wrote:
> On Fri 2016-08-26 11:32, Gunnar Morling wrote:
>> > How much additional work would it be to keep the "old" rest in a legacy
>> module separated from the pure one?
>> > Does it even make sense?
>>
>> As a user, when
eed to know about that instead of the JPA one.
>>
>> > Would that live in OGM or ORM ?
>>
>> Good question, depends on whether there is any RDBMS with native enum
>> support?
>>
>>
>> 2016-08-26 13:02 GMT+02:00 Sanne Grinovero <sa...@hib
+1
On 24 August 2016 at 08:11, Gunnar Morling wrote:
> Hi,
>
> Now that the first changes in HV are being made towards BV 2.0, one
> question is which version of HV that should be.
>
> For BV we are doing a major version jump from 1.1 to 2.0 as the minimum
> Java version is
In the context of Hibernate OGM, it turns out that some datastores
have a rather nice "native" support for enums.
We aim to map each property of the user's domain model to its most
appropriate "physical type", unless the choice is overriden by the an
explicit user request.
In the case of an
On 11 August 2016 at 15:19, Scott Marlow <smar...@redhat.com> wrote:
>
> On 08/11/2016 06:19 AM, Sanne Grinovero wrote:
>>
>> I've been watching this:
>> - https://github.com/wildfly/wildfly/pull/8984
>>
>> And that's the reason I've been asking fo
d 5.1, and also all people running on WF
from benefiting of the Elasticsearch features.
Vice-versa, if we release 5.6 with Elasticsearch support and then follow up
quickly with a very similar 5.7 which just introduces the changes to catch
up with ORM 5.2, then we have something good for everyone.
Hi all,
as you might be aware, ORM 5.2 made some rather radical internal work,
and the latest Hibernate Search releases aren't compatible.
So far, business as usual: we typically simply catch up on the next minor.
The problem is that normally Hibernate Search releases are time-boxed
- with us
I've been watching this:
- https://github.com/wildfly/wildfly/pull/8984
And that's the reason I've been asking for a 5.1 release, as it has
been blocked by issues for long.
Indeed if this wasn't being tracked for 10.1 that's sad as we need
WildFly releases with up to date versions of ORM to
gt; understood Guillaume that the workaround is not really viable:
>
>> The fact is that using maven-jar-plugin 3.0.0 is not an option as it
> has memory issues
>
> Or did I miss something?
Yes, I replied to that.
>
>
> 2016-08-10 11:53 GMT+02:00 Sanne Grinovero <sa...@hibernate.org&g
o.
>
> Thanks,
>
> --Gunnar
>
>
> 2016-08-10 10:15 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>>
>> On 10 August 2016 at 07:12, Guillaume Smet <guillaume.s...@gmail.com>
>> wrote:
>> > Hi Sanne,
>> >
>> > First, sorry for
ng
list.
Thanks,
Sanne
>
> --
> Guillaume
>
> On Tue, Aug 9, 2016 at 11:51 PM, Sanne Grinovero <sa...@hibernate.org> wrote:
>> Hi all,
>> I was having critical issues with Eclipse / OGM after a recent rebase,
>> which seemed was caused by:
>> - https://
Hi all,
I was having critical issues with Eclipse / OGM after a recent rebase,
which seemed was caused by:
- https://hibernate.atlassian.net/browse/OGM-1102
The new maven-jar-plugin is no longer compatible with latest m2e
integration, Fred Bricon already published an m2e preview with a fix;
if
Hi all,
I've upgraded our CI nodes to run:
java version "9-ea"
Java(TM) SE Runtime Environment (build 9-ea+130)
Java HotSpot(TM) 64-Bit Server VM (build 9-ea+130, mixed mode)
I hope nothing changes in our build status, but if there are failures
this might be a possible cause.
Thanks,
Sanne
Hi Steve,
yes you have to skip WildFly based tests when on Java 9: it doesn't work yet.
There's a new WildFly release 10.1.0.CR1 which boots and works
*mostly*, but several frameworks it contains aren't fully compatible
yet so you might be lucky, but no guarantees. Among the things now
working
I'm surprised, we had for sure longer posts. Someone changed this recently?
On 1 Aug 2016 16:04, "Vlad Mihalcea" wrote:
> Hi,
>
> Can anyone help me with the following task for the forum. Currently, our
> post length is limited to 64 chars, which makes it really
, should I put Red Hat or Hibernate?
>> At the moment I'm using Hibernate and hibernate.org as organizarion
>> url, but let me know.
>>
>> Cheers,
>> Davide
>>
>> On Thu, Jul 21, 2016 at 11:26 PM, Guillaume Smet
>> <guillaume.s...@gmail.com> wrot
ation which is a related, reported
> bug.
Fair enough, it has to work clearly and correctly first. People will
have to come back on this if they have concrete data on how it
performs, that's usually a better approach than trying to predict or
make it unnecessarily complex.
-- Sanne
>
> On Mo
Thanks, that's very helpful! Starting to play now.
On 26 July 2016 at 13:15, Emmanuel Bernard wrote:
> I made more progress with the full interfaces for the DSL
> https://github.com/hibernate/hibernate-search/pull/1132
>
> You can play with it in your IDE, runtime won't
On 25 July 2016 at 19:55, Steve Ebersole <st...@hibernate.org> wrote:
> See inline...
>
>
> On Mon, Jul 25, 2016 at 1:06 PM Sanne Grinovero <sa...@hibernate.org> wrote:
>>
>> some comments inline:
>>
>> On 25 July 2016 at 18:27, Steve Ebersole <
some comments inline:
On 25 July 2016 at 18:27, Steve Ebersole wrote:
> I wanted to start a consolidated discussion about multi-load support. This
> relates to a few Jiras, questioning a few different aspects of its current
> behavior:
>
>
Hi all,
we're still needing a release of Hibernate ORM 5.1.1 for Hibernate OGM..
could we plan for one soon please?
Thanks,
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> Search for the evil artifact"}
>> -> so our JPQL queries don't work if we only have one property in the
>> embedded. We might also want to special case this but I really don't
>> think it's a good idea.
>>
>> While this discussion might seem to come out of the blue, it
Hi Guillaume,
yes I'm aware of the issue; we discussed it before, I think on this
same mailing list but maybe it was during our last meeting.
We really need to fix that metadata; Stefania (my partner) is an SEO
consultant and is shocked at how bad we do with this; apparently we
are a funny
Hi Vlad,
I think that might be quite tricky to implement, as it might not
always be clear into which region we'd need to lookup from, or
invalidate, not least locks might need to cross multiple regions.
Think for example when a type A is removed with ID=1, and then a type
B with the same ID is
atabase.
>
> Sure, migration support is on the roadmap ;)
>
>
>
>
>
> 2016-07-12 11:06 GMT+01:00 Sanne Grinovero <sa...@hibernate.org>:
>>
>> On 12 July 2016 at 10:55, Gunnar Morling <gun...@hibernate.org> wrote:
>> > Hi,
>&g
On 12 July 2016 at 10:55, Gunnar Morling wrote:
> Hi,
>
> We had an interesting discussion on how to map element collections of
> component types with a single column to document stores such as MongoDB.
>
> E.g. assume we have
>
> @Entity
> public class Person {
>
>
Hi all,
I've enabled github's new feature to restrict pushing to the
`production` branch of:
- https://github.com/hibernate/hibernate.org
- https://github.com/hibernate/in.relation.to
It will not allow pushing with "force" on the reference branch.
A general reminder: if you think you need to
s. That is no longer a real requirement.
>>
>> Any disagree?
>>
>> On Tue, Jul 5, 2016, 11:58 AM Sanne Grinovero <sa...@hibernate.org> wrote:
>>
>> > Hi all,
>> > today creating a unit test I was greeted by this "old friend":
>> &
Hi all,
today creating a unit test I was greeted by this "old friend":
> org.hibernate.MappingException: Composite-id class must implement
> Serializable:
shall we get rid of this requirement?
It's just an inconvenience for end users to have to remember this
marker, as far as I know we don't
;> >
>>> > Vlad
>>> >
>>> > On Fri, Jul 1, 2016 at 11:19 AM, andrea boriero <and...@hibernate.org>
>>> > wrote:
>>> >
>>> > > i have just realized and sent a new message with the correct subject.
>&
Hi Andrea,
the email subject mentions 5.0.9, the blog talks about 5.2.1 .. did we
release both?
Thanks,
Sanne
On 1 July 2016 at 09:13, andrea boriero wrote:
> For details:
> http://in.relation.to/2016/06/30/hibernate-orm-521-final-release/
>
(Incl. Types) is injected into the Dialect during
>>>>>>> Dialect construction based on some explicit configuration. In that
>>>>>>> way the
>>>>>>> relation between Dialect and the spatial capability mirrors the
>>>>>&
On 27 June 2016 at 16:23, Scott Marlow wrote:
>>
>> That dependency to org.hibernate:main from org.jboss.as.ejb3 still looks
>> a bit scary. My simple test passes, not sure whether that may be a
>> problem in other cases, though?
>>
>
> Sorry, I missed this part of your email.
ist to be cleaned up?
--Sanne
>
> --Gunnar
>
>
>
>
> 2016-06-27 15:39 GMT+02:00 Scott Marlow <smar...@redhat.com>:
>>
>>
>>
>> On 06/25/2016 05:12 PM, Sanne Grinovero wrote:
>> > On 25 June 2016 at 13:15, Gunnar Morling <gun...@h
Hi Mark,
you wouldn't expect the timeout to be "reset" to some default value
when your code writes to an entity?
If you could explain the use case, that might help us to understand this.
Thanks,
Sanne
On 27 June 2016 at 14:47, Mark Paluch wrote:
>
> Hi Guillaume,
>
> TTL
Nice idea!
since the modules were merged already, don't we already require geolatte-geom ?
I guess some code might be intentionally designed to fail gracefully
about this library being there or not, but we'd need to make sure that
can be tested for it to be maintainable.
My preference would be
I've updated the OpenJDK preview of JDK 9 to build 9-ea+124 on our CI servers.
I expect it all to work like before, but in case you receive a failure
report be aware that it might relate to the JVM upgrade.
For a general overview of our Java 9 compatibility status see here as usual:
-
On 25 June 2016 at 13:15, Gunnar Morling wrote:
> Ok, so this was caused by the module dependency
> from org.hibernate.jipijapa-hibernate5 to org.hibernate. Seems I need to
> create a 5.1-specific adapter module, too, and require that to be
> configured by users via
11:20 AM, Steve Ebersole <st...@hibernate.org>
>> wrote:
>>>
>>> http://ci.hibernate.org/job/hibernate-orm-master-h2-main/
>>> http://ci.hibernate.org/job/hibernate-orm-master-h2-check/
>>>
>>> Initial attempt
>>>
>>> On Sat,
+1 keep those releases coming!
and yes those fixes need to be made available better sooner than later.
On 24 Jun 2016 09:14, "Gunnar Morling" wrote:
> Hi,
>
> I noticed there is a 5.0.1 version in JIRA for OGM, and a handful of issues
> are assigned to it. Do we still plan
for creating a report with changed public
> API/SPIs. Running this prior to a release - comparing to the last stable
> version - helps to detect any unintentional changes and create a public
> report / migration notes for intentionally changed things.
>
>
> 2016-06-20 12:47 GMT+02:0
On 20 June 2016 at 08:33, Emmanuel Bernard wrote:
> Are the incompatibilities here for good on ORM, or could they be
> reverted / softened in the 5.2 branch to allow for an easier path?
I'm working on a set of PRs for both ORM and Search which reduce the
list of
t;> testRuntime( 'org.jvnet.jaxb2_commons:jaxb2-basics:0.11.0' )
>> testRuntime( 'org.jvnet.jaxb2_commons:jaxb2-basics-ant:0.11.0' )
>> testRuntime( 'javax:javaee-api:7.0' )
>> }
>> // ~~
>>
>
On 18 June 2016 at 18:50, Chris Cranford wrote:
> +1
>
> I think (1) and (2) on each push still makes sense with (3) being nightly.
+1
-- Sanne
>
> Chris
>
>
> On 06/18/2016 11:33 AM, Steve Ebersole wrote:
>> We have been having a lot of timeouts on the ORM CI builds.
g> wrote:
>>
>> Yep, we discussed that approach last year already:
>> http://lists.jboss.org/pipermail/hibernate-dev/2015-March/012250.html
>>
>> 2016-06-13 9:49 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>>
>> > On 13 June 2016 at 07
There have been various complaints that people can't upgrade to the
latest Hibernate ORM because they don't have a compatible version of
Hibernate Search.
Rejected 3 issues on JIRA as duplicates of:
https://hibernate.atlassian.net/browse/HSEARCH-2296
We never guaranteed compatibility beyond the
Thanks Max!
no worries, we have no rush. Just seems nice to be listed there as well ;)
My evil plan includes to make it easy to write a unit test to somehow
associate to the process of reporting an issue on JIRA.. it would be
great if you could discuss this use case when you meet with them face
lidator/commit/8a0eb0bfbc7610ea6fc9962eef024a98c3f9468c#diff-963bab11ed76f80c4a804903ed66e03fR34
>
>
> 2016-06-12 22:18 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>>
>> Some more progress by simply setting this environment variable:
>>
>> GRADLE_OPTS="-XaddExports:java.securit
On 7 June 2016 at 13:41, Steve Ebersole <st...@hibernate.org> wrote:
> If you send a PR I will include it.
Thanks Steve, I finally got to it:
- https://hibernate.atlassian.net/browse/HHH-10839
- https://github.com/hibernate/hibernate-orm/pull/1418
>
> On Sun, Jun 5, 2016 at
:56, Sanne Grinovero <sa...@hibernate.org> wrote:
> On 11 June 2016 at 18:47, Sanne Grinovero <sa...@hibernate.org> wrote:
>> On 11 June 2016 at 18:25, Steve Ebersole <st...@hibernate.org> wrote:
>>> The ORM failure seems to be a Gradle/JDK9 issue. Any ide
On 11 June 2016 at 18:47, Sanne Grinovero <sa...@hibernate.org> wrote:
> On 11 June 2016 at 18:25, Steve Ebersole <st...@hibernate.org> wrote:
>> The ORM failure seems to be a Gradle/JDK9 issue. Any idea about that?
>
> Not sure, that's a new one :)
>
adle 2.12 .. I'm not at a
terminal at the moment, I could try later.
>
> On Fri, Jun 10, 2016, 4:39 PM Sanne Grinovero <sa...@hibernate.org> wrote:
>>
>> Hi all,
>> please try to have a look at this page when you have a moment:
>> - http://ci.hibernate.org
forum posts for details). And I
> am not going to make this a manual step for each and every release.
>
> On Tue, Jun 7, 2016 at 3:42 AM Sanne Grinovero <sa...@hibernate.org> wrote:
>>
>> I've seen quite some people struggling with the upgrade to Hibernate
>> ORM 5
rstood that you meant to re-distribute a customized WF
image so I was quite confused :)
>
> 2016-06-08 16:59 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>>
>> On 8 June 2016 at 08:11, Gunnar Morling <gun...@hibernate.org> wrote:
>> > 2016-06-07 15:51 GMT+02:0
On 8 June 2016 at 08:11, Gunnar Morling wrote:
> 2016-06-07 15:51 GMT+02:00 Steve Ebersole :
>
>> Too bad we can't just publish a Docker image.
>>
>
> We could do that, but I think we should have a solution for non-Docker
> users, too.
What's the point
On 8 June 2016 at 15:06, Steve Ebersole wrote:
> Well the reasoning was discussed on this list and everyone agreed :) It
> was part of a larger discussion about releases and maintaining maintenance
> branches. But if everyone, I am ok with doing CR (only) for minor
+1
I've also hit some incompatible API changes which I only figured out
too late (when attempting to upgrade Hibernate Search).
I could have pre-tested snapshot builds but didn't have time for that
- and didn't expect 5.2 to be released without a Beta period, or I
would have made time for that.
I've seen quite some people struggling with the upgrade to Hibernate
ORM 5.2 as they think that hibernate-entitymanager was either
mistakenly not uploaded, or wasn't synched to Maven Central yet.
Could we restore the pom.xml for this artifact and have it redirect to
hibernate-orm ?
Doing so
I just noticed that the org.hibernate.Query interface was deprecated
in 5.2, with the suggestion to use org.hibernate.query.Query now.
That's ok, but it seems the "deprecation process" also forced some API
changes already on the deprecated interface which seem might have been
unintentional.
The
Thanks Gunnar, I'm wondering the same.
At the same time though, I would rather avoid the work of adapting the
SQM code to an ORM version which was not meant to be compatible with
it.
I'd rather wait with that until we base OGM on ORM6 and invest the
saved energy otherwise.
Mine is not a
Hello all,
we released Hibernate Search 5.6.0.Beta1, with many more improvements
for our Elasticsearch integration.
More details on our blog:
- http://in.relation.to/2016/05/24/ElasticsearchintegrationReachesBeta1/
Regards,
Sanne
___
hibernate-dev
Hi Max,
I just noticed that several popular open source projects, including
our "sister projects" WildFly and Vert.X have some kind of public
workspace to help people getting started to contribute:
http://www.eclipse.org/che/getting-started/
Would you know what it would take to include some of
One of the last pending tasks for the Elasticsearch work is to
mass-rename all packages from
org.hibernate.search.backend.elasticsearch.*
to
org.hibernate.search.elasticsearch.*
It's trivial to do, but before proceeding I'd like to make sure that
all your important work was merged. All ready
Awesome!
On 17 May 2016 at 16:44, Vlad Mihalcea wrote:
> Congrats!
>
> On Tue, May 17, 2016 at 4:52 PM, Davide D'Alto wrote:
>
>> Hibernate OGM 5.0.0.Final is out!
>>
>> Compared to the 4.2.Final, this release is aligned with Hibernate ORM
>> 5 and
at.
>
> 2016-05-10 16:21 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>
>> Hi all,
>> thanks for the logs.
>>
>> yes like Emmanuel suggested please don't make me a bottleneck by
>> assigning me OGM reviews
>>
>> OGM release:
>>
Hi all,
thanks for the logs.
yes like Emmanuel suggested please don't make me a bottleneck by
assigning me OGM reviews
OGM release:
Yes please make it happen :)
All tasks seem "ready for launch" on JIRA since last week. I hope
someone could copy the updated "quickstart" to the website, I've not
Remember the licensing terms. You can not distribute those drivers.
On Sat, 7 May 2016, 14:30 Vlad Mihalcea, wrote:
> Hi,
>
> I added those for testing, but now I realized that these could be missing
> from Jenkins.
> I'll add a Gradle condition to include the
starting page.
I'm assuming you took that link from some of our documentation/README,
as it used to be a good starting URL.
Happy to update the link to something better, if you have
suggestions.. I couldn't find a better alternative :-/
Thanks,
Sanne
>
> 2016-05-04 12:03 GMT+02:00 Sa
On 4 May 2016 at 10:56, Gunnar Morling wrote:
> Hi there,
>
> This is still an issue: when not being logged, an error instead of the
> activity dashboard is shown in JIRA.
I don't see such an error. Are you maybe looking at an URL which isn't
the typical welcome page?
wrote:
>
>
> On 04/18/2016 11:32 AM, Sanne Grinovero wrote:
>>
>> I think there was some confusion in this thread, probably it wasn't
>> clear that WildFly 10 already does inject automatically OGM, and that
>> ship sailed so we have to keep in mind what Jipijapa
I'm wondering why the Elasticsearch client for Hibernate Search is
using Gson, and not Jackson as JSON codec?
Especially as we already have Jackson as a dependency for both Search
(via Avro), OGM (via Couchbase), and it's also used within WildFly and
Camel, we might need to change this.
Sorry if
Hi Vlad,
there are several components which can safely use static fields, of
course as you say only if their state is not affected by which
SessionFactory is using them.
So I would agree on treating those with care: it should always be a
warning sign during code reviews and warrant an in-depth
Thanks Vlad, good idea!
On 27 April 2016 at 11:33, Vlad Mihalcea wrote:
> Hi,
>
> I wanted to ask everyone to let me know if you'd like to include any
> resource in the Community newsletter.
> If you stumble on a blog post, forum or StackOverflow question, that you
>
I can't mention Service w/o getting your attention :)
On 27 April 2016 at 13:34, Hardy Ferentschik wrote:
> Hi,
>
>> Yet it is a good idea nowadays to have LuceneWorkSerializer extend
>> Service, as we dropped that level of flexibility. This implies that
>> there's a single
On 27 April 2016 at 11:35, Gunnar Morling <gun...@hibernate.org> wrote:
> Hey Sanne,
>
> great write-up!
>
> 2016-04-27 0:04 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>>
>> The "Service" and "ServiceManager" concepts in
On 27 April 2016 at 10:33, Davide D'Alto wrote:
> This is an interesting sum up.
> Shouldn't we keep these thoughts in a separate document for developer?
>
> Together with some higher level diagrams of the architecture, maybe.
I indeed wrote it as you expressed need for an
The "Service" and "ServiceManager" concepts in Hibernate Search have a
specific meaning which is often misunderstood and/or abused, causing
trouble.
They also changed over time: victim of two major refactorings which
evolved the purpose and stretching its intent
So I'll change the definition
Hello all,
a maintenance release of our latest stable branch, version 5.5.3.Final
of Hibernate Search is now available, and is the suggested stable
version for everyone to use.
More details about the improvements can be found on our blog:
-
)
Just pointing this out as there was mention of "clean room" design.
>
> On Mon, Apr 25, 2016 at 9:52 AM Sanne Grinovero <sa...@hibernate.org> wrote:
>>
>> N.B. that chancing the exception types thrown by our native methods is
>> an API change in my opin
axException - we could just make QuerySyntaxException
> extend from IllegalArgumentException rather than Hibernate's
> HibernateException hierarchy.
>
> I think the bottom line is that having Session and EntityManager split
> before caused all kinds of difficult-to-debug comple
On 24 April 2016 at 19:00, Gunnar Morling <gun...@hibernate.org> wrote:
>
>
> 2016-04-22 12:55 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>>
>> On 21 April 2016 at 18:35, Gunnar Morling <gun...@hibernate.org> wrote:
>> > Hi,
>> >
>&
Gunnar's words seem wise to me: users will need to have the JPA API on
classpath anyway, so I don't see why we should have - and maintain -
strategies for different kind of exceptions.
This might have been useful in the past, but looking forward?
If the reasoning is that Hibernate - having more
author some
> content.
>
>
> On Fri, Apr 22, 2016 at 5:30 AM Sanne Grinovero <sa...@hibernate.org>
> wrote:
>
>> There's a middle-ground strategy which might be cool to try.
>>
>> Go here:
>> -
>> https://github.com/hibernate/hibernate.org/edit/pr
On 21 April 2016 at 18:35, Gunnar Morling wrote:
> Hi,
>
> As IndexShardingStrategy is deprecated, I thought I'd use
> ShardIdentifierProvider and friends in new code I write. It's not clear to
> me though, how it's meant to be used.
>
> Some questions:
>
> * Is it correct
There's a middle-ground strategy which might be cool to try.
Go here:
- https://github.com/hibernate/hibernate.org/edit/production/orm/roadmap.adoc
edit the doc within the browser, confirm the changes with a brief
commit message and CI should pick it up, then publish within 5
minutes.
I just
too.. if you happen to want
to fix one, we can of course change the fixVersion back.
Thanks,
Sanne
On 18 April 2016 at 19:08, Sanne Grinovero <sa...@hibernate.org> wrote:
> Hi,
> thanks for starting this discussion: agreed on the need to release
> something soon!
>
> One wo
us to lay the grounds for "index families" as we'll learn what
> needs to be done for different settings per cluster etc.
Exactly.
But also I'd move the option of Lucene embedded + ES to 5.7. Not to
say that we shouldn't explore these, just not considering them
blockers.
Thanks,
San
In the context of implementing Elasticsearch support for Hibernate
Search, there's a recurring need to transform the domain model to the
"Document" representation using a strategy which depends on the
storage choice, i.e. Lucene vs Elasticsearch.
For example Guillaume working on HSEARCH-2067
Hi,
thanks for starting this discussion: agreed on the need to release
something soon!
One word of caution though: it looks like media are picking up on this
work with interest so I expect a good amount of people to try the
first "preview" out; yet the expectations will probably be higher than
I think there was some confusion in this thread, probably it wasn't
clear that WildFly 10 already does inject automatically OGM, and that
ship sailed so we have to keep in mind what Jipijapa is going to do by
default:
The current state in WildFly 10's deployers is very simple: if it
"sees" that
This question came up again on github; seems Gunnar, Davide and myself
would agree on preferring a little more flexibility on the no-orm
projects than ORM's guidelines:
-
https://github.com/hibernate/hibernate-search/pull/1064#issuecomment-211320931
This flexibility would be a perk for
On 17 April 2016 at 19:43, Vlad Mihalcea wrote:
> Hi,
>
> Thanks for the update. I'm going to integrate it next week after the
> Session->EntityFactory merge.
Best to double-check with Steve, but I believe updates to the user
guide might not need to wait for his
integrations (which is
> expected, it's an SPI) not users
>
>
> On Fri, Apr 15, 2016, 9:46 AM Sanne Grinovero <sa...@hibernate.org> wrote:
>>
>> Do you have a practical need for SharedSessionContract and
>> SharedSessionContractImplementor to exist within the
y
>>> contract too, but the source (Session/StatelessSession via QueryProducer)
>>> would not necessarily need to implement EntityManager.
>>>
>>>
>>> I think the QueryProducer route is probably the best option in terms of
>>> allowing the cons
eep you informed. As for the JIRA
>> account, here's the mine :
>> mincon...@gmail.com
>>
>> Cheers,
>> Mincong
>>
>>
>> On Fri, Apr 8, 2016 at 2:35 PM, Sanne Grinovero <sa...@hibernate.org>
>> wrote:
>>>
>>> Hi Mincong,
&
h this consolidation then I can not
>>>> rush it as much
>>>>
>>>> On Wed, Apr 6, 2016 at 4:48 PM Chris Cranford <cranc...@gmail.com> wrote:
>>>>
>>>>> I have to concur with Sanne, a hold on master pushes until this merge of
>&
601 - 700 of 2025 matches
Mail list logo