Native Schema API Support
- Dominant language
- TypeScript
- Stars
- 481
- Forks
- 108
- Avg merge
- 6d 8h
- Merged PRs (30d)
- 5
Description
> **Initiative** — a body of work too big for one release, expressing a vision. Never-tracked container; the board tracks its children. No roadmap parent (a schema/connectivity roadmap item may emerge later).
## Vision
Neptune DB has released a **Schema API** that returns much of the data our schema-sync process derives today by issuing SPARQL/Gremlin queries; Neptune Analytics already ships an equivalent. This initiative adopts those native Schema APIs as a first-class source for schema discovery — faster, more reliable, and less query-dependent than the current sync path — while keeping generic (non-Neptune) databases working through the existing mechanism.
## Scoping
Not yet charted. See the kickoff child (`wayfinder:kickoff`) for the paths to explore and potential blockers. Run `/wayfinder` against this initiative to create the map, at which point the kickoff closes and the map owns the scoping route.
## For the current release
Only the **research + scoping** (the kickoff → Wayfinder map) is targeted for v3.3. Implementation lands in a later release.
> [!IMPORTANT]
> Internal only — this issue is maintained by the core team and is not accepting external contributions.
Contributor guide
Research direction
Start by reviewing the kickoff child marked `wayfinder:kickoff` and the existing schema-sync process described in this initiative. Run `/wayfinder` against issue #2008 to create the map, identify paths and blockers, and define the scope; completion means research and scoping are documented, not implementation of the native Schema API support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- api, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100