Documentation
¶
Overview ¶
Package generate_dq_rule_sql implements the generate_dq_rule_sql MCP tool: it turns a plain-language description of a data quality check into rule SQL, so a rule can be authored without writing SQL by hand.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
type Input ¶
type Input struct {
EdgeSiteID string `` /* 171-byte string literal not displayed */
ConnectionID string `` /* 162-byte string literal not displayed */
JobName string `` /* 174-byte string literal not displayed */
Columns []string `` /* 131-byte string literal not displayed */
Query string `` /* 135-byte string literal not displayed */
}
Input is the tool's typed input. edgeSiteId/connectionId come from prepare_create_dq_job; the table is identified by jobName.
type Output ¶
type Output struct {
Status OutputStatus `` /* 131-byte string literal not displayed */
Message string `json:"message" jsonschema:"Human-readable summary."`
SQLQuery string `` /* 188-byte string literal not displayed */
}
Output is the typed response.
type OutputStatus ¶
type OutputStatus string
OutputStatus is the overall outcome of a generate_dq_rule_sql call.
const ( // StatusSuccess means SQL was generated. StatusSuccess OutputStatus = "success" // StatusValidationError means the inputs failed validation before any call. StatusValidationError OutputStatus = "validation_error" // StatusError means generation failed due to a downstream DQ error. StatusError OutputStatus = "error" )
Source Files
Click to show internal directories.
Click to hide internal directories.