Where Does Great Expectations Store Suites and Results?
Great Expectations keeps suites, checkpoints and validation results in a project folder. Classic and GX Core layouts plus the Windows caveat.
Last updated
Great Expectations stores project state inside the project, not in your home. The classic layout is a great_expectations/ folder with the main yml, expectations, checkpoints, plugins and an uncommitted directory for secrets and outputs. GX Core 1.x uses the same idea under a gx/ folder created by get_context().
Windows is the odd platform out: the open source Python package does not support it, so local runs happen on macOS, Linux or WSL. GX Cloud moves storage server side entirely, which makes these folders local only concerns. Checkpoints reference suites by name, so renaming files without updating references breaks scheduled validations.
Where Great Expectations stores this, by platform
<project>/great_expectations
great_expectations.yml plus expectations/, checkpoints/, plugins/ and uncommitted/ (credentials, validations, data docs). GX 1.x instead creates gx/ via gx.get_context(). Keep uncommitted/ out of version control.
<project>/great_expectations
Same project relative layout as Mac. Stores backends can redirect metadata to databases or cloud, in which case these folders hold config while results live remotely.
Frequently asked questions
What belongs in git?
Commit great_expectations.yml, expectations, checkpoints and plugins. Leave uncommitted/ out: it holds credentials, local validation results and generated Data Docs that should never reach the repo.
Where do validation results go?
Into uncommitted/validations with Data Docs in uncommitted/data_docs by default. Point stores at a database or cloud bucket when local files stop scaling.
Notice an outdated path? Let us know.