apache/iceberg

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

Open

#14227 opened on Oct 1, 2025

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Java (5,146 stars) (1,915 forks)batch import
buggood first issue

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

Tech stack
javadocker
Domain
backenddatabase
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaApache IcebergDockerLog4j
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate how CATALOG LOG4J LOGLEVEL is currently used in the iceberg rest fixture Docker image. The issue reports that setting this enviroment variable to WARN does not suppress INFO logs. Look at the Dockerfile and entrypoint scripts (likely under docker/ or in the rest fixture module) to understand how log4j is configured. Check if there are multiple log4j configuration files or if the variable is passed to a JVM argument. Alternatively, consider adding support for a more granular logging environment variable, e.g., ICEBERG LOG LEVEL, that sets the log level for specific packages like org.apache.iceberg. The goal is to allow users to control logging levels without modifying the image. See issue #14227 for details.