issues  

Messages by Thread

• Re: [PR] rfc: Implement an API for all Data File Formats [iceberg-rust] via GitHub
• Re: [PR] fix: add iceberg_type column for SqlCatalog [iceberg-python] via GitHub
• [I] fix(streaming-write): use rolling ParquetWriter + OutputStream.tell() for spec-correct file sizes and bounded memory [iceberg-python] via GitHub
• [I] Writing UTC timestamp to an iceberg table fails [iceberg-rust] via GitHub
• [I] Server-provided REST config is effectively remote client reconfiguration without a safe allow-list [iceberg] via GitHub
  • Re: [I] Server-provided REST config is effectively remote client reconfiguration without a safe allow-list [iceberg] via GitHub
  • Re: [I] Server-provided REST config is effectively remote client reconfiguration without a safe allow-list [iceberg] via GitHub
• [I] Mixed-prefix GCS batch deletes reuse the first object's client for the whole batch [iceberg] via GitHub
  • Re: [I] Mixed-prefix GCS batch deletes reuse the first object's client for the whole batch [iceberg] via GitHub
• [I] Creating a source can create external databases and tables [iceberg] via GitHub
  • Re: [I] Creating a source can create external databases and tables [iceberg] via GitHub
  • Re: [I] Creating a source can create external databases and tables [iceberg] via GitHub
  • Re: [I] Creating a source can create external databases and tables [iceberg] via GitHub
• [I] Full table and namespace property maps are mirrored into BigQuery metadata [iceberg] via GitHub
  • Re: [I] Full table and namespace property maps are mirrored into BigQuery metadata [iceberg] via GitHub
  • Re: [I] Full table and namespace property maps are mirrored into BigQuery metadata [iceberg] via GitHub
  • Re: [I] Full table and namespace property maps are mirrored into BigQuery metadata [iceberg] via GitHub
  • Re: [I] Full table and namespace property maps are mirrored into BigQuery metadata [iceberg] via GitHub
• [I] Maintenance locks are not owner-bound and can be cleared by another job [iceberg] via GitHub
  • Re: [I] Maintenance locks are not owner-bound and can be cleared by another job [iceberg] via GitHub
  • Re: [I] Maintenance locks are not owner-bound and can be cleared by another job [iceberg] via GitHub
  • Re: [I] Maintenance locks are not owner-bound and can be cleared by another job [iceberg] via GitHub
• [I] Spark direct path-based table access bypasses catalog mediation [iceberg] via GitHub
  • Re: [I] Spark direct path-based table access bypasses catalog mediation [iceberg] via GitHub
  • Re: [I] Spark direct path-based table access bypasses catalog mediation [iceberg] via GitHub
• [I] `remove_orphan_files` scopes `file_list_view` with raw string prefix matching [iceberg] via GitHub
  • Re: [I] `remove_orphan_files` scopes `file_list_view` with raw string prefix matching [iceberg] via GitHub
  • Re: [I] `remove_orphan_files` scopes `file_list_view` with raw string prefix matching [iceberg] via GitHub
  • Re: [I] `remove_orphan_files` scopes `file_list_view` with raw string prefix matching [iceberg] via GitHub
  • Re: [I] `remove_orphan_files` scopes `file_list_view` with raw string prefix matching [iceberg] via GitHub
• [I] Spark remove_orphan_files can be used as a delete primitive outside the target table [iceberg] via GitHub
  • Re: [I] Spark remove_orphan_files can be used as a delete primitive outside the target table [iceberg] via GitHub
  • Re: [I] Spark remove_orphan_files can be used as a delete primitive outside the target table [iceberg] via GitHub
• [I] Planning handles and idempotency keys are not normatively bound to principal, route, or request body [iceberg] via GitHub
  • Re: [I] Planning handles and idempotency keys are not normatively bound to principal, route, or request body [iceberg] via GitHub
  • Re: [I] Planning handles and idempotency keys are not normatively bound to principal, route, or request body [iceberg] via GitHub
  • Re: [I] Planning handles and idempotency keys are not normatively bound to principal, route, or request body [iceberg] via GitHub
• [I] Registration endpoints allow unrestricted `metadata-location` URIs, including `file://` [iceberg] via GitHub
  • Re: [I] Registration endpoints allow unrestricted `metadata-location` URIs, including `file://` [iceberg] via GitHub
  • Re: [I] Registration endpoints allow unrestricted `metadata-location` URIs, including `file://` [iceberg] via GitHub
