gifted-florist-55079
01/17/2023, 7:18 PMfaint-painting-38451
01/17/2023, 9:27 PMbland-lighter-26751
01/17/2023, 10:52 PMenough-monitor-24292
01/18/2023, 8:52 AMrhythmic-quill-75064
01/18/2023, 9:07 AMjava.lang.OutOfMemoryError: Java heap space
I am using datahub-helm 0.2.89 and I have to start from this version. Any idea ? Thanks.fresh-cricket-75926
01/18/2023, 10:46 AMrich-policeman-92383
01/18/2023, 11:31 AMcd datahub
git clone <https://github.com/datahub-project/datahub.git> .
git checkout tags/v0.9.6 -b datahub_v0.9.6
DATAHUB_VERSION=v0.9.6 COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 docker-compose -f docker/docker-compose.yml -f docker/docker-compose.override.yml -p datahub build datahub-frontend-react
Errorfierce-restaurant-41034
01/18/2023, 3:38 PMwonderful-author-3020
01/18/2023, 3:52 PMproud-policeman-19830
01/18/2023, 4:07 PMdatahub
for local dev on my M1
mac (using --version=v0.9.3
with docker quickstart), and it's all running fine. However, I just got my hands on a rather lovely SBC from khadas (an Edge 2 pro - 16GB ram 8 cores arm64), and even though this is well within the docker specs, it fails to run (looks like mysql-setup and kafka-setup failed), any ideas? Logfile in threadelegant-salesmen-99143
01/18/2023, 6:28 PM"ImportError: cannot import name 'Distribution' from 'pkg_resources' (unknown location)\n",
. Any idea why that might be happening?
They used to ingest successfully before, and the failes started about two weeks ago or soquaint-barista-82836
01/18/2023, 8:28 PMorg.apache.logging.log4j:log4j-core
version 2.14.0
was detected in Maven library manager
located at /var/lib/neo4j/lib/neo4j-logging-4.2.4.jar
and is vulnerable to CVE-2021-45105
, which exists in versions >= 2.13.0, < 2.17.0
.
The vulnerability was found in the Github Security Advisory with vendor severity: High
(NVD severity: Medium
).
This vulnerability has a known exploit available. Source: Github.
The vulnerability can be remediated by updating the library to any of the following versions 2.3.1, 2.12.3, 2.17.0
or higher, using mvn versions:use-latest-releases -Dincludes=org.apache.logging.log4j:log4j-core
.
The library is associated with the technology Apache Log4j
.
Is there a fix as part of deployment ?enough-monitor-24292
01/19/2023, 5:22 AMflat-agency-53385
01/19/2023, 4:00 PM{
"errors": [
{
"message": "An unknown error occurred.",
"locations": [
{
"line": 4,
"column": 3
}
],
"path": [
"createGlossaryTerm"
],
"extensions": {
"code": 500,
"type": "SERVER_ERROR",
"classification": "DataFetchingException"
}
}
],
"data": {
"createGlossaryTerm": null
},
"extensions": {}
}
This is the query and variables
#Create glossary term
mutation CreateGlossaryTerm($name:String!, $description: String, $urn: String){
createGlossaryTerm(input: {name: $name, description: $description, parentNode: $urn})
}
#Variables
{
"name":"firstcustkey",
"description": " Initial CustKey for a Line.",
"urn": "urn:li:glossaryNode:821e6ed3-756b-43da-805c-ce7ed1d02ee8"
}
This same query was working fine yesterday so I am not sure what changed. I have confirmed that the parentnode exists.late-helicopter-99742
01/19/2023, 4:20 PM@Relationship
in datahub. Please see thread for details. Please advise.colossal-smartphone-90274
01/19/2023, 4:40 PMkafkaSetupJob:
enabled: true
image:
repository: linkedin/datahub-kafka-setup
# tag: "v0.9.6" # defaults to .global.datahub.version
resources:
limits:
cpu: 500m
memory: 1024Mi
requests:
cpu: 300m
memory: 768Mi
securityContext:
runAsUser: null
podSecurityContext:
fsGroup: null
runAsUser: null
podAnnotations: {}
extraEnvs:
- name: DATAHUB_USAGE_EVENT_NAME
value: "DataHub_UsageEvent_JSON_v1"
- name: PLATFORM_EVENT_TOPIC_NAME
value: "DataHub_PlatformEvent_JSON_v1"
- name: METADATA_CHANGE_EVENT_NAME
value: "DataHub_MetadataChangeEvent_JSON_v4"
- name: METADATA_AUDIT_EVENT_NAME
value: "DataHub_MetadataAuditEvent_JSON_v4"
- name: FAILED_METADATA_CHANGE_EVENT_NAME
value: "DataHub_FailedMetadataChangeEvent_JSON_v4"
- name: METADATA_CHANGE_PROPOSAL_TOPIC_NAME
value: "DataHub_MetadataChangeProposal_JSON_v1"
- name: METADATA_CHANGE_LOG_VERSIONED_TOPIC_NAME
value: "DataHub_MetadataChangeLog_Versioned_JSON_v1"
- name: FAILED_METADATA_CHANGE_PROPOSAL_TOPIC_NAME
value: "DataHub_FailedMetadataChangeProposal_JSON_v1"
- name: METADATA_CHANGE_LOG_TIMESERIES_TOPIC_NAME
value: "DataHub_MetadataChangeLog_Timeseries_JSON_v1"
elegant-state-4
01/19/2023, 6:20 PM./gradlew build
?echoing-needle-51090
01/20/2023, 5:02 AMkind-dusk-91074
01/20/2023, 7:02 AMelegant-salesmen-99143
01/20/2023, 8:34 AMechoing-needle-51090
01/20/2023, 9:24 AMcuddly-plumber-64837
01/20/2023, 2:10 PMcreamy-tent-10151
01/20/2023, 7:19 PMbetter-fireman-33387
01/22/2023, 11:41 AMhallowed-shampoo-52722
01/22/2023, 6:43 PMthankful-morning-85093
01/23/2023, 6:57 AMgroups
is blank now. I tried using datahub user to assign my user Admin and then login using my user. I still did not have admin privileges.stocky-energy-24880
01/23/2023, 11:57 AMdatahub docker quickstart
on M1 Mac OS.
is this already a known issue?
Any suggestion or work around?delightful-barista-90363
01/23/2023, 3:06 PMelegant-salesmen-99143
01/23/2023, 5:07 PMdelightful-sunset-48960
01/23/2023, 5:30 PM