Component
API Server / GraphQL
Infrahub version
1.7.x
Current Behavior
if an Infrahub instance does not include any "owner" metadata for relationships or attributes, then cypher queries that look for these metadata can raise errors about the relationship not existing on the database
the error can be safely ignored, but it will be raised every time an object is retrieved from the database
the error looks something like this
Received notification from DBMS server: <GqlStatusObject gql_status='01N51', status_description='warn: relationship type does not exist. The relationship type `HAS_OWNER` does not exist in database `neo4j`. Verify that the spelling is correct.', position=<SummaryInputPosition line=30, column=24, offset=1325>, raw_classification='UNRECOGNIZED', classification=<NotificationClassification.UNRECOGNIZED: 'UNRECOGNIZED'>, raw_severity='WARNING', severity=<NotificationSeverity.WARNING: 'WARNING'>, diagnostic_record={'_classification': 'UNRECOGNIZED', '_severity': 'WARNING', '_position': {'offset': 1325, 'line': 30, 'column': 24}, 'OPERATION': '', 'OPERATION_CODE': '0', 'CURRENT_SCHEMA': '/'}> for query: ...
Expected Behavior
We should suppress this error for optional relationship types, such as HAS_OWNER and HAS_SOURCE
Steps to Reproduce
the error might only appear when the neo4j database is clustered
Additional Information
the example error message from the user report is raised when the RelationshipGetPeerQuery is executed
Component
API Server / GraphQL
Infrahub version
1.7.x
Current Behavior
if an Infrahub instance does not include any "owner" metadata for relationships or attributes, then cypher queries that look for these metadata can raise errors about the relationship not existing on the database
the error can be safely ignored, but it will be raised every time an object is retrieved from the database
the error looks something like this
Expected Behavior
We should suppress this error for optional relationship types, such as HAS_OWNER and HAS_SOURCE
Steps to Reproduce
the error might only appear when the neo4j database is clustered
Additional Information
the example error message from the user report is raised when the
RelationshipGetPeerQueryis executed