You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m running into an issue with DataHub where I can’t connect to a self-hosted Tableau server through the proxy using Tableau ingestion. It works fine when I use non-secure HTTP with the server’s IP, but it fails when I try with the DNS URL and HTTPS.
I’ve added the https_proxy details to both the datahub-frontend-react and datahub-actions services in the docker-compose-without-neo4j-m1.quickstart.yml file, but it doesn’t seem to pick up the proxy during the Tableau ingestion process. What’s odd is that when I use curl inside the DataHub container with the same proxy and DNS URL over HTTPS, it connects just fine.
Also, I don’t have any issues connecting to BigQuery using the BigQuery ingestion process, so the proxy setup seems to work properly in other cases. Could you help check if the Tableau ingestion is handling proxy configurations correctly?
This is my yaml file for Tableau ingestion:
source:
type: tableau
config:
connect_uri: 'https://luffy.labtest.com'
stateful_ingestion:
enabled: true
ingest_tags: true
ingest_owner: true
token_name: DataHub
token_value: '${Tableau_Token}'
site: TW
i tried adding session_trust_env: true the tableau ingestion yaml file and I've got the following error:
[2024-12-10 03:00:18,785] DEBUG {datahub.ingestion.run.pipeline:364} - Reporter type:file,<class 'datahub.ingestion.reporting.file_reporter.FileReporter'> configured.
[2024-12-10 03:00:19,263] DEBUG {datahub.entrypoints:215} - Error: Failed to configure the source (tableau): 1 validation error for TableauConfig
session_trust_env
extra fields not permitted (type=value_error.extra)
Traceback (most recent call last):
File "/tmp/datahub/ingest/venv-tableau-3cbb1ad0ed8a0388/lib/python3.10/site-packages/datahub/ingestion/run/pipeline.py", line 136, in _add_init_error_context
yield
File "/tmp/datahub/ingest/venv-tableau-3cbb1ad0ed8a0388/lib/python3.10/site-packages/datahub/ingestion/run/pipeline.py", line 289, in init
self.source = source_class.create(
File "/tmp/datahub/ingest/venv-tableau-3cbb1ad0ed8a0388/lib/python3.10/site-packages/datahub/ingestion/source/tableau/tableau.py", line 628, in create
config = TableauConfig.parse_obj(config_dict)
File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj
File "pydantic/main.py", line 341, in pydantic.main.BaseModel.init
pydantic.error_wrappers.ValidationError: 1 validation error for TableauConfig
session_trust_env
extra fields not permitted (type=value_error.extra)
Linux version: Ubuntu 24.04 LTS
DataHub CLI version: 0.14.1
Datahub version: 0.14.1
Models: bundled
Python version: 3.12.3 (main, Nov 6 2024, 18:32:19) [GCC 13.2.0]
DataHub Docker Installation
I’m running into an issue with DataHub where I can’t connect to a self-hosted Tableau server through the proxy using Tableau ingestion. It works fine when I use non-secure HTTP with the server’s IP, but it fails when I try with the DNS URL and HTTPS.
I’ve added the https_proxy details to both the datahub-frontend-react and datahub-actions services in the docker-compose-without-neo4j-m1.quickstart.yml file, but it doesn’t seem to pick up the proxy during the Tableau ingestion process. What’s odd is that when I use curl inside the DataHub container with the same proxy and DNS URL over HTTPS, it connects just fine.
Also, I don’t have any issues connecting to BigQuery using the BigQuery ingestion process, so the proxy setup seems to work properly in other cases. Could you help check if the Tableau ingestion is handling proxy configurations correctly?
This is my yaml file for Tableau ingestion:
source:
type: tableau
config:
connect_uri: 'https://luffy.labtest.com'
stateful_ingestion:
enabled: true
ingest_tags: true
ingest_owner: true
token_name: DataHub
token_value: '${Tableau_Token}'
site: TW
Please see my test results below:
Results of Talbleau ingestion via HTTPS/HTTP URL and IP.
https_ip_failure.txt
https_url_failure.txt
http_ip_success.txt
Result of successful Curl connection via Proxy
curl_https_url_success.txt
The text was updated successfully, but these errors were encountered: