Scale Intelligence■ Docs
Docs / The model / SourceTable

SourceTable.

One table of a read artefact: its count with its exactness, its population and the control that must come back right at the same hash

Figure 1SourceTablespecified
SOURCETABLEvalue at none scopeschematexttabletextkindenum:table|view|fileabsent when the count was not read in the boundrowscountoptionalexactnessenum:exact|estimated|not read in th…absent when the reading did not list themcolumns[SourceColumn]optionalwhat one row ispopulationtextthe known count or row that must come back right at the same file hash: rows=<count>, bytes=<count>, or marker=<file>:<key> for a completion marker whose JSON names the countcontroltextread_attimefor a table that is a folder of files: each file with its hash, its bytes and its rows where readfiles[LakeFile]optionalfor a view of a catalogue: its definition as the engine states it, which is the rule that made the derived table; the files the definition reads are the table's files, and the rule is recorded on the procedure at every readingdefinitiontextoptionalSOURCECOLUMNthrough columnsLAKEFILEthrough files
SourceTable is a value at none scope. The drawing shows its fields and the objects that they point at.
kind
value
scope
none
key
none
store
none
family
sources

Fields#

fieldtyperequirednote
schematextyes
tabletextyes
kindone of table | view | fileyes
rowscountnoabsent when the count was not read in the bound
exactnessone of exact | estimated | not read in the boundyes
columnsSourceColumnnoabsent when the reading did not list them
populationtextyeswhat one row is
controltextyesthe known count or row that must come back right at the same file hash: rows=, bytes=, or marker=: for a completion marker whose JSON names the count
read_attimeyes
filesLakeFilenofor a table that is a folder of files: each file with its hash, its bytes and its rows where read
definitiontextnofor a view of a catalogue: its definition as the engine states it, which is the rule that made the derived table; the files the definition reads are the table’s files, and the rule is recorded on the procedure at every reading

Routes that use it#

No route takes or returns SourceTable directly. The record holds it, and the objects that point at it reach it.