Catalog facts for agent memory#330
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
| .help("Environment the catalog belongs to") | ||
| .action(ArgAction::Set); | ||
|
|
||
| Command::new("facts") |
There was a problem hiding this comment.
facts has a specific meaning when it comes to data analytics so I would presume this command name is confusing to both humans(like me :D) and ai. Perhaps a better name is meta or ai-context
There was a problem hiding this comment.
Yeah maybe we want to disambiguate this from fact tables in a data warehousing context. I'll take a quick look at this.
`facts` collides with fact tables in dimensional modeling — confusing right where this lives, on a data catalog. Rename the CLI surface and tower-cmd internals to `knowledge`. The generated tower-api client still calls them `facts` since the backend is unchanged.
This PR integrates catalog facts from the API into the CLI to give agents memory about data stored in a catalog. This is just an experimental feature to see how it improves (or not) workloads.
Example