-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
🎉 New Source: New York Times [low-code cdk] #18746
Conversation
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.
Hello @Xabilahu, Marcos from Airbyte here 👋 . We received more than 25 new contributions along the weekend. One is yours 🎉 thank so much for! Our team is limited and maybe the review process can take longer than expected. As described in the Airbyte's Hacktoberfest your contribution was submitted before November 2nd and it is eligible to win the prize. The review process will validate other requirements. I ask to you patience until someone from the team review it.
Because I reviewed some contributions for Hacktoberfest so far I saw some common patterns you can check in advance:
- Make sure you have added connector documentation to
/docs/integrations/
- Remove the file
catalog
from/integration_tests
- Edit the
sample_config.json
inside/integration_tests
- For the
configured_catalog
you can use onlyjson_schema: {}
- Add title to all properties in the
spec.yaml
- Make sure the
documentationUrl
in thespec.yaml
redirect to Airbyte's future connector page, eg: connector Airtable thedocumentationUrl: https://docs.airbyte.com/integrations/sources/airtable
- Review now new line at EOF (end-of-file) for all files.
If possible send to me a DM in Slack with the tests credentials, this process will make easier to us run integration tests and publish your connector. If you only has production keys, make sure to create a bootstrap.md explaining how to get the keys.
{
"api_key": "YOUR API KEY",
"year": 2022,
"month": 6,
"period": 7,
"shared_type": "facebook"
} Instructions on how to get the API Key in |
Hi @marcosmarxm, thanks for the update! Below the status of the checklist:
|
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.
airbyte-integrations/connectors/source-nytimes/source_nytimes/spec.yaml
Outdated
Show resolved
Hide resolved
year: | ||
type: integer | ||
title: Year | ||
description: Year | ||
minimum: 1851 | ||
order: 1 | ||
month: | ||
type: integer | ||
title: Month | ||
description: Month | ||
minimum: 1 | ||
maximum: 12 | ||
order: 2 |
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.
I think this must be changed to start_date
and implement incremental syncs. Let me know if you need help here.
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.
I agree that this would be a good idea. I have been looking at datetime_stream_slicer.py
and it seems that it does not support monthly increments. I think it would be good for this use case. I think that I'm able to contribute that change as well.
Acceptance tests are failing because we need the changes in #18861 to be merged, where I add support for monthly and yearly incremental updates. Anyways, the implementation seems to work when I run the following command under a custom installation with the changes in #18861: python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json The used {
"api_key": "API-KEY",
"start_date": "2021-06",
"end_date": "2021-08",
"period": 7,
"shared_type": "facebook"
} |
Hello! I'm going to be out of the office this Friday and won't be able to review your contribution again today, I return next Monday. So far, most contributions look solid and are almost done to be approved. As said in Chris' comment all contributions made before 2-November are eligible to receive the prize and have 2 weeks to merge the contributions. But I ensure next week we're going to have your contribution merged. If you have questions about the implementation you can send them in Sorry the inconvenience and see you again next week, thank you so much for your contribution! |
@Xabilahu I'll review this again later today. The test are failing in my side. |
@marcosmarxm Tests should be passing now, I removed |
/test connector=connectors/source-nytimes
Build FailedTest summary info:
|
@marcosmarxm Need to run the acceptance tests with this config: {
"api_key": "API-KEY-HERE",
"start_date": "2021-06",
"end_date": "2021-06",
"period": 7,
"shared_type": "facebook"
} |
@Xabilahu I'm running with: {
"api_key": "api_key",
"start_date": "2022-10",
"end_date": "2022-11",
"period": 7
} |
The problem is with |
|
@marcosmarxm From the logs, I see that it failed at expected record validation step for
Could you try to run it with the provided config? |
Can you remove the expected records? It is more used for local/dev validation. |
/test connector=connectors/source-nytimes
Build PassedTest summary info:
|
/publish connector=connectors/source-nytimes
if you have connectors that successfully published but failed definition generation, follow step 4 here |
* Initial implementation: Support for `archive` stream * Added support for `most_popular` streams (emailed, shared, viewed) * Add `expected_records.txt` for acceptance tests * Added Documentation * Updated changelog with PR id * Add support for incremental syncs * Reduce size and remove most_popular streams from expected_records.txt * Remove `expected_records.txt` * auto-bump connector version Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com> Co-authored-by: Marcos Marx <marcosmarxm@users.noreply.github.com>
What
New Source: New York Times. https://developer.nytimes.com
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereUpdating a connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changesTests
Unit
Put your unit tests output here.
Integration
Put your integration tests output here.
Acceptance