some-car-9623
01/12/2023, 3:01 PMaverage-hydrogen-40851
01/12/2023, 4:23 PMsparse-australia-70466
01/12/2023, 4:37 PMdatahub-frontend
? I'm having some issues integrating authentication with our internal OIDC provider and I wanted to see some more verbose logs.red-waitress-53338
01/13/2023, 2:35 AMabundant-television-56673
01/13/2023, 9:33 AM[A-z]+\.[A-z0-9-]+@company\.com
I get zero users returned when there are clear matches in the ingestion output
'urn:li:corpuser:<http://ZMuraaaa_x.com#EXT#@company.onmicrosoft.com.*|ZMuraaaa_x.com#EXT#@company.onmicrosoft.com.*>',
'urn:li:corpuser:zoe.a1@company.com.*',
'urn:li:corpuser:zoe.a2@company.com.*',
'urn:li:corpuser:<http://Zoe.a3_south.gov#EXT#@company.onmicrosoft.com.*|Zoe.a3_south.gov#EXT#@company.onmicrosoft.com.*>',
'urn:li:corpuser:<http://Zoe.Chase_test.com#EXT#@company.onmicrosoft.com.*|Zoe.Chase_test.com#EXT#@company.onmicrosoft.com.*>',
salmon-psychiatrist-4013
01/13/2023, 11:13 AMFile "C:\Users\xxxxx\AppData\Local\Programs\Python\Python39\lib\site-packages\datahub\ingestion\source\sql\vertica.py", line 1014, in loop_profiler_requests
for projection in inspector.get_projection_names(schema): # type: ignore
AttributeError: 'PGInspector' object has no attribute 'get_projection_names'
With little bit of debugging i was able to figure out that the inspector being used is sqlalchemy.dialects.postgresql.base.PGInspector and this inspector infact doesn't have function get_projection_names.
Question : is it the correct function being used in loop_profiler_requests call and in general did anybody have success with profiling Vertica ?melodic-dress-7431
01/13/2023, 1:43 PMmelodic-dress-7431
01/13/2023, 1:44 PMDid not find a registered class for airflow
melodic-dress-7431
01/13/2023, 1:44 PMelegant-state-4
01/13/2023, 4:06 PM./gradlew :gms:impl:build -Prest.model.compatibility=ignore
as recommended in the developer guide. I am getting the following error:
Project 'gms' not found in root project 'datahub'.Is the guide out of date? Also when I try to build the metadata-service I get the following error:
idl compatibility report:
Incompatible changes:
1) /collection/actions/batchIngest/parameters/entities/type: new enum added symbols DATA_MESH
2) com.linkedin.entity.Entity/value/com.linkedin.metadata.snapshot.Snapshot/ref/union/com.linkedin.metadata.snapshot.DataPlatformSnapshot/aspects/array/items/com.linkedin.metadata.aspect.DataPlatformAspect/ref/union/com.linkedin.dataplatform.DataPlatformInfo/type/com.linkedin.dataplatform.PlatformType/symbols: new enum added symbols DATA_MESH, breaks old readers
3) com.linkedin.entity.Entity/value/com.linkedin.metadata.snapshot.Snapshot/ref/union/com.linkedin.metadata.snapshot.DataPlatformSnapshot/aspects/array/items/com.linkedin.metadata.aspect.DataPlatformAspect/ref/union/com.linkedin.dataplatform.DataPlatformInfo/type/com.linkedin.dataplatform.PlatformType/symbols: new enum added symbols DATA_MESH, breaks old readers
[RS-COMPAT]: false
[MD-COMPAT]: false
[RS-I]:/collection/actions/batchIngest/parameters/entities/type: new enum added symbols DATA_MESH
[MD-I]:com.linkedin.entity.Entity/value/com.linkedin.metadata.snapshot.Snapshot/ref/union/com.linkedin.metadata.snapshot.DataPlatformSnapshot/aspects/array/items/com.linkedin.metadata.aspect.DataPlatformAspect/ref/union/com.linkedin.dataplatform.DataPlatformInfo/type/com.linkedin.dataplatform.PlatformType/symbols: new enum added symbols DATA_MESH, breaks old readers
[MD-I]:com.linkedin.entity.Entity/value/com.linkedin.metadata.snapshot.Snapshot/ref/union/com.linkedin.metadata.snapshot.DataPlatformSnapshot/aspects/array/items/com.linkedin.metadata.aspect.DataPlatformAspect/ref/union/com.linkedin.dataplatform.DataPlatformInfo/type/com.linkedin.dataplatform.PlatformType/symbols: new enum added symbols DATA_MESH, breaks old readers
busy-dream-36363
01/13/2023, 5:17 PMbusy-dream-36363
01/13/2023, 5:17 PMbusy-dream-36363
01/13/2023, 5:18 PMbusy-dream-36363
01/13/2023, 5:18 PMbusy-dream-36363
01/13/2023, 5:19 PMfaint-actor-78390
01/13/2023, 5:25 PMDataHub CLI version: 0.9.5.2
Python version: 3.9.12 (main, Apr 4 2022, 05:22:27) [MSC v.1916 64 bit (AMD64)]
average-dinner-25106
01/16/2023, 4:48 AMbland-orange-13353
01/16/2023, 1:12 PMpowerful-cat-68806
01/16/2023, 2:03 PMdatahub-frontend:
enabled: true
oidcAuthentication:
enabled: true
provider: okta
# clientId:
# secretRef: datahub-okta-client-secret
# secretKey: clientid
# # only needed if you would like to store the client secret in secret
# clientSecretRef:
# secretRef: datahub-okta-client-secret
# secretKey: clientsecret
oktaDomain: <http://jfrog.okta.com|jfrog.okta.com>
extraEnvs:
- name: AUTH_OIDC_ENABLED
value: true
- name: AUTH_OIDC_CLIENT_SECRET
value: xxxxxxxxxxxx
- name: AUTH_OIDC_BASE_URL
value: xxxxxxxxxxxx
- name: AUTH_OIDC_DISCOVERY_URI
value: <https://my_okta_domain/.well-known/openid-configuration>
- name: AUTH_OIDC_SCOPE
value: <mailto:xxxxx@jxxxx.com|xxxxx@jxxxx.com>
- name: AUTH_OIDC_BASE_URL
value: xxxxxxxxxxxxxxx
- name: AUTH_OIDC_CLIENT_ID
value: xxxxxxxxxxxxxxxx
fancy-rose-64137
01/16/2023, 3:54 PMCaused by: java.sql.SQLException: Incorrect string value: '\\xE2\\x8F\\xB3 Pi...' for column 'metadata' at row 1
polite-activity-25364
01/17/2023, 6:08 AMlimited-refrigerator-50812
01/17/2023, 10:12 AMrich-pager-68736
01/17/2023, 11:25 AM"Failed to resolve secret with name {match}. Aborting recipe execution."
After recreating those secrets it works again.gifted-knife-16120
01/17/2023, 12:04 PMbrainy-piano-85560
01/17/2023, 1:03 PMbetter-fireman-33387
01/17/2023, 1:14 PMfaint-hair-91313
01/17/2023, 1:40 PMelegant-state-4
01/17/2023, 3:44 PM./gradlew :metadata-ingestion:installDev
. I get the following error.
In file included from src/cxoApiType.c:11:
src/cxoModule.h:14:10: fatal error: 'Python.h' file not found
#include <Python.h>
cold-city-21137
01/17/2023, 4:08 PMcreamy-machine-95935
01/17/2023, 6:52 PM