Pipeline Service Client - Handle unexpected status response (#13314)

* airflow install docs

* Pipeline Service Client - Handle unexpected response
This commit is contained in:
Pere Miquel Brull 2023-09-26 12:58:39 +02:00 committed by GitHub
parent a4b9a2d2cb
commit 9900764961
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 20 additions and 10 deletions

View File

@ -78,18 +78,25 @@ Carefully reviewing this will prevent easy errors.
### (Optional) 3. Update your OpenMetadata Ingestion Client
If you are running the ingestion workflows **externally**, you need to make sure that the Python Client you use is aligned
If you are running the ingestion workflows **externally** or using a custom Airflow installation, you need to make sure that the Python Client you use is aligned
with the OpenMetadata server version.
For example, if you are upgrading the server to the version `x.y.z`, you will need to update your client with
```
```bash
pip install openmetadata-ingestion[<plugin>]==x.y.z
```
The `plugin` parameter is a list of the sources that we want to ingest. An example would look like this `openmetadata-ingestion[mysql,snowflake,s3]==1.1.5`.
You will find specific instructions for each connector [here](/connectors).
Moreover, if working with your own Airflow deployment - not the `openmetadata-ingestion` image - you will need to upgrade
as well the `openmetadata-managed-apis` version:
```bash
pip install openmetadata-managed-apis==x.y.z
```
## 1.1.5 - Stable Release 🎉
OpenMetadata 1.1.5 is a stable release. Please check the [release notes](/releases/latest-release).

View File

@ -78,23 +78,24 @@ Carefully reviewing this will prevent easy errors.
### (Optional) 3. Update your OpenMetadata Ingestion Client
If you are running the ingestion workflows **externally**, you need to make sure that the Python Client you use is aligned
If you are running the ingestion workflows **externally** or using a custom Airflow installation, you need to make sure that the Python Client you use is aligned
with the OpenMetadata server version.
For example, if you are upgrading the server to the version `x.y.z`, you will need to update your client with
```
```bash
pip install openmetadata-ingestion[<plugin>]==x.y.z
```
The `plugin` parameter is a list of the sources that we want to ingest. An example would look like this `openmetadata-ingestion[mysql,snowflake,s3]==1.1.1`.
The `plugin` parameter is a list of the sources that we want to ingest. An example would look like this `openmetadata-ingestion[mysql,snowflake,s3]==1.1.5`.
You will find specific instructions for each connector [here](/connectors).
## 1.2 - Stable Release 🎉
Moreover, if working with your own Airflow deployment - not the `openmetadata-ingestion` image - you will need to upgrade
as well the `openmetadata-managed-apis` version:
OpenMetadata 1.2 is a stable release. Please check the [release notes](/releases/latest-release).
If you are upgrading production this is the recommended version to upgrade to.
```bash
pip install openmetadata-managed-apis==x.y.z
```
## Deprecation Notice

View File

@ -284,10 +284,12 @@ public class AirflowRESTClient extends PipelineServiceClient {
return buildUnhealthyStatus("Airflow APIs not found. Please follow the installation guide.");
}
return buildUnhealthyStatus(
String.format("Unexpected status response: code [%s] - [%s]", response.statusCode(), response.body()));
} catch (Exception e) {
return buildUnhealthyStatus(String.format("Failed to get REST status due to [%s].", e.getMessage()));
}
throw new PipelineServiceClientException(String.format("Failed to get REST status due to %s.", response.body()));
}
@Override