search

airscholar / e2e-data-engineering

An end-to-end data engineering pipeline that orchestrates data ingestion, processing, and storage using Apache Airflow, Python, Apache Kafka, Apache Zookeeper, Apache Spark, and Cassandra. All components are containerized with Docker for easy deployment and scalability.
https://www.youtube.com/watch?v=GqAcTrqKcrY
204 stars 92 forks source link

web server is not working,Which dependency. #2

Closed Ram443 closed 11 months ago

Ram443 commented 11 months ago

Hi

Thank you for your great courses. I am facing issue with e2e-data-engineering, can you please help me on this issue. web server is not working, Which dependency do we need to use.

Requirement already satisfied: importlib-metadata>=3.6.0 in /home/airflow/.local/lib/python3.9/site-packages (from Flask==2.2.5->-r requirements.txt (line 39)) (6.6.0) INFO: pip is looking at multiple versions of googleapis-common-protos to determine which version is compatible with other requirements. This could take a while.

The conflict is caused by: The user requested protobuf==3.19.2 googleapis-common-protos 1.60.0 depends on protobuf!=3.20.0, !=3.20.1, !=4.21.1, !=4.21.2, !=4.21.3, !=4.21.4, !=4.21.5, <5.0.0.dev0 and >=3.19.5

To fix this you could try to:

  1. loosen the range of package versions you've specified
  2. remove package versions to allow pip attempt to solve the dependency conflict
image
Ram443 commented 11 months ago

Hi

Thank you for your great courses. I am facing issue with e2e-data-engineering, can you please help me on this issue. web server is not working, Which dependency do we need to use.

Requirement already satisfied: importlib-metadata>=3.6.0 in /home/airflow/.local/lib/python3.9/site-packages (from Flask==2.2.5->-r requirements.txt (line 39)) (6.6.0) INFO: pip is looking at multiple versions of googleapis-common-protos to determine which version is compatible with other requirements. This could take a while.

The conflict is caused by: The user requested protobuf==3.19.2 googleapis-common-protos 1.60.0 depends on protobuf!=3.20.0, !=3.20.1, !=4.21.1, !=4.21.2, !=4.21.3, !=4.21.4, !=4.21.5, <5.0.0.dev0 and >=3.19.5

To fix this you could try to:

  1. loosen the range of package versions you've specified
  2. remove package versions to allow pip attempt to solve the dependency conflict
image