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

[FEATURE REQ] Add Schedules & Triggers and Job notifications to AzureDatabricksLinkedService #43398

Open
2 tasks done
Xanatos8 opened this issue Dec 13, 2024 · 0 comments
Open
2 tasks done
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@Xanatos8
Copy link

Is your feature request related to a problem? Please describe.
Right now using the AzureDatabricksLinkedService it's not possible to define this two fields:

  • Schedules & Triggers
  • Job notifications

These two fields work together to achieve that streaming applications are always running and send notifications when the application runs, fails and when there's latency while processing data.

Describe the solution you'd like
Add a way to add these two fields to AzureDatabricksLinkedService so that they can be defined through the API.

Describe alternatives you've considered
ADF emails kind of work, but they don't provide all the monitoring tools that Databricks provided right now. It's missing the latency feature. For the continuous part a loop may be added to the ADF pipeline when the Databricks job fails.

Additional context
Screenshots in the Databricks UI:
Image
Image

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • Description Added
  • Expected solution specified
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

1 participant