aws / aws/graph-explorer

[Bug] RDF node/edge totals do not match expected totals in Neptune

Open
#485 0 comments 0 reactions 0 assignees View on GitHub
sparql usability
Dominant language
TypeScript
Stars
481
Forks
108
Avg merge
6d 8h
Merged PRs (30d)
5

Description

## Description

When using Neptune and the summary API, the total node and edge counts for a RDF data set in Graph Explorer are inconsistent with what I would expect.

Using the Airports sample data here are the counts for RDF

Using the Airports sample data here are the counts for RDF

And here are the counts for Gremlin

the counts for Gremlin

If I disable the summary API calls in the code I see numbers that much more closely match my expectations.

If I disable the summary API calls in the code I see numbers that much more closely match my expectations.

## Environment

- OS: macOS 14.5
- Browser: Arc
- Graph Explorer Version: 1.8
- Graph Database & Version: Amazon Neptune 1.3.2

## Steps to Reproduce

1. Create blank Neptune database
2. Seed with Airports sample data for both property graph and RDF
3. Create notebook for Neptune database
4. Open Graph Explorer
5. Observe node and edge count differences between property graph and RDF

## Expected Behavior

The node and edge counts should be consistent

---

> [!IMPORTANT]
> If you are interested in working on this issue or have submitted
> a pull request, please leave a comment.

> [!TIP]
> Please use a 👍 reaction to provide a +1/vote.
>
> This helps the community and maintainers prioritize this request.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.