apache/iceberg

INFO logs are getting flooded in iceberg-rest-fixture image

Closed

#14,227 opened on Oct 1, 2025

View on GitHubContributor guide
 (11 comments) (0 reactions) (0 assignees)Java (1,915 forks)batch import
buggood first issue

Repository metrics

Stars
 (5,146 stars)
PR merge metrics
 (Avg merge 10d 22h) (164 merged PRs in 30d)

Description

Apache Iceberg version

1.10.0 (latest release)

Query engine

Trino

Please describe the bug 🐞

The container logs are getting flooded with lots of INFO logs related to commits etc. in latest & older iceberg-rest-fixture image with postgres backing store. Tried to set env var CATALOG_LOG4J_LOGLEVEL: WARN but it didn't help. Kindly provide some mechanism to set the log levels - this will improve performance & focus on warn/errors quickly Example: [qtp1239807799-6590] INFO org.apache.iceberg.BaseMetastoreCatalog - Table loaded by catalog: rest_backend.tablename [qtp1239807799-6590] INFO org.apache.iceberg.BaseMetastoreTableOperations - Successfully committed to table tablename in 12 ms [qtp1239807799-6590] INFO org.apache.iceberg.BaseMetastoreTableOperations - Refreshing table metadata from new version:

Willingness to contribute

  • I can contribute a fix for this bug independently
  • I would be willing to contribute a fix for this bug with guidance from the Iceberg community
  • I cannot contribute a fix for this bug at this time

Contributor guide

Research direction
Investigate how to set log4j log levels in the iceberg rest fixture Docker container. Check the Dockerfile for log4j configuration, and see if an environment variable like CATALOG LOG4J LOGLEVEL is supported. Consider adding a mechanism to pass arbitrary log4j properties via env vars or a config file.
Tech stack
javadocker
Domain
backenddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
DockerJava logging basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70