• [I] The deprecated S3 signer spec does not declare authentication at all [iceberg] via GitHub
  • Re: [I] The deprecated S3 signer spec does not declare authentication at all [iceberg] via GitHub
  • Re: [I] The deprecated S3 signer spec does not declare authentication at all [iceberg] via GitHub
  • Re: [I] The deprecated S3 signer spec does not declare authentication at all [iceberg] via GitHub
• [I] The deprecated OAuth endpoint still documents unsafe token-exchange behavior [iceberg] via GitHub
  • Re: [I] The deprecated OAuth endpoint still documents unsafe token-exchange behavior [iceberg] via GitHub
  • Re: [I] The deprecated OAuth endpoint still documents unsafe token-exchange behavior [iceberg] via GitHub
  • Re: [I] The deprecated OAuth endpoint still documents unsafe token-exchange behavior [iceberg] via GitHub
• [I] Remote signing endpoints may escape the catalog base URI via absolute URIs [iceberg] via GitHub
  • Re: [I] Remote signing endpoints may escape the catalog base URI via absolute URIs [iceberg] via GitHub
  • Re: [I] Remote signing endpoints may escape the catalog base URI via absolute URIs [iceberg] via GitHub
  • Re: [I] Remote signing endpoints may escape the catalog base URI via absolute URIs [iceberg] via GitHub
  • Re: [I] Remote signing endpoints may escape the catalog base URI via absolute URIs [iceberg] via GitHub
  • Re: [I] Remote signing endpoints may escape the catalog base URI via absolute URIs [iceberg] via GitHub
• [I] Secret-bearing GET responses remain cacheable and ETag-revalidated [iceberg] via GitHub
  • Re: [I] Secret-bearing GET responses remain cacheable and ETag-revalidated [iceberg] via GitHub
  • Re: [I] Secret-bearing GET responses remain cacheable and ETag-revalidated [iceberg] via GitHub
  • Re: [I] Secret-bearing GET responses remain cacheable and ETag-revalidated [iceberg] via GitHub
• [I] `OutputFile.create()` is not atomic and can overwrite objects after the existence check [iceberg] via GitHub
  • Re: [I] `OutputFile.create()` is not atomic and can overwrite objects after the existence check [iceberg] via GitHub
  • Re: [I] `OutputFile.create()` is not atomic and can overwrite objects after the existence check [iceberg] via GitHub
  • Re: [I] `OutputFile.create()` is not atomic and can overwrite objects after the existence check [iceberg] via GitHub
  • Re: [I] `OutputFile.create()` is not atomic and can overwrite objects after the existence check [iceberg] via GitHub
• [I] `GoogleAuthManager` uses Google's obsolete generic credential loader without credential-type validation [iceberg] via GitHub
  • Re: [I] `GoogleAuthManager` uses Google's obsolete generic credential loader without credential-type validation [iceberg] via GitHub
  • Re: [I] `GoogleAuthManager` uses Google's obsolete generic credential loader without credential-type validation [iceberg] via GitHub
• [I] Restore/state paths still accept Java object deserialization [iceberg] via GitHub
  • Re: [I] Restore/state paths still accept Java object deserialization [iceberg] via GitHub
  • Re: [I] Restore/state paths still accept Java object deserialization [iceberg] via GitHub
  • Re: [I] Restore/state paths still accept Java object deserialization [iceberg] via GitHub
• [I] Credential refresh endpoint override accepts arbitrary absolute URLs and forwards catalog auth context [iceberg] via GitHub
  • Re: [I] Credential refresh endpoint override accepts arbitrary absolute URLs and forwards catalog auth context [iceberg] via GitHub
  • Re: [I] Credential refresh endpoint override accepts arbitrary absolute URLs and forwards catalog auth context [iceberg] via GitHub
• [I] Deletion-vector length and offset are not validated enough to stop crash or huge allocation attacks [iceberg] via GitHub
  • Re: [I] Deletion-vector length and offset are not validated enough to stop crash or huge allocation attacks [iceberg] via GitHub
• [I] `gcs.service.host` can redirect authenticated GCS traffic to arbitrary endpoints [iceberg] via GitHub
  • Re: [I] `gcs.service.host` can redirect authenticated GCS traffic to arbitrary endpoints [iceberg] via GitHub
  • Re: [I] `gcs.service.host` can redirect authenticated GCS traffic to arbitrary endpoints [iceberg] via GitHub
• [I] Equality-delete loading fully materializes delete files with avoidable heap amplification [iceberg] via GitHub
  • Re: [I] Equality-delete loading fully materializes delete files with avoidable heap amplification [iceberg] via GitHub
  • Re: [I] Equality-delete loading fully materializes delete files with avoidable heap amplification [iceberg] via GitHub
  • Re: [I] Equality-delete loading fully materializes delete files with avoidable heap amplification [iceberg] via GitHub
• [I] `IcebergGenerics` can leak unrequested columns and metadata when deletes are applied [iceberg] via GitHub
  • Re: [I] `IcebergGenerics` can leak unrequested columns and metadata when deletes are applied [iceberg] via GitHub
  • Re: [I] `IcebergGenerics` can leak unrequested columns and metadata when deletes are applied [iceberg] via GitHub
  • Re: [I] `IcebergGenerics` can leak unrequested columns and metadata when deletes are applied [iceberg] via GitHub
• [I] Freshness-aware table caching reuses state across config and credential boundaries [iceberg] via GitHub
  • Re: [I] Freshness-aware table caching reuses state across config and credential boundaries [iceberg] via GitHub
  • Re: [I] Freshness-aware table caching reuses state across config and credential boundaries [iceberg] via GitHub
• [I] REST responses trust file paths and storage credentials without central prefix or scheme enforcement [iceberg] via GitHub
  • Re: [I] REST responses trust file paths and storage credentials without central prefix or scheme enforcement [iceberg] via GitHub
  • Re: [I] REST responses trust file paths and storage credentials without central prefix or scheme enforcement [iceberg] via GitHub
  • Re: [I] REST responses trust file paths and storage credentials without central prefix or scheme enforcement [iceberg] via GitHub
• [I] Path-backed catalogs derive warehouse paths from unsanitized namespace and table names [iceberg] via GitHub
  • Re: [I] Path-backed catalogs derive warehouse paths from unsanitized namespace and table names [iceberg] via GitHub
  • Re: [I] Path-backed catalogs derive warehouse paths from unsanitized namespace and table names [iceberg] via GitHub
  • Re: [I] Path-backed catalogs derive warehouse paths from unsanitized namespace and table names [iceberg] via GitHub
  • Re: [I] Path-backed catalogs derive warehouse paths from unsanitized namespace and table names [iceberg] via GitHub
• [I] Metastore-controlled `metadata_location` is trusted without provenance checks [iceberg] via GitHub
  • Re: [I] Metastore-controlled `metadata_location` is trusted without provenance checks [iceberg] via GitHub
  • Re: [I] Metastore-controlled `metadata_location` is trusted without provenance checks [iceberg] via GitHub
  • Re: [I] Metastore-controlled `metadata_location` is trusted without provenance checks [iceberg] via GitHub
  • Re: [I] Metastore-controlled `metadata_location` is trusted without provenance checks [iceberg] via GitHub
• [I] REST /v1/config can pivot transport and auth settings for the full client session [iceberg] via GitHub
  • Re: [I] REST /v1/config can pivot transport and auth settings for the full client session [iceberg] via GitHub
  • Re: [I] REST /v1/config can pivot transport and auth settings for the full client session [iceberg] via GitHub
  • Re: [I] REST /v1/config can pivot transport and auth settings for the full client session [iceberg] via GitHub
• [I] Remote and metadata-driven class names reach unsafe constructor loading [iceberg] via GitHub
  • Re: [I] Remote and metadata-driven class names reach unsafe constructor loading [iceberg] via GitHub
  • Re: [I] Remote and metadata-driven class names reach unsafe constructor loading [iceberg] via GitHub
• [I] `bq_connection` is free-form and copied into BigQuery `connectionId` without policy validation [iceberg] via GitHub
  • Re: [I] `bq_connection` is free-form and copied into BigQuery `connectionId` without policy validation [iceberg] via GitHub
  • Re: [I] `bq_connection` is free-form and copied into BigQuery `connectionId` without policy validation [iceberg] via GitHub
• [I] The Key Vault client trusts any configured vault URL and reuses ambient Azure credentials [iceberg] via GitHub
  • Re: [I] The Key Vault client trusts any configured vault URL and reuses ambient Azure credentials [iceberg] via GitHub
• [I] Remotely supplied storage-credential config can override transport and factory behavior [iceberg] via GitHub
  • Re: [I] Remotely supplied storage-credential config can override transport and factory behavior [iceberg] via GitHub
  • Re: [I] Remotely supplied storage-credential config can override transport and factory behavior [iceberg] via GitHub
  • Re: [I] Remotely supplied storage-credential config can override transport and factory behavior [iceberg] via GitHub
• [I] Vended-credential refresh accepts arbitrary absolute URLs and reuses the catalog auth session [iceberg] via GitHub
  • Re: [I] Vended-credential refresh accepts arbitrary absolute URLs and reuses the catalog auth session [iceberg] via GitHub
  • Re: [I] Vended-credential refresh accepts arbitrary absolute URLs and reuses the catalog auth session [iceberg] via GitHub
• [I] Untrusted Azure storage authorities are turned into credential-bearing service endpoints [iceberg] via GitHub
  • Re: [I] Untrusted Azure storage authorities are turned into credential-bearing service endpoints [iceberg] via GitHub
  • Re: [I] Untrusted Azure storage authorities are turned into credential-bearing service endpoints [iceberg] via GitHub
• [I] S3 remote signer clients share auth and HTTP state across catalogs [iceberg] via GitHub
  • Re: [I] S3 remote signer clients share auth and HTTP state across catalogs [iceberg] via GitHub
  • Re: [I] S3 remote signer clients share auth and HTTP state across catalogs [iceberg] via GitHub
• [I] Vended ADLS credential selection collapses to storage-account granularity and ignores delegated prefixes [iceberg] via GitHub
  • Re: [I] Vended ADLS credential selection collapses to storage-account granularity and ignores delegated prefixes [iceberg] via GitHub
  • Re: [I] Vended ADLS credential selection collapses to storage-account granularity and ignores delegated prefixes [iceberg] via GitHub
• [I] INT96 dictionary-packed decode writes to the wrong byte offset [iceberg] via GitHub
  • Re: [I] INT96 dictionary-packed decode writes to the wrong byte offset [iceberg] via GitHub
  • Re: [I] INT96 dictionary-packed decode writes to the wrong byte offset [iceberg] via GitHub
• [I] Multiple custom decoders allocate heap memory directly from file-controlled sizes without defensive caps [iceberg] via GitHub
  • Re: [I] Multiple custom decoders allocate heap memory directly from file-controlled sizes without defensive caps [iceberg] via GitHub
  • Re: [I] Multiple custom decoders allocate heap memory directly from file-controlled sizes without defensive caps [iceberg] via GitHub
• [I] Arrow direct-memory allocation is effectively unbounded and scan allocators are not closed [iceberg] via GitHub
  • Re: [I] Arrow direct-memory allocation is effectively unbounded and scan allocators are not closed [iceberg] via GitHub
  • Re: [I] Arrow direct-memory allocation is effectively unbounded and scan allocators are not closed [iceberg] via GitHub
• [I] `Metrics` performs unsafe Java deserialization on a public serializable type [iceberg] via GitHub
  • Re: [I] `Metrics` performs unsafe Java deserialization on a public serializable type [iceberg] via GitHub
  • Re: [I] `Metrics` performs unsafe Java deserialization on a public serializable type [iceberg] via GitHub
• [PR] fix: accept UTC timestamps in parquet writer [iceberg-rust] via GitHub
  • Re: [PR] fix: accept UTC timestamps in parquet writer [iceberg-rust] via GitHub
  • Re: [PR] fix: accept UTC timestamps in parquet writer [iceberg-rust] via GitHub
  • Re: [PR] fix: accept UTC timestamps in parquet writer [iceberg-rust] via GitHub
  • Re: [PR] fix: accept UTC timestamps in parquet writer [iceberg-rust] via GitHub
  • Re: [PR] fix: accept UTC timestamps in parquet writer [iceberg-rust] via GitHub
  • Re: [PR] fix: accept UTC timestamps in parquet writer [iceberg-rust] via GitHub
  • Re: [PR] fix: accept UTC timestamps in parquet writer [iceberg-rust] via GitHub
• [I] Bug(schema): AssignFreshSchemaIDs Java Divergance [iceberg-go] via GitHub
  • Re: [I] Bug(schema): AssignFreshSchemaIDs Java Divergance [iceberg-go] via GitHub
