microscopic-mechanic-13766
10/25/2022, 1:35 PMsink:
type: datahub-rest
config:
server: '<http://datahub-gms:8080>'
source:
type: hive
config:
database: <db>
profiling:
enabled: true
host_port: 'hive-server:10000'
options:
connect_args:
auth: KERBEROS
kerberos_service_name: hive-server
bumpy-pharmacist-66525
10/25/2022, 1:48 PMstateful_ingestion
feature on sources which support it. I am in the process of updating the Iceberg
source to support stateful_ingestion
, but I am running into a weird issue. From my testing, when the feature is enabled and I try to re-create and then re-ingest a table (after it has been soft-deleted by a previous ingestion run), it does not appear again in the UI. Is this the expected behavior? I would have imagined that when the ingestion recipe is executed, that the dataset (which was remade) would re-appear in the UI even if it was soft-deleted in an earlier ingestion run.salmon-angle-92685
10/25/2022, 4:39 PMwide-spring-1569
10/25/2022, 6:02 PMcannot resolve include "//customer/views/customer_account/customer_responses_all.view.lkml"
This is almost certainly due to the fact that we are using multiple repos to define our LookML with a manifest.lkml
used to define references to files in other projects, e.g.
local_dependency: {
project: "customer"
}
Is this something that people have been able to work with or is our multi-repo setup beyond what the acryl-datahub[lookml]
library is set up to handle?
Basically I have about 10 repos and they all reference each other in the include statements which makes the parsing of LookML much harder.refined-energy-76018
10/26/2022, 12:25 AMUP_FOR_RETRY
status? If not, are there any plans to?little-breakfast-38102
10/26/2022, 5:22 AMUSER datahub
ENTRYPOINT [“datahub”]
Appreciate any help on this.
best-umbrella-88325
10/26/2022, 10:58 AMRUN_INGEST - {'errors': [],
'exec_id': '484fcd84-7b63-41f2-9ace-faac265203ec',
'infos': ['2022-10-26 10:47:10.581114 [exec_id=484fcd84-7b63-41f2-9ace-faac265203ec] INFO: Starting execution for task with name=RUN_INGEST',
'2022-10-26 10:47:18.713045 [exec_id=484fcd84-7b63-41f2-9ace-faac265203ec] INFO: stdout=venv setup time = 0\n'
'This version of datahub supports report-to functionality\n'
'datahub ingest run -c /tmp/datahub/ingest/484fcd84-7b63-41f2-9ace-faac265203ec/recipe.yml --report-to '
'/tmp/datahub/ingest/484fcd84-7b63-41f2-9ace-faac265203ec/ingestion_report.json\n'
'[2022-10-26 10:47:13,128] INFO {datahub.cli.ingest_cli:182} - DataHub CLI version: 0.9.0\n'
'[2022-10-26 10:47:13,158] INFO {datahub.ingestion.run.pipeline:175} - Sink configured successfully. DataHubRestEmitter: configured '
AWS Glue Output:
RUN_INGEST - {'errors': [],
'exec_id': '82df4b0b-8d97-461b-bc4c-f4922ebe5d04',
'infos': ['2022-10-26 10:53:31.768404 [exec_id=82df4b0b-8d97-461b-bc4c-f4922ebe5d04] INFO: Starting execution for task with name=RUN_INGEST',
'2022-10-26 10:53:37.857276 [exec_id=82df4b0b-8d97-461b-bc4c-f4922ebe5d04] INFO: stdout=venv setup time = 0\n'
'This version of datahub supports report-to functionality\n'
'datahub ingest run -c /tmp/datahub/ingest/82df4b0b-8d97-461b-bc4c-f4922ebe5d04/recipe.yml --report-to '
'/tmp/datahub/ingest/82df4b0b-8d97-461b-bc4c-f4922ebe5d04/ingestion_report.json\n'
'[2022-10-26 10:53:34,404] INFO {datahub.cli.ingest_cli:177} - DataHub CLI version: 0.8.43.5\n'
'[2022-10-26 10:53:34,478] INFO {datahub.ingestion.run.pipeline:163} - Sink configured successfully. DataHubRestEmitter: configured '
dazzling-caravan-26726
10/26/2022, 11:06 AMdazzling-caravan-26726
10/26/2022, 11:06 AMdazzling-caravan-26726
10/26/2022, 11:08 AMcolossal-hairdresser-6799
10/26/2022, 12:11 PMprehistoric-helicopter-42228
10/26/2022, 1:51 PMsquare-solstice-69079
10/26/2022, 2:18 PMhappy-twilight-44865
10/26/2022, 2:19 PMhappy-baker-8735
10/26/2022, 2:39 PM{
"entityType":"domain",
"entityUrn": "urn:li:domain:referentiel",
"changeType":"UPSERT",
"aspectName":"domainProperties",
"aspect":{
"value":"{\"name\": \"Référentiel\"}",
"contentType":"application/json"
}
{
"entityType":"domain",
"entityUrn": "urn:li:domain:referentiel",
"changeType":"UPSERT",
"aspectName":"domainProperties",
"aspect":{
"value":"{\"name\": \"R\u00e9f\u00e9rentiel\"}",
"contentType":"application/json"
}
hallowed-lizard-92381
10/26/2022, 8:01 PMwitty-motorcycle-52108
10/26/2022, 9:05 PMsilly-oil-35180
10/27/2022, 1:07 AMhttp://<gms-url>:8080/aspects/<encoded urn>/aspects?action=getTimeseriesAspectValues
However, Stats
tab is not activated on web ui.
I checked GraphQL which used to fetch dataset(getDataset
). GarphQL didn’t fetch any datasetProfiles
.
Why this problem happens? How can I fix it?gifted-knife-16120
10/27/2022, 3:07 AMEnable Profiling
for postgres? I already give SELECT permission, but it still show an permission errorlemon-cat-72045
10/27/2022, 6:28 AMfamous-florist-7218
10/27/2022, 8:22 AMbigquery
ingestion. It seems the executor couldn’t run probably. Lineage map function was unable to retrieve the audit log. Any help?
Here is the log from datahub-actions:
[2022-10-27 07:26:25,746] INFO {datahub.ingestion.source.bigquery_v2.lineage:154} - Populating lineage info via GCP audit logs for my-dev-95adf
[2022-10-27 07:26:25,783] INFO {datahub.ingestion.source.bigquery_v2.lineage:161} - Log Entries loaded
[2022-10-27 07:26:25,783] INFO {datahub.ingestion.source.bigquery_v2.lineage:371} - Entering create lineage map function
[2022-10-27 07:26:25,783] INFO {datahub.ingestion.source.bigquery_v2.lineage:218} - Start loading log entries from BigQuery for my-dev-95adf with start_time=2022-10-25T23:26:40Z and end_time=2022-10-27T07:59:41Z
[2022-10-27 07:26:25,783] INFO {datahub.ingestion.source.bigquery_v2.lineage:234} - Start iterating over log entries from BigQuery for my-dev-95adf
unable to retrieve container logs for <containerd://68b4741cd185c5ac09e560ee58932bb7166861d580c955ace267eed4be25f8d>9
unable to retrieve container logs for <containerd://68b4741cd185c5ac09e560ee58932bb7166861d580c955ace267eed4be25f8d>9
unable to retrieve container logs for <containerd://68b4741cd185c5ac09e560ee58932bb7166861d580c955ace267eed4be25f8d>9
unable to retrieve container logs for <containerd://68b4741cd185c5ac09e560ee58932bb7166861d580c955ace267eed4be25f8d>9
...
late-yak-71835
10/27/2022, 9:22 AMmicroscopic-mechanic-13766
10/27/2022, 11:31 AMbitter-byte-67818
10/27/2022, 2:25 PMmelodic-tomato-17544
10/27/2022, 4:35 PMGET /color-of-the-day
and GET /color-of-the-day/{date}
where the second takes a specific date. The openapi spec details the parameters, format, etc., but the datahub ingester is still making requests to /color-of-the-day/{date}
(literally), and not picking up the example parameter, eg, requesting GET /color-of-the-day/2021-10-24
… any suggestions? I’ve tried googling around but the answers are pretty sparse. I did figure out I can use forced_examples
in the recipe source config, but I’d prefer not to if possible, favoring the API documentation instead.some-car-9623
10/27/2022, 6:35 PMrefined-energy-76018
10/28/2022, 12:29 AMworried-branch-76677
10/28/2022, 3:59 AMInputFieldClass
.
Any guidance will be nicelemon-cat-72045
10/28/2022, 5:52 AMgifted-knife-16120
10/28/2022, 6:20 AMingest profiling
for postgres
{"public.tablename": ["Profiling exception year -1 is out of range"]},
above is the error. how can I fix this?