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.

No module named 'airflow.providers.google.common.hooks.leveldb'

See original GitHub issue

Apache Airflow version: 2.0.2

Kubernetes version (if you are using kubernetes) (use kubectl version): v1.18.18

Environment: Cloud provider or hardware configuration: AWS

What happened:

Updated to Airflow 2.0.2 and a new warning appeared in webserver logs:

WARNING - Exception when importing 'airflow.providers.google.common.hooks.leveldb.LevelDBHook' from 'apache-airflow-providers-google' package: No module named 'airflow.providers.google.common.hooks.leveldb'

What you expected to happen: No warning.

How to reproduce it: Don’t know the specific details. Have tried adding pip install --upgrade apache-airflow-providers-google but the error was still there.

Anything else we need to know: I am not using LevelDB for anything in my code, as a result I don’t understand from where this error is coming.

Issue Analytics

State:
Created 2 years ago
Comments:17 (10 by maintainers)

Top GitHub Comments

1reaction

potiukcommented, Apr 29, 2021

WARNING - Exception when importing ‘airflow.providers.google.common.hooks.leveldb.LevelDBHook’ from ‘apache-airflow-providers-google’ package: No module named ‘airflow.providers.google.common.hooks.leveldb’

Yep. This will fixed when we release next Google Provider and you update either the provider or, Airlfow (we plan to release 2.0.3 very soon addressing a small subset of changes + PIP 21 installability). PR here: https://github.com/apache/airflow/pull/15576

1reaction

potiukcommented, Apr 21, 2021

BTW. I recommend to use corresponding docker build . command to build the image rather than breeze.

See the latest documentation for this with nice examples: https://airflow.apache.org/docs/docker-stack/build.html#customizing-the-image

It’s much simpler now to build the images and when you use docker build commands by default the released packages are used from PYPI to build the image rather than local source code. Unless you want to use latest master, version of Airflow/providers - this is the recommended way now.

Top Results From Across the Web

import error after upgrade to airflow2.0.2 - Stack Overflow

It's a bug (harmless) in definition of the google provider 2.2.0 in fact: In provider.yaml : airflow.providers.google.common.hooks.leveldb.

airflow.providers.google.leveldb.hooks.leveldb - Apache Airflow

Hook for Level DB ... LevelDBHook. Plyvel Wrapper to Interact With LevelDB Database ... exception airflow.providers.google.leveldb.hooks.leveldb.

[GitHub] [airflow] maryampashmi commented on issue #15451: No ...

airflow.providers.google.leveldb.hooks.LevelDBHook This is didn't solved. I am getting the same error. Just tried to create a docker to install the module ...

apache-airflow-providers-google 8.6.0 - PyPI

All classes for this provider package are in airflow.providers.google ... Fix DataprocJobBaseOperator not being compatible with dotted names (#23439).

airflow already exist in the db - You.com | The AI Search ...

LevelDBHook' from 'apache-airflow-providers-google' package: No module named 'airflow.providers.google.common.hooks.leveldb' airflow-init_1 | Upgrades done ...