Databases
StackOverflow2013
Postsdbo
POFrom JPA to NOSQL
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFrom JPA to NOSQL
    primarykey
    data
    text
    <p><br> I am trying to add a NOSQL data into my JPA-based application, following <a href="http://static.springsource.org/spring-data/data-graph/snapshot-site/reference/html/#cross-store" rel="nofollow">this tutorial</a>.<br> The entity I want to add, was befored modeled without NOSQL in this way: </p> <p><strong>Triple.java</strong></p> <pre><code>@Entity @IdClass(ConceptPk.class) @Table(name = "triple") public class TripleDBModel { protected List&lt;Annotation&gt; annotations; public Concept conceptUriSubject; public Concept conceptUriObject; public Concept conceptUriPredicate; @ManyToMany( cascade={CascadeType.ALL }, fetch=FetchType.LAZY ) @JoinTable(name = "triple_has_annotation", joinColumns={@JoinColumn(name="uri_concept_subject"), @JoinColumn(name="uri_concept_object"), @JoinColumn(name="uri_concept_predicate") }, inverseJoinColumns=@JoinColumn(name="annotation_id") ) public List&lt;Annotation&gt; getAnnotations() { return annotations; } public void setAnnotations(List&lt;Annotation&gt; annotations) { this.annotations = annotations; } </code></pre> <p><strong>ConceptPk.java</strong> </p> <pre><code>@Embeddable public class ConceptPk implements java.io.Serializable { private static final long serialVersionUID = 1L; public Concept conceptUriSubject; public Concept conceptUriObject; public Concept conceptUriPredicate; @Id @ManyToOne(cascade=CascadeType.MERGE) @JoinColumn(name="uri_concept_subject") public Concept getConceptUriSubject() { return conceptUriSubject; } public void setConceptUriSubject(Concept conceptUriSubject) { this.conceptUriSubject = conceptUriSubject; } </code></pre> <p>I am omiting repetitions, but the 3 <code>Concept</code>s are part of the primary key, of the @Id.<br> Adapting this entity to NOSQL: </p> <pre><code>@Entity @IdClass(ConceptPk.class) @Table(name = "triple") @NodeEntity(partial = true) public class TripleDBModel { //Fields referring other entities shouldn't be initialized protected List&lt;Annotation&gt; annotations; //public Concept conceptUriSubject; //public Concept conceptUriObject; //public Concept conceptUriPredicate; @RelatedTo(type = "conceptUriSubject", elementClass = Concept.class) Set&lt;Concept&gt; conceptUriSubject; </code></pre> <p>Now the question, which actually are two questions: </p> <p>A) <code>@RelatedTo(type = "conceptUriSubject", elementClass = Concept.class)</code> gives me error on Eclipse, and advises me to add a cast, but this doesn't solve the error. I don't know if I must an annotation or any other additional thing to <code>Class.java</code> </p> <p>B) As I have specified, the primery key is composed by 3 concepts, and <code>ConceptPK.java</code> is required. JPA modelling is ok, but I don't know how to do the same in NOSQL</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBlanca Hdez
    1. USBlanca Hdez
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POFrom JPA to NOSQL
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POFrom JPA to NOSQL
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POFrom JPA to NOSQL
      1. USfregos23
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload