synapse

type AcceptedValuesCheck ¶

type AcceptedValuesCheck struct {
	// contains filtered or unexported fields
}

func (c *AcceptedValuesCheck) Check(ctx context.Context, ti *scheduler.ColumnCheckInstance) error

type AssetMaterializationMap ¶

type AssetMaterializationMap map[pipeline.MaterializationType]map[pipeline.MaterializationStrategy]MaterializerFunc

type BasicOperator ¶

type BasicOperator struct {
	// contains filtered or unexported fields
}

func NewBasicOperator(conn config.ConnectionGetter, extractor query.QueryExtractor, materializer materializer, parser *sqlparser.SQLParser) *BasicOperator

func (o BasicOperator) Run(ctx context.Context, ti scheduler.TaskInstance) error

func (o BasicOperator) RunTask(ctx context.Context, p *pipeline.Pipeline, t *pipeline.Asset) error

type Materializer ¶

type Materializer struct {
	MaterializationMap AssetMaterializationMap
	// contains filtered or unexported fields
}

The other packages all use a materializer that renders the query to a single string. Due to the quirks of synapse we need to create a different materializer that returns a slice of strings, since synapse server requires us to send separate batches for certain things.

func NewMaterializer(fullRefresh bool) *Materializer

func (m *Materializer) Render(asset *pipeline.Asset, query string) ([]string, error)

type MaterializerFunc ¶

type MaterializerFunc func(task *pipeline.Asset, query string) ([]string, error)

type PatternCheck ¶ added in v0.10.1

type PatternCheck struct {
	// contains filtered or unexported fields
}

func (c *PatternCheck) Check(ctx context.Context, ti *scheduler.ColumnCheckInstance) error

type Renderer ¶ added in v0.6.6

type Renderer struct {
	// contains filtered or unexported fields
}

func NewRenderer(fullRefresh bool) *Renderer

func (r *Renderer) Render(asset *pipeline.Asset, query string) (string, error)