Closed saras-daton closed 1 year ago
Hi @joellabes @dbeatty10, Can you please review this PR and share feedback if any..
@joellabes - That is right, it is not possible to input source table name. We have to search by pattern to identify the tables and unify the data with certain deduplication and standardisation rules. All the models in a package are independent of one another. Downstream applications will source these to join and derive business KPI's.
@joellabes - Need your suggestion for below:
We have renamed few packages to adhere common naming standard. Example: facebook_ads is renamed to FacebookAds. However, we still see both packages appearing in dbt hub, although they point to same GIT repo. Can you help us understand the process to overcome this scenario.
We also removed old releases which are no longer required from the GIT Repo, however we still see those versions in the DBT HUB Packages version dropdown
@joellabes @dbeatty10 - Can you please help us with above query?
@saras-daton sorry for the delay - I've just added instructions to the hub.getdbt.com repo explaining how to do a redirect: https://github.com/dbt-labs/hub.getdbt.com/pull/2481
Added unicommerce package to Saras-daton
Description
New Data Unification package for Unicommerce Daton Integration data Renaming Existing packages to pascal case
Link to your package's repository: https://github.com/saras-daton/AmazonAds.git https://github.com/saras-daton/AmazonSellerCentral.git https://github.com/saras-daton/AmazonVendorCentral.git https://github.com/saras-daton/FacebookAds.git https://github.com/saras-daton/Shopify.git https://github.com/saras-daton/Unicommerce.git https://github.com/saras-daton/Upscribe.git https://github.com/saras-daton/Recharge.git https://github.com/saras-daton/GoogleAnalytics.git
Checklist
This checklist is a cut down version of the best practices that we have identified as the package hub has grown. Although meeting these checklist items is not a prerequisite to being added to the Hub, we have found that packages which don't conform provide a worse user experience.
First run experience
Customisability
Packages for data transformation (delete if not relevant):
Dependencies
Dependencies on dbt Core
require-dbt-version
range indbt_project.yml
. Example: A package which depends on functionality added in dbt Core 1.2 should set itsrequire-dbt-version
property to[">=1.2.0", "<2.0.0"]
.Dependencies on other packages defined in packages.yml:
Interoperability
{{ dbt.except() }}
and{{ dbt.type_string() }}
.users
.Versioning