-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[DOCS] Choosing and configuring DataConnectors #3533
[DOCS] Choosing and configuring DataConnectors #3533
Conversation
✔️ Deploy Preview for niobium-lead-7998 ready! 🔨 Explore the source changes: 4033abc 🔍 Inspect the deploy log: https://app.netlify.com/sites/niobium-lead-7998/deploys/61816c132ab0fd0007b22542 😎 Browse the preview: https://deploy-preview-3533--niobium-lead-7998.netlify.app |
HOWDY! This is your friendly 🤖 CHANGELOG bot 🤖Please don't forget to add a clear and succinct description of your change under the Develop header in ✨ Thank you! ✨ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome overall! I think we might need some more explanation on some specific topics. We may also need a bit more detail explaining when to use Configured vs Inferred. Is it just that you can use Inferred when Data Assets are not divided equally in the same location, but where there's inconsistency, you need to use Configured? Inferred are actually more configurable than I had expected, so making this more explicit would be helpful.
docs/guides/connecting_to_your_data/how_to_choose_which_dataconnector_to_use.md
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_choose_which_dataconnector_to_use.md
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_choose_which_dataconnector_to_use.md
Outdated
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_choose_which_dataconnector_to_use.md
Outdated
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_configure_an_inferredassetdataconnector.md
Outdated
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_configure_a_runtimedataconnector.md
Outdated
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_configure_an_inferredassetdataconnector.md
Outdated
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_configure_an_inferredassetdataconnector.md
Outdated
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_configure_an_inferredassetdataconnector.md
Outdated
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_configure_an_inferredassetdataconnector.md
Outdated
Show resolved
Hide resolved
…m:great-expectations/great_expectations into docs/DEVREL-213/everything-dataconnectors
docs/guides/connecting_to_your_data/how_to_configure_an_inferredassetdataconnector.md
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Some comments inside.
- I did not see any examples that use the Batch filtering capabilities (including the use of a custom
Python
based filter query.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great overall! Just a few more minor nits. I haven't gone through the testing piece in detail either.
| InferredAssetDataConnectors | ConfiguredAssetDataConnectors | | ||
| --- | --- | | ||
| InferredAssetFilesystemDataConnector | ConfiguredAssetFilesystemDataConnector | | ||
| InferredAssetFilePathDataConnector | ConfiguredAssetFilePathDataConnector | | ||
| InferredAssetAzureDataConnector | ConfiguredAssetAzureDataConnector | | ||
| InferredAssetGCSDataConnector | ConfiguredAssetGCSDataConnector | | ||
| InferredAssetS3DataConnector | ConfiguredAssetS3DataConnector | | ||
| InferredAssetSqlDataConnector | ConfiguredAssetSqlDataConnector | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this table.
docs/guides/connecting_to_your_data/how_to_choose_which_dataconnector_to_use.md
Outdated
Show resolved
Hide resolved
docs/guides/connecting_to_your_data/how_to_configure_an_inferredassetdataconnector.md
Show resolved
Hide resolved
|
||
The configuration would also work with a regex capturing the entire filename (e.g. `pattern: (.*)\.csv`). However, capturing the month on its own allows for `batch_identifiers` to be used to retrieve a specific Batch of the Data Asset. For more information about capture groups, refer to the Python documentation on [regular expressions](https://docs.python.org/3/library/re.html#re.Match.group). | ||
|
||
Later on we could retrieve the data in `yellow_tripdata_2019-02.csv` of `yellow_tripdata` as its own batch using `context.get_validator()` by specifying `{"month": "2019-02"}` as the `batch_identifier`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is wild - I hadn't realized that you could specify batch_identifiers
at the top level of the get_validator
- I've only seen it specified within the batch_request
.
docs/guides/connecting_to_your_data/how_to_configure_a_configuredassetdataconnector.md
Show resolved
Hide resolved
…gure_a_configuredassetdataconnector.md
Is this referring to the If so, I have added an example to |
…m:great-expectations/great_expectations into docs/DEVREL-213/everything-dataconnectors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Just one question/possible update, but I don't want it to gate. Amazing work!
docs/guides/connecting_to_your_data/how_to_configure_an_inferredassetdataconnector.md
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Just one question/possible update, but I don't want it to gate. Amazing work!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (strong work!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks wonderful :)
Changes proposed in this pull request:
Notable changes not in this pull request:
Definition of Done
Please delete options that are not relevant.