跳至主要内容

Data crossstore between Mongo and JPA


Data crossstore between Mongo and JPA

Spring Data Mongo provides another attractive feature, when you mix to use Mongo and JPA in your projects, you can unite the models of Mongo and JPA.

Model

The Conference and Signup are still used as example models,Conference is JPA entity class and Signup is a Mongo Document.
@Entity
public class Conference {
 @Id
 @GeneratedValue(strategy = GenerationType.AUTO)
 @Column(name = "id")
 private Long id;

 
 @RelatedDocument
 private Signup signup;
}
The Signup Document is defined as the following.
@Document
public class Signup {

 @Id
 private String id;

}
@RelatedDocument annotation indicates the signup property of Conference is a reference of Signup Mongo Document. This annotation will be processed by a AspectJ aspect which provided in Spring Data Mongo.
You have to add some code fragments to Spring configuration.
<!-- Mongo cross-store aspect config -->
<bean
 class="org.springframework.data.mongodb.crossstore.MongoDocumentBacking"
 factory-method="aspectOf">
 <property name="changeSetPersister" ref="mongoChangeSetPersister" />
</bean>
 
<bean id="mongoChangeSetPersister"
 class="org.springframework.data.mongodb.crossstore.MongoChangeSetPersister">
 <property name="mongoTemplate" ref="mongoTemplate" />
 <property name="entityManagerFactory" ref="entityManagerFactory" />
</bean>
Firstly, this aspect will mark this property as @Transient and prevent JPA recognize it as a persistent property.
Then register a transaction synchronization to entity lifecycle events of the host JPA Entity( Conference ) to synchronize the@RelatedDocument data into Mongo Document.
We also use Junit @Before to initialize the data.
@Before
public void beforeTestCase() {
 log.debug("==================before test case=========================");
 conferenceRepository.save(newConference());
}
The newConference() method is use for create a new Conference object, we also create a new Singup as the value of signup property.
@Test
public void retrieveConference() {
 log.debug("==================enter retrieveConference=========================");

 assertTrue(null != id);

 Conference conf = em.find(Conference.class, id);

 log.debug("conf@@@" + conf);
 assertTrue(null != conf);
 assertTrue(null == conf.getSignup());
}
When you run this Test, pass!
Everything is OK?
Spring Data Mongo provides a LoggingEventListener to tracking the Mongo events.
<bean class="org.springframework.data.mongodb.core.mapping.event.LoggingEventListener" />
After you enable this listener, you should see the Mongo log info about saving Conference. But we run this Test again, we can not see it at all.
Add another line code in the first line of the test method.
em.clear();
Run the Test, failed.
No doubt the Signup was not stored in Mongo when saving Conference object.
As motioned before, the crosssotre synchronization is fired by the entity lifecycle events. If JPA event @PostPersist is not fired in a transaction, the Mongo event will not be fired.
@Before
// @Transactional(propagation = Propagation.REQUIRED)
public void beforeTestCase() {
 log.debug("==================before test case=========================");
 transactionTemplate = new TransactionTemplate(transactionManager);
 transactionTemplate.execute(new TransactionCallback<Void>() {

  @Override
  public Void doInTransaction(TransactionStatus status) {
  }
 }
}
Alternatively, we change the initial codes slightly, and use aTranscationTemplate to process the Conference saving action as an unit of work.
Run this test again, pass.

More ...

If possible store a Collection of data into Mongo like this,
@RelatedDocument
private List<Signup> signups;
Unfortunately, it does not work.
But you wrap the List into standalone Document like.
@Document
public class SignupInfo {

 @Id
 private String id;

 @DBRef
 private List<Signup> signups = new ArrayList<Signup>();
}
And change the relation to SignupInfo.
@RelatedDocument
private SignupInfo signupinfo;
But you have to save the Signup objects in Mongo firstly, because Spring Data Mongo does not support Cascade saving feature like JPA.
I have some wishes for the crossstore.
  1. Store reverse when store a Document.
Update to now, there is no way to do the work reverse. When you store a Mongo Document it does not support to store the related JPA entity into database.
2. Query cross different data storage. Obviously, it is impossible to execute query cross different stores.

Summary

Personally, I think the Mongo and JPA crossstore is only a toy, and the provided feature is too weak. I hope it can be improved in future, and provides seamless integration between different data stores as I expected.
标签：

评论

发表评论

此博客中的热门博文

AngularJS CakePHP Sample codes

Introduction This sample is a Blog application which has the same features with the official CakePHP Blog tutorial, the difference is AngularJS was used as frontend solution, and CakePHP was only use for building backend RESR API. Technologies AngularJS   is a popular JS framework in these days, brought by Google. In this example application, AngularJS and Bootstrap are used to implement the frontend pages. CakePHP   is one of the most popular PHP frameworks in the world. CakePHP is used as the backend REST API producer. MySQL   is used as the database in this sample application. A PHP runtime environment is also required, I was using   WAMP   under Windows system. Post links I assume you have some experience of PHP and CakePHP before, and know well about Apache server. Else you could read the official PHP introduction( php.net ) and browse the official CakePHP Blog tutorial to have basic knowledge about CakePHP. In these posts, I tried to follow the steps describ
2 条评论
阅读全文

JPA 2.1: Attribute Converter

JPA 2.1: Attribute Converter If you are using Hibernate, and want a customized type is supported in your Entity class, you could have to write a custom Hibernate Type. JPA 2.1 brings a new feature named attribute converter, which can help you convert your custom class type to JPA supported type. Create an Entity Reuse the   Post   entity class as example. @Entity @Table(name="POSTS") public class Post implements Serializable { private static final long serialVersionUID = 1L; @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name="ID") private Long id; @Column(name="TITLE") private String title; @Column(name="BODY") private String body; @Temporal(javax.persistence.TemporalType.DATE) @Column(name="CREATED") private Date created; @Column(name="TAGS") private List<String> tags=new ArrayList<>(); } Create an attribute convert
发表评论
阅读全文

Auditing with Hibernate Envers

Auditing with Hibernate Envers The approaches provided in JPA lifecyle hook and Spring Data auditing only track the creation and last modification info of an Entity, but all the modification history are not tracked. Hibernate Envers fills the blank table. Since Hibernate 3.5, Envers is part of Hibernate core project. Configuration Configure Hibernate Envers in your project is very simple, just need to add   hibernate-envers   as project dependency. <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-envers</artifactId> </dependency> Done. No need extra Event listeners configuration as the early version. Basic Usage Hibernate Envers provides a simple   @Audited   annotation, you can place it on an Entity class or property of an Entity. @Audited private String description; If   @Audited   annotation is placed on a property, this property can be tracked. @Entity @Audited public class Signup implements Serializa
发表评论
阅读全文