Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Consider splitting Google Provider
See original GitHub issueThe Google provider is huge. It’s by far the biggest provider out there and it has a number of sometimes more closely coupled and sometimes not coupled at all (leveldb) operators.
We should consider splitting the Google operator into smaller pieces, but that would involve some more decisions:
- what to do with common part
- what should be the split ? Per service? Per cloud ?
- how to manage dependencies between different provider
- how to manage transition and backwards compatibility
This is more of opening the discussion than making decisions yet.
Issue Analytics
- State:
- Created 2 years ago
- Comments:28 (27 by maintainers)
Top Results From Across the Web
Splitting traffic | Google App Engine standard environment docs
When you have specified two or more versions for splitting, you must choose whether to split traffic by using either an IP address...
Read more >Google: Splitting or Merging a Website Can Cause Months of ...
Google's John Mueller revealed that splitting or merging sites could cause months of unstable search rankings.
Read more >Google Stock Split | Where Next for GOOGL Shares?
87.41% of retail investor accounts lose money when trading CFDs with this provider. You should consider whether you understand how CFDs work and...
Read more >Google Stock Split: What Investors Should Know Going Forward
The aim of this article isn't to debate the merits of the stock split to GOOG but to discuss the stock price outlook...
Read more >Email routing and delivery options for Google Workspace
You can also use split delivery when you migrate from another email server to Gmail. Use split delivery with a small group of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@rodrigo-fss -> Plyvel is not a requirement for Google Provider any more - it’s optional dependency - you do not have to install it. But in any case you need to upgrade to 2.1+ as google providers are already not compatible with 2.0.* line so you are using a really old version of those and even if we split providers, you will have to upgrade anyway to use that.
So upgreding to Airflow 2.1+ (Ideallly 2.3+) is the RIGHT solution to your problem, not waiting for splitting the provider.
+1 to the polls on Airflow Summit.