You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Neptune connector does not recognize "~". When having properties with the same name (except on has a ~, the query returns wrong information and seems to return values from the 1st of the two properties found (though this hasn't been validated).
To Reproduce
Steps to reproduce the behavior:
Create database with multiple properties of the same name name except use a "~" as a prefix for one of the properties
example: "~id" & "id"
describe the data
notice one sql result column "~id" should be empty
Expected behavior
Expect to query the Datacatlog and have different values in the "~id" and "id" columns
Screenshots / Exceptions / Errors
No exceptions in the logs
Connector Details (please complete the following information):
SAR is not permitted, so this was manually installed with the help of AWS team
Additional context
The text was updated successfully, but these errors were encountered:
I discussed with Bryan. The tildes are used for bulk-load only. Once that data lands in Neptune, it does not have the tilde. For example, the ~id and ~label columns from a node CSV file just result in the node ID and node label after being ingested.
We did observe that Bryan has nodes with a "property" named "id". The connector assumes the "id" column in a table always refers to the node ID. It does not allow for a property also to be named "id". The issue is to get past this limitation.
Describe the bug
The Neptune connector does not recognize "~". When having properties with the same name (except on has a ~, the query returns wrong information and seems to return values from the 1st of the two properties found (though this hasn't been validated).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect to query the Datacatlog and have different values in the "~id" and "id" columns
Screenshots / Exceptions / Errors
No exceptions in the logs
Connector Details (please complete the following information):
SAR is not permitted, so this was manually installed with the help of AWS team
Additional context
The text was updated successfully, but these errors were encountered: