apache/iceberg

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

Open

#14,227 opened on 2025年10月1日

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

説明

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

コントリビューターガイド

技術スタック
javadocker
領域
backenddatabase
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
JavaApache IcebergDockerLog4j
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
70
調査方針
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.