[
https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668680#comment-16668680
]
Ilya Kasnacheev commented on IGNITE-9893:
-----------------------------------------
[~scottmf]
Does it make sense to include hibernate 5.2 when 5.3 is already out?
I ask this because we can only ship hibernate 5.2 as a part of Ignite 2.8 now,
and it will not be out until 2019. Will not hibernate 5.2 irrelevant by then?
Everybody will be wanting 5.3.
I have checked your code with 5.3 and it seems there are massive SPI changes.
Maybe you could fix it to support 5.3? Is support of 5.3 even feasible? If not,
we could reconsider 5.2.
Your patch seems to be somewhat behind master, by the way - there are
compilation errors.
> add hibernate-5.2 module
> ------------------------
>
> Key: IGNITE-9893
> URL: https://issues.apache.org/jira/browse/IGNITE-9893
> Project: Ignite
> Issue Type: New Feature
> Components: hibernate
> Reporter: Scott Feldstein
> Priority: Major
>
> hi,
> I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD.
> commit:
> [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9]
> All tests pass except
> CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover
> from the hibernate-5.1 implementation. There is a bug already associated with
> the failure:
> https://issues.apache.org/jira/browse/IGNITE-1757
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
