Hibernate OGM 5.4.0.Alpha1 release
by Davide D'Alto
We’re happy to announce the release of Hibernate OGM 5.4.0.Alpha1.
Hibernate OGM is now compatible with Hibernate ORM 5.3 (still a
candidate release) and JPA 2.2. We support Infinipan 9.2 and JBoss
modules are now available as WildFly feature packs.
You can run server-side JavaScript on MongoDB or Java code in
Infinispan Embedded as if they were stored procedures using the JPA
approach.
When using the Infinispan Remote dialect, it is now possible to
configure new caches using the @CacheConfiguration annotation.
You can find all the details in the blog post:
http://in.relation.to/2018/04/17/hibernate-ogm-5-4-Alpha1-released/
Thanks,
Davide
6 years
Hibernate Search 5.10.0.Beta2
by Yoann Rodiere
Hi,
We just published 5.10.0.Beta2, the second beta release for the 5.10
branch. This release mainly includes an upgrade to WildFly 12 for the JBoss
modules, but it also adds a few bugfixes and improvements.
Check out our blog for more information about this release:
http://in.relation.to/2018/04/13/hibernate-search-5-10-0-Beta2/
--
Yoann Rodiere
yoann(a)hibernate.org / yrodiere(a)redhat.com
Software Engineer
Hibernate NoORM team
6 years
HHH-8944 - ColumnTransformer handling is too aggressive in qualifying "column names"
by Steve Ebersole
Anyone know of places where we document ColumnTransformer read-fragment
handling as qualifying columns other than the column the transformer is
attached to? E.g., consider:
@Column( name="dob" )
@ColumnTransformer( read="SYSDATE - dob / 365", ... )
public int getAge() { ... }
Currently, Hibernate will try to qualify both "SYSDATE" and "dob" with
table alias. The simple fix is to simply limit the qualification to the
column that the transformer is attached to ("dob"). Just want to make sure
that we do not document anywhere that multiple column references will all
be replaced. E.g. (contrived):
@Column( name="dob" )
@ColumnTransformer( read="(SYSDATE - dob / 365) + offset", ... )
public int getAge() { ... }
The question is whether both "dob" and "offset" columns will get
qualified. Allowing this is much more involved, requiring that we somehow
allow configuration of all the referenced columns that should be qualified
(which has its own set of difficulties when it comes to multi-table
structures).
I propose the simple solution, unless there are any objections
6 years
JDK 11 Early Access build 8 available
by Rory O'Donnell
Hi Sanne,
**JDK 11 EA build 8, *****under both the GPL and Oracle EA licenses, is
now available at **http://jdk.java.net/11**. **
*
* Newly approved Schedule, status & features
o http://openjdk.java.net/projects/jdk/11/
* Release Notes:
o http://jdk.java.net/11/release-notes
* Summary of changes
o https://download.java.net/java/early_access/jdk11/8/jdk-11+8.html
*Notable changes in JDK 11 EA builds since last email:*
* Build 8:
o If you have a library that uses the Selector API heavily then
now would be a good time to test it out. [1]
* Build 7
o The VM option "-XX:+AggressiveOpts" is deprecated in JDK 11 and
will be removed in a future release.
* Build 6:
o JDK-8193033 : remove terminally deprecated
sun.misc.Unsafe.defineClass. Users should use the public
replacement `java.lang.invoke.MethodHandles.Lookup.defineClass`
which was added in Java SE 9. [2]
**
*SURVEY: The HotSpot Serviceability Agent (SA) *[3]
* If you have used, or have (support) processes that utilize the
Serviceability Agent or related APIs, then we would definitely
appreciate if you would complete this survey:
https://www.surveymonkey.com/r/CF3MYDL
Regards,
Rory
[1] http://mail.openjdk.java.net/pipermail/nio-dev/2018-April/004964.html
[2]
https://docs.oracle.com/javase/9/docs/api/java/lang/invoke/MethodHandles....
[3] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-April/001052.html
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
6 years
HipChat / JIRA / Atlassian account(s) login
by Sanne Grinovero
Many of us reported problems with HipChat today / recently.
It seems Atlassian has merged accounts of HipChat and various other
services, like our
JIRA.
I would suggest to reset your password and consider that your new
password will apply to all (most?) of your Atlassian accounts:
I'm not sure what they did exactly, but after resetting my password on
JIRA a couple of days back, now to login on HipChat I had to use that
same password.
HTH
6 years
[HSEARCH][V6-POC] Bug tracking for the Search 6 POC
by Yoann Rodiere
Hello,
With the Search 6 POC getting closer and closer to something we can merge,
and thus more and more complex, we are starting to see quite a lot of TODOs
piling up.
I've been tracking most of them in a Google Doc
<https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM...>
so far, and it's fine for big architectural topics, but for small things
it's clearly inadequate.
What would you all think if we started to use the main Hibernate Search
project to track the small TODOs we have in the Search 6 POC? We would
probably have to add some JIRA Components that only make sense in Search 6
("indexing", ...), but beyond that I don't think this would cause much
trouble.
The tickets would all be Tasks targeting version 6, and we could tag them
with a new "POC-6.0" component if you think it's necessary. Examples of
tasks would be:
- Native sorts in the Lucene Sort DSL extension
<https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM...>
- Native predicates in the Lucene Predicate DSL extension
<https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM...>
- Rework the Lucene DSL implementations to fail fast when parameter
conversion errors occur
<https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM...>
- Polish and test Stream indexing (add CompletableFuture returns in
particular)
- Decide wether to use absolute or relative object path in "nested"
search predicates
If this feels like too much garbage for the main bug tracker, we can create
a separate JIRA project instead. But then this will add to the trouble
we'll have to go through when merging (commits referring to tickets from
another project).
Sanne, all, WDYT?
--
Yoann Rodiere
yoann(a)hibernate.org / yrodiere(a)redhat.com
Software Engineer
Hibernate NoORM team
6 years
Jenkins Updates
by Davide D'Alto
Hi,
I've run some updates on CI.
Everything seems to work fine but keep that in mind if something weird happens.
Cheers,
Davide
6 years
[HV] Master is now 6.1, 6.0 is branched
by Guillaume Smet
Hi,
$SUBJECT says it all.
I set up the CI jobs so everything should be fine on this front.
Be careful to backport bug fixes to the 6.0 branch.
--
Guillaume
6 years
