Repository navigation
Ability to Override the Hive metastre LOG Configuration #528
Description
below configOverrides is not working for metastore-log4j2.properties
apiVersion: hive.stackable.tech/v1alpha1
kind: HiveCluster
metadata:
name: hive-postgres-s3
namespace: "data"
spec:
image:
productVersion: 3.1.3
clusterConfig:
listenerClass: external-stable
database:
connString: jdbc:postgresql://hms-pg-cluster:5432/hive
credentialsSecret: hive-credentials
dbType: postgres
s3:
reference: oss
metastore:
configOverrides:
metastore-log4j2.properties:
rootLogger.level: "DEBUG"
security.properties:
rootLogger.level: "DEBUG"
roleGroups:
default:
replicas: 1
Activity
CoderYellow commentedon Nov 2, 2024
Is there currently a way to customize the log level for the metastore? Can this be configured within the HiveCluster CRD? Without this capability, troubleshooting becomes significantly more challenging.
[-]Ability to Override the Hive ConfigMap Configuration[/-][+]Ability to Override the Hive metastre LOG Configuration[/+]sbernauer commentedon Nov 4, 2024
Hi @CoderYellow,
we don't support configOverrides on all files, so the
metastore-log4j2.propertiesis not supported.However, what you probably want to do is use the logging mechanism we have added to the platform, which allow you fine-grained control, regardless of the actual different logging implementations in all the different tools.
You can find the documentation here: https://docs.stackable.tech/home/stable/concepts/logging, the specific one for Hive metastore here: https://docs.stackable.tech/home/stable/hive/usage-guide/logging
Without having tested it, your config could look something like
sbernauer commentedon Nov 19, 2024
Hi @CoderYellow I see you reacted with a heart, am I correct to assume your problem is fixed? :)