Skip to content
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

[ADAP-1090] [Feature] Adding Pyspark job options to the model config #1068

Closed
3 tasks done
gbmarc1 opened this issue Jan 4, 2024 · 2 comments
Closed
3 tasks done
Labels
Stale type:enhancement New feature or request

Comments

@gbmarc1
Copy link

gbmarc1 commented Jan 4, 2024

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt-bigquery functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Adding pyspark job options to the model config to alter the job behaviour on the model level. I suggest adding the dataproc_pyspark_job field to the model config which is a dictionary with the following fields.

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

yes

Anything else?

PR -> https://github.com/dbt-labs/dbt-bigquery/pull/1048/files

@gbmarc1 gbmarc1 added type:enhancement New feature or request triage:product labels Jan 4, 2024
@github-actions github-actions bot changed the title [Feature] Adding Pyspark job options to the model config [ADAP-1090] [Feature] Adding Pyspark job options to the model config Jan 4, 2024
Copy link
Contributor

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

@github-actions github-actions bot added the Stale label Aug 13, 2024
Copy link
Contributor

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale type:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants