You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
typeStructurestruct {
// ... current fields omitted// Tabular indicates if this data is intended to be interpreted in a row/column formatTabularbool// The number of errors determined by validating this data against SchemaErrorsint
}
Note that Errors should always be encoded to json (as in, no omitempty), even if the number of errors is 0 (because 0 errors is good!).
Tabular is to indicate "this data is intended to be consumed as a table", which might apply to high-dimensional data, but almost always applies to certain formats like csv.
Ok quick updates on this, after some thought, I think we can drop the Tabular field. I initially thought we'd need to rely on the tabular flag to manage the transition from tabular schemas to jsonschema, but we've found a way around that. If anything, Tabular may end up being a field of VizConfig. So two updates to this issue:
No more tabular field
Let's change the name of the new Errors field to ErrCount, which seems more accurate
b5
added a commit
that referenced
this issue
Jan 24, 2018
dataset.Structure now has a field to store the number of validation
errors in a given dataset. dsfs.CreateDataset now fills this out
at time of dataset creation automatically.
closes#47
Two new fields on Structure before we ship 0.1.0:
Note that Errors should always be encoded to json (as in, no
omitempty
), even if the number of errors is 0 (because 0 errors is good!).Tabular is to indicate "this data is intended to be consumed as a table", which might apply to high-dimensional data, but almost always applies to certain formats like csv.
Steps to complete
Assign
and json coding funcsdsfs.CreateDataset
to set the Errors field before writingTabular = true
if Structure.Format == "csv"The text was updated successfully, but these errors were encountered: