We’re happy to announce the release of: Hibernate OGM 5.3 CR1
Components upgrade
-
Hibernate ORM version is upgraded to 5.2
-
Hibernate Search version is upgraded to 5.9
Infinispan embedded sequences and id generation improvements
When using @SequenceGenerator, Hibernate OGM will create Clustered Counter at start up.
This change will lead to better performance because it doesn’t have to check if the Clustered Counter already exists each time.
See Clustered Counters.
When these are used for id generation their names now also contain the table name and not only the column name. Given the following example:
@Entity
@Table(name = "Ruby")
private static class Ruby {
@Id
@GeneratedValue(strategy = GenerationType.TABLE, generator = "gen")
@TableGenerator(name = "gen", table = "Ruby_generators", initialValue = 0, pkColumnValue = "ruby_sequence")
Long id;
}The name of the Clustered Counter will be Ruby_generators.ruby_sequence instead of only ruby_sequence.
This is to avoid collision when different @TableGenerator are defined with different table attribute but the same pkColumn values.
| Keep in mind that if you already have some generators Hibernate OGM won’t recognize them. Make sure to update the model with a different initialValue higher than the one you have currently reached. |
Release Notes
All the changes are described in the https://hibernate.atlassian.net/issues/?jql=project=10160+AND+fixVersion=31626
Where can I get it?
You can include in your project the dialect of your choice using this Maven coordinates:
Alternatively, you can download archives containing all the binaries, source code and documentation from Sourceforge.
If you are interested about available versions, you can check the official Hibernate OGM download page.
How can I get in touch?
You can find us through the following channels:
-
Stack Overflow: we monitor the tag hibernate-ogm
-
Zulip: Hibernate OGM Zulip stream
We are looking forward to hearing your feedback!
