brave-businessperson-3969
01/28/2022, 4:18 PMagreeable-plastic-37919
01/28/2022, 8:31 PMprehistoric-room-17640
02/01/2022, 1:41 PMagreeable-plastic-37919
02/01/2022, 5:11 PMsquare-machine-96318
02/03/2022, 1:03 AMsquare-machine-96318
02/03/2022, 2:38 AMbetter-orange-49102
02/03/2022, 3:03 PMagreeable-plastic-37919
02/03/2022, 3:35 PMbetter-orange-49102
02/04/2022, 9:02 AMhandsome-football-66174
02/04/2022, 2:58 PMgorgeous-dinner-4055
02/05/2022, 3:48 AMmetadata-ingest/src/datahub/metadata
subfolder where the metadata is built by translating the .pdl
files into avro
files. Is there any reason not to check those into our forked version of Datahub? Do those change often? Are there cross platform compilation issues? Conserving space?
The reason behind this question is that internally we use Bazel to build our dependencies, and instead of trying to publish whls(we don't have an internal pypi to host these whls 😞) we can directly import the code and create a dependency through the git source code in other repos.
We could publish the whls to S3 or as git packages, but before going down that route, just curious why we don't check them in.echoing-dress-35614
02/05/2022, 9:07 PM⠿ datahub-frontend-react Error 0.3s
⠸ kafka-setup Pulling 0.3s
⠿ broker Error 0.3s
⠿ elasticsearch-setup Error 0.3s
⠸ datahub-gms Pulling 0.3s
⠸ elasticsearch Pulling 0.3s
⠸ mysql Pulling 0.3s
⠿ datahub-actions Error 0.3s
no matching manifest for linux/arm64/v8 in the manifest list entries
echoing-dress-35614
02/05/2022, 10:16 PMMETADATA_SERVICE_AUTH_ENABLED
environment variable to the datahub-gms container that was started using quickstart - what's the preferred method to add this when using the quickstart config?breezy-noon-83306
02/06/2022, 6:44 PMfew-air-56117
02/07/2022, 10:16 AMwooden-football-7175
02/07/2022, 2:40 PMbusy-lion-43973
02/07/2022, 3:42 PMsticky-kite-42322
02/08/2022, 12:03 PMbillowy-jewelry-4209
02/08/2022, 7:33 PMred-accountant-48681
02/08/2022, 8:30 PMboundless-student-48844
02/09/2022, 7:04 AMdatahub-mae-consumer
image with tag v0.8.26
Execution failed for task ':metadata-jobs:mae-consumer-job:checkstyleMain'.
> Could not resolve all files for configuration ':metadata-jobs:mae-consumer-job:checkstyle'.
> Could not download antlr4-runtime.jar (org.antlr:antlr4-runtime:4.7)
> Could not get resource '<https://plugins.gradle.org/m2/org/antlr/antlr4-runtime/4.7/antlr4-runtime-4.7.jar>'.
> Could not GET '<https://plugins.gradle.org/m2/org/antlr/antlr4-runtime/4.7/antlr4-runtime-4.7.jar>'.
> Connection reset
It seems to be due to redirect of URL (303 response when wget). Do you have some idea how to fix this?prehistoric-dawn-23569
02/09/2022, 11:59 AMbetter-orange-49102
02/09/2022, 12:12 PMfew-air-56117
02/09/2022, 1:33 PMsquare-machine-96318
02/10/2022, 1:22 AMdelightful-sugar-63810
02/10/2022, 5:58 PMFailedMetadataChangeEvent_v4
FailedMetadataChangeProposal_v1
MetadataAuditEvent_v4
MetadataChangeEvent_v4
MetadataChangeLog_Timeseries_v1
MetadataChangeLog_Versioned_v1
MetadataChangeProposal_v1
I'm planning to define a retention policy for these topics. Does that sounds okay if I define a window that allows the records to get consumed, like 5-10 days? Are there any topics that are used as a (long term)source-of-truth data store by any component?agreeable-plastic-37919
02/10/2022, 6:44 PMusageStats = DatasetUsageStatisticsClass(
timestampMillis=1629840771000,
uniqueUserCount=10,
totalSqlQueries=20,
fieldCounts=[
DatasetFieldUsageCountsClass(
fieldPath="field1",
count=10
)
]
)
# Construct a MetadataChangeProposalWrapper object.
metadata_event = MetadataChangeProposalWrapper(
entityType="dataset",
changeType=ChangeTypeClass.UPSERT,
entityUrn=builder.make_dataset_urn("myplatform", "path.to.my.table"),
aspectName="datasetUsageStatistics",
aspect=usageStats,
)
# Emit metadata! This is a blocking call
emitter.emit(metadata_event)
ancient-apartment-23316
02/10/2022, 9:25 PMbrave-secretary-27487
02/11/2022, 10:25 AMMETADATA_SERVICE_AUTH_ENABLED
The docs state the following set the METADATA_SERVICE_AUTH_ENABLED environment variable to "true" for the datahub-gms AND datahub-frontend containers / pods.
While the docs on github suggest there are more steps to enable the meta data auth service.
found at (https://github.com/acryldata/datahub-helm/tree/master/charts/datahub/subcharts/datahub-frontend) and https://datahubproject.io/docs/introducing-metadata-service-authentication/
Should I follow the official docs or go with the github docs?agreeable-plastic-37919
02/11/2022, 1:01 PM