-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Source Facebook Marketing: Add lookback window to insights streams #12402
Source Facebook Marketing: Add lookback window to insights streams #12402
Conversation
@sherifnada I made this Draft related to #9805 |
@vladimir-remar this is ready to review? |
@lazebnyi can you check the implementation @vladimir-remar is doing for Facebook Marketing? |
@@ -147,3 +147,13 @@ class Config: | |||
"A list which contains insights entries, each entry must have a name and can contains fields, breakdowns or action_breakdowns)" | |||
), | |||
) | |||
|
|||
insights_lookback_window: Optional[PositiveInt] = Field( |
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.
we should make this default_insights_lookback_window
and apply it only to the default insights synced by this connector, and separately we should allow configuring this on a per-insight level in the custom insights
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.
thanks for your patience I will work on this ASAP.
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.
Hey @vladimir-remar I'm not sure you ended up implementing @sherifnada suggestion. Is anything blocking you from going in the suggested direction?
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 @alafanechere, maybe I'm wrong, I just replicate the same approach in the custom insight part.
airbyte/airbyte-integrations/connectors/source-facebook-marketing/source_facebook_marketing/spec.py
Line 80 in c6d00d7
insights_lookback_window: Optional[PositiveInt] = Field( |
@@ -147,3 +147,13 @@ class Config: | |||
"A list which contains insights entries, each entry must have a name and can contains fields, breakdowns or action_breakdowns)" | |||
), | |||
) | |||
|
|||
insights_lookback_window: Optional[PositiveInt] = Field( |
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.
Hey @vladimir-remar I'm not sure you ended up implementing @sherifnada suggestion. Is anything blocking you from going in the suggested direction?
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.
@vladimir-remar I think you're right, @sherifnada's concern is addressed, 👍 I'm requesting change as I think you need to update unit tests to cover your changes. This connector is in General Availability, meaning we are quite strict in terms of coverage. Could you please bump the connector version in the Dockerfile and update the changelog in facebook-marketing.md
?
I would also need an additional review from @sherifnada or @lazebnyi 🙏 |
/test connector=connectors/source-facebook-marketing
|
@alafanechere I think @grubberr can help with review. Already discussed with him about that. He working now on FB marketing. |
airbyte-integrations/connectors/source-facebook-marketing/source_facebook_marketing/spec.py
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-facebook-marketing/source_facebook_marketing/spec.py
Show resolved
Hide resolved
@vladimir-remar please also fix unit_tests
|
/test connector=connectors/source-facebook-marketing
Build FailedTest summary info:
|
Hey @grubberr do you have an idea why tests are failing now after passing yesterday? Did you merge master in the branch? |
@alafanechere Yes I did today after see the conflict. |
@vladimir-remar I think unit_tests failed because the master branch changed and you need to synchronise your code base with the latest updates in the master |
/test connector=connectors/source-facebook-marketing
Build PassedTest summary info:
|
airbyte-integrations/connectors/source-facebook-marketing/source_facebook_marketing/spec.py
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-facebook-marketing/source_facebook_marketing/spec.py
Outdated
Show resolved
Hide resolved
...te-integrations/connectors/source-facebook-marketing/unit_tests/test_base_insight_streams.py
Outdated
Show resolved
Hide resolved
…d_updated and test_completed_slices_in_lookback_period
/test connector=connectors/source-facebook-marketing
Build PassedTest summary info:
|
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.
Thank you @grubberr for the review and @vladimir-remar for the changes! I'm now waiting for @misteryeo approval to publish and merge.
/publish connector=connectors/source-facebook-marketing
|
Thank you @vladimir-remar for the contribution! The new connector version is now published and I'm going to merge this PR. |
What
Bring back the possibility to set up an attribution window.
Let say the users will not use all the data retrieve from the insight stream and just use part of it (e.g., spend) in some cases
set a
looback_window
short than 28 days would help the users by reducing the sync time.How
Set value for
insights_lookback_window
throught config.Recommended reading order
x.java
y.python
🚨 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.
Updating 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 hereTests
Unit
Put your unit tests output here.
Integration
Put your integration tests output here.
Acceptance
Put your acceptance tests output here.