How hrbrmstr/sergeant works
sergeant is an R client for querying and managing Apache Drill, with a DBI driver and dplyr interface over Drill’s REST API. The main workflow is to connect, build or submit a query, and receive results for use in R. The README also documents administrative and informational APIs, schema and storage inspection, custom SQL-function mappings, CTAS generation, and Docker helpers. Source excerpts were unavailable, so relationships below rely on README documentation; uncertain internal call wiring is omitted.
Main entry points: rest-api.r REST client · query.r Query API · dplyr.r dplyr interface · dbi.r DBI driver
Components 14
R interfaces
- dplyr interface
R/dplyr.r - DBI driver
R/dbi.r
Query workflow
- Query API
R/query.r - Result conversion
R/query.r - REST client
R/rest-api.r - SQL mappings
R/custom.r
Drill operations
- Schema inspection
R/query.r - Storage inspection
R/query.r - Server controls
R/rest-api.r - Query profiles
R/rest-api.r
Convenience helpers
- CTAS generation
R/ctas-profile.R - Docker helpers
R/drill-docker.R
Other components
- R user
- Apache Drill
Connections 20
- R user → dplyr interface: connects and queries
- dplyr interface → DBI driver: uses driver
- DBI driver → REST client: uses REST
- REST client → Apache Drill: submits requests
- R user → Query API: submits SQL
- Query API → REST client: sends query
- Query API → Result conversion: converts results
- Result conversion → R user: returns data
- R user → SQL mappings: uses mappings
- R user → CTAS generation: generates statement
- R user → Schema inspection: inspects schemas
- Schema inspection → REST client: requests metadata
- R user → Storage inspection: inspects storage
- Storage inspection → REST client: requests metadata
- R user → Server controls: manages server
- Server controls → REST client: sends controls
- R user → Query profiles: inspects profiles
- Query profiles → REST client: requests profiles
- R user → Docker helpers: manages Docker
- Docker helpers → Apache Drill: starts or stops