Bug: Http query request failed

[danielmartincraig]

I have encountered an issue; I run neptune-for-graphql and I see that after finding all my nodes and edges via the Neptune Summary API, and after discovering the properties of the edges and nodes, I see error messages like the following begin to flow:

Http query request failed: Client network socket disconnected before secure TLS connection was established Trying with the AWS SDK

I am running the tool like so:

neptune-for-graphql --input-graphdb-schema-neptune-endpoint xxxx-xxx-xx.us-east-1.neptune.amazonaws.com:xxxx --output-aws-pipeline-cdk-neptune-IAM

I am using Neptune engine 1.2.1.0, with sigV4 enabled. My cluster instance is of type 'provisioned', it's of size db.r5.4xlarge.

[kenhuuu]

Just to clarify, are you saying that the utility isn't working after finding the nodes/edges and you are seeing those error messages, or are you saying that the utility does work but you are asking if you should be concerned about those error messages?

[danielmartincraig]

The utility is not working; it starts logging the error and it never finishes running and never puts anything in the output/ folder.

[danielmartincraig]

It just starts logging the error endlessly