167000 OGM debug messages (..Unable to find a matching @RelationshipEntity..) from parsing just 6 classes

Drivers & Stacks Spring Data Neo4j & Neo4j-OGM
1

The debug output from OGM parsing 6 simple classes is yielding ~167000 instances of debug messages similar to…

17:30:21.925 [main] DEBUG org.neo4j.ogm.context.GraphEntityMapper - Unable to find a matching @RelationshipEntity for (56992)-[PART_OF]->(56988)

Coupled with the fact that …

  • No @RelationshipEntity is declared
  • the parsing is taking some time (~30 seconds)
  • the majority of the 167000 debug messages seem to be a repetition of the following block…

Unable to find a matching @RelationshipEntity for (56990)-[PART_OF]->(56988)

Unable to find a matching @RelationshipEntity for (56992)-[INSTANCE_OF]->(56990)

Unable to find a matching @RelationshipEntity for (56992)-[REFERS_TO]->(57035)

Unable to find a matching @RelationshipEntity for (56994)-[REFERS_TO]->(57035)

Unable to find a matching @RelationshipEntity for (56994)-[INSTANCE_OF]->(56990)

Unable to find a matching @RelationshipEntity for (56993)-[INSTANCE_OF]->(56990)

Unable to find a matching @RelationshipEntity for (56993)-[PART_OF]->(56988)

Unable to find a matching @RelationshipEntity for (56995)-[PART_OF]->(56988)

Unable to find a matching @RelationshipEntity for (56995)-[REFERS_TO]->(57036)

Unable to find a matching @RelationshipEntity for (56994)-[REFERS_TO]->(57036)

Unable to find a matching @RelationshipEntity for (56994)-[PART_OF]->(56988)

Unable to find a matching @RelationshipEntity for (57055)-[PART_OF]->(56988)

Unable to find a matching @RelationshipEntity for (57055)-[REFERS_TO]->(57037)

leads me to think that perhaps I have made some kind of mistake with the annotation – but I cannot see where the problem is.

Hopefuly someone more experienced with Neo4j OGM can spot my stupid mistake or perhaps this is normal OGM behaviour?? - doesn't feel like it.

Thanks in advance for any bright ideas
Rod

2

In outline the classes are…

@NodeEntity

public abstract class CheckEntity implements SynchCheckEntities{

@Id

@GeneratedValue(strategy = UuidStrategy. class )

protected String givenIdentity;

…

}

3

@NodeEntity(label="CheckParent")

public abstract class AbstractCheck extends CheckEntity{

protected String description = null ;

protected String checkCode = null ;

protected String category = null ;

protected String severity = null ;

@Relationship(type="PART_OF", direction=Relationship. UNDIRECTED )

protected Set associatedGroup = new HashSet();

@Relationship(type="REFERS_TO", direction=Relationship. UNDIRECTED )

protected Set associatedHyperlinks = new HashSet();

…

}

4

public class CheckGroup extends CheckEntity{

private String title = null ;

private String findingBaseColour = null ;

private String identityPrefix = null ;

private String findingBaseText = null ;

…

}

public class Check extends AbstractCheck {

protected String specifiedIdentity = null ;

@Relationship(type="INSTANCE_OF", direction=Relationship. OUTGOING )

private CheckTemplate associatedTemplate = null ;

…

}

public class CheckTemplate extends AbstractCheck{

private String title= null ;

…

}

public class CheckOrientedHyperlinks extends CheckEntity{

@Convert(URLConverter. class )

private URL refersTo;

….

}

5

This is indeed normal behaviour for the DEBUG level.
I can understand that this is annoying given the fact that you see so much repetition of it. But this is due to the fact that Neo4j-OGM logs this message for every relationship it wants to map from the graph to the entities.

6

Hi,

I understand that logging at DEBUG level will generate a high volume of messages. My query (probably badly explained - apologies) was really why was this happening for @RelationshipEntity when none of the parsed classes has that annotation. It just seemed a bit odd and made me wonder if I had inadvertently screwed up the annotations within my classes.

7

There is some logic that checks if a @RelationshipEntity exists for the relationship coming back from the server. This means that for every relationship, you will get this log entry.
Nothing to worry about, but I can understand that this is annoying.