-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: number of records constraints #820
Comments
@aborruso
|
The maximum_fields probably is not necessary, because in the schema you have exactly the required fields, you can't have more and you can't have less. The number of lines is variable and you should have some constraints. Than
Thank you |
And probably also |
Fields limit might be useful for cases when a schema is not provided so probably it will make sense to provide these options as well (while it's very easy) |
👍 |
Wow, thank you very much @roll !!! |
@roll Is there a new documentation section, on how to use it? |
@aborruso |
@roll as usual, you are very kind. Thank you |
@roll how to run via cli this check? In example Thank you |
WOW, really great |
Overview
Hi,
below you have one of the official documentation yaml file. There some constraints fields related.
A lot of time I know that I know that a resource is valid only if it is made up of at least 365 rows (some annual dataset including leap years). Or that the rows shouldn't be more than 10.
I think it should be a great validate and check feature to have.
Thank you
Please preserve this line to notify @roll (lead of this repository)
The text was updated successfully, but these errors were encountered: