Thanks, Michael. In my case, it's SDN 3.2.1 (will be migrating to 3.3 shortly) w/ Neo4j 2.1.6. Still trying to figure out how/where the issue came up as the only time outside of a POJO I create a rel is through a couple MERGE statements, but those are infrequent. In the case of those MERGEs, is there anything special that needs to be added as a property? Does this matter if the rel is to have no properties associated with it (which is the case for the majority of the rels in this graph)?
On Mon, May 11, 2015 at 1:55 PM, Michael Hunger < [email protected]> wrote: > Prior to 2.0 it only had index and sub-ref based TypeRepresentation which > was changed in 2.0 as we added a label based TRS. > That one uses simple class names, there is a configuration override that > you can use to retain the old behavior. > > If you added the relationships manually, it doesn't have a _type_ property > and it is not added to the appropriate index. > > you can call neo4jTemplate.postEntityCreation(node, Type.class) for the > manually created nodes and rels. > > Alternatively you can migrate your database to 2.1 and update SDN to > 3.3.0.RELEASE > > See my announcement blog post from back then: > http://neo4j.com/blog/spring-data-neo4j-progress-update-sdn-3-neo4j-2/ > > Alternatively you could look into SDN4 which is due soon as RC1 and then > GA in June: > http://neo4j.com/blog/announcing-spring-data-neo4j-4-0/ > > Cheers, Michael > > > > Am 03.12.2014 um 13:16 schrieb Mamta Thakur <[email protected]>: > > Hi, > > We are using neo4j 2.0.3 and SDN (3.1.0). > > We are getting this error when trying to execute this cypher with > repository. > @Query("MATCH (n:Member)-[:MY_FB]->p WHERE n.id = {0} RETURN p;") > -> > org.neo4j.graphdb.NotFoundException: RELATIONSHIP[7141600] has no property > with propertyKey="__type__". > > If I look for this relationship id "7141600" This is a relationship of p > -[r:INVITE]-x. > Our SDN save(repository.save()) hangs up quiet often so Invite relations > were inserted using native java code like this. > > private static final RelationshipType INVITED = DynamicRelationshipType > .withName("INVITED"); > relationship = initiator.createRelationshipTo(recipient, INVITED); > > Can someone please guide me to the fix. I don't know why is this _type_ > required anyway. Earlier(prior upgrade 1.9.2) we used to have fully > qualified class names as _type_ for NODEs, now I see just classname. Which > is not consistent in itself. > > > Regards, > Mamta. > > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Neo4j" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/neo4j/6ySrNrmLAvs/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
