integration
Here are 1,618 public repositories matching this topic...
-
Updated
Mar 25, 2021 - JavaScript
-
Updated
Mar 30, 2021 - Java
-
Updated
Mar 7, 2021 - C#
-
Updated
Mar 15, 2021
SQL Insert Statement
Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase
Expected behavior:
to be able to insert to a sql database in an activity
What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database
Additional information you deem important (e.g. I need this tomorrow):
-
Updated
Mar 30, 2021 - Python
-
Updated
Mar 29, 2021 - Scala
-
Updated
Mar 30, 2021 - Scala
-
Updated
Mar 12, 2021 - Python
-
Updated
Mar 30, 2021 - Java
-
Updated
Jan 24, 2017 - Scala
-
Updated
Dec 29, 2020 - PowerShell
Running operator against OpenShift 4.6 and noticed:
W0322 15:58:35.370055 10528 warnings.go:67] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
-
Updated
Mar 30, 2021 - TypeScript
-
Updated
Mar 30, 2021 - Java
-
Updated
Feb 25, 2021 - JavaScript
-
Updated
Mar 29, 2021 - JavaScript
-
Updated
Mar 18, 2021 - Python
-
Updated
Mar 9, 2021 - Java
-
Updated
Mar 30, 2021 - Java
-
Updated
Oct 18, 2018 - C
Is your feature request related to a problem? If yes, please describe the problem.
Currently our playground is without any code sharing capabilities.
Describe the solution you'd like to see.
Allow to share the playground with a certain query by adding the query as a base64 in the URL.
Were you inspired by anything else, that you have experienced?
Inspired by https://sandcastle
-
Updated
Jan 19, 2021 - Java
-
Updated
Mar 30, 2021 - Java
-
Updated
Mar 29, 2021 - JavaScript
-
Updated
Mar 23, 2021 - Apex
Improve this page
Add a description, image, and links to the integration topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the integration topic, visit your repo's landing page and select "manage topics."


Tell us about the problem you're trying to solve
As demonstrated in airbytehq/airbyte#1814 (comment) when the Instagram source receives a transient 500 from the FB servers, the sync for that stream fails.
Describe the solution you’d like
The source should instead backoff & retry on transient failures, same as with rate limiting. We should do this