• [I] Variant parsing is vulnerable to memory-DoS and malformed-input crashes [iceberg] via GitHub
  • Re: [I] Variant parsing is vulnerable to memory-DoS and malformed-input crashes [iceberg] via GitHub
  • Re: [I] Variant parsing is vulnerable to memory-DoS and malformed-input crashes [iceberg] via GitHub
  • Re: [I] Variant parsing is vulnerable to memory-DoS and malformed-input crashes [iceberg] via GitHub
  • Re: [I] Variant parsing is vulnerable to memory-DoS and malformed-input crashes [iceberg] via GitHub
  • Re: [I] Variant parsing is vulnerable to memory-DoS and malformed-input crashes [iceberg] via GitHub
  • Re: [I] Variant parsing is vulnerable to memory-DoS and malformed-input crashes [iceberg] via GitHub
  • Re: [I] Variant parsing is vulnerable to memory-DoS and malformed-input crashes [iceberg] via GitHub
• [PR] fix(table): tighten strict negative metrics checks [iceberg-go] via GitHub
  • Re: [PR] fix(table): tighten strict negative metrics checks [iceberg-go] via GitHub
• [PR] fix(test): align TestCreateTable existence check [iceberg-go] via GitHub
  • Re: [PR] fix(test): align TestCreateTable existence check [iceberg-go] via GitHub
  • Re: [PR] fix(test): TestCreateTable existence check failure [iceberg-go] via GitHub
• Re: [I] feat(table): match Java's DV planning validations in PlanFiles [iceberg-go] via GitHub
  • Re: [I] feat(table): match Java's DV planning validations in PlanFiles [iceberg-go] via GitHub
• Re: [PR] feat(storage): Add HDFS backend via opendal services-hdfs-native [iceberg-rust] via GitHub
  • Re: [PR] feat(storage): Add HDFS backend via opendal services-hdfs-native [iceberg-rust] via GitHub
  • Re: [PR] feat(storage): Add HDFS backend via opendal services-hdfs-native [iceberg-rust] via GitHub
  • Re: [PR] feat(storage): Add HDFS backend via opendal services-hdfs-native [iceberg-rust] via GitHub
  • Re: [PR] feat(storage): Add HDFS backend via opendal services-hdfs-native [iceberg-rust] via GitHub
  • Re: [PR] feat(storage): Add HDFS backend via opendal services-hdfs-native [iceberg-rust] via GitHub
• [PR] perf(upsert): prune destination scan via df partition-column ranges a… [iceberg-python] via GitHub
  • Re: [PR] perf(upsert): prune destination scan via df partition-column ranges a… [iceberg-python] via GitHub
  • Re: [PR] perf(upsert): prune destination scan via df partition-column ranges a… [iceberg-python] via GitHub
  • Re: [PR] perf(upsert): prune destination scan via df partition-column ranges a… [iceberg-python] via GitHub
  • Re: [PR] perf(upsert): prune destination scan via df partition-column ranges a… [iceberg-python] via GitHub
• Re: [I] Bug(literals): DecimalLiteral.Type() hardcodes precision 9 regardless of actual column type [iceberg-go] via GitHub
  • Re: [I] Bug(literals): DecimalLiteral.Type() hardcodes precision 9 regardless of actual column type [iceberg-go] via GitHub
  • Re: [I] Bug(literals): DecimalLiteral.Type() hardcodes precision 9 regardless of actual column type [iceberg-go] via GitHub
  • Re: [I] Bug(literals): DecimalLiteral.Type() hardcodes precision 9 regardless of actual column type [iceberg-go] via GitHub
• [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
  • Re: [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
  • Re: [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
  • Re: [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
  • Re: [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
  • Re: [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
  • Re: [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
  • Re: [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
  • Re: [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
  • Re: [PR] feat(catalog): add PurgeTable as optional interface for physical file deletion [iceberg-go] via GitHub
• [PR] Spark 4.1: Implement SupportsReportOrdering in scan to skip redundant sorts [iceberg] via GitHub
  • Re: [PR] Spark 4.1: Implement SupportsReportOrdering in scan to skip redundant sorts [iceberg] via GitHub
  • Re: [PR] Spark 4.1: Implement SupportsReportOrdering in scan to skip redundant sorts [iceberg] via GitHub
  • Re: [PR] Spark 4.1: Implement SupportsReportOrdering in scan to skip redundant sorts [iceberg] via GitHub
  • Re: [PR] Spark 4.1: Implement SupportsReportOrdering in scan to skip redundant sorts [iceberg] via GitHub
  • Re: [PR] Spark 4.1: Implement SupportsReportOrdering in scan to skip redundant sorts [iceberg] via GitHub
  • Re: [PR] Spark 4.1: Implement SupportsReportOrdering in scan to skip redundant sorts [iceberg] via GitHub

• Earlier messages
• Later messages