Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Breaking change in Avro 1.12.1 affects parquet-avro users: logical types now deserialize to different Java types

未关闭
#3,515 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
技术栈
java

调研方向

从 issue 的 AVRO-3989 链接以及此处描述的 ReflectData、SpecificData 和 GenericRecord 行为开始;没有指定 parquet-java 文件或测试。比较 Avro 1.12.0 和 1.12.1 对所列逻辑类型的处理方式,然后与 maintainers 确定预期的更改或文档,再定义完成的标准。

由索引模型根据 Issue 内容生成。

描述

Summary

Avro 1.12.1 introduces a breaking change that affects parquet-avro users. Multiple logical types are now deserialized to their proper Java types instead of their underlying primitive types when using ReflectData, causing ClassCastException in existing code.

Background

Problem

The fix in AVRO-3989 changed the deserialization behavior for ALL logical types. When using within parquet-avro ReflectData or SpecificData classes, these fields now return their logical Java type objects instead of their underlying primitive types from GenericRecord.

Affected logical types and conversions:
Logical Type Old Type (≤1.12.0) New Type (1.12.1)
timestamp-millis Long Instant
timestamp-micros Long Instant
date Integer LocalDate
time-millis Integer LocalTime
time-micros Long LocalTime
local-timestamp-millis Long LocalDateTime
local-timestamp-micros Long LocalDateTime
uuid String UUID
decimal ByteBuffer BigDecimal

This breaks existing code that expects primitive values:

// This used to work in Avro 1.12.0
Long timestamp = (Long) genericRecord.get("timestamp_field");
Integer date = (Integer) genericRecord.get("date_field");
String uuid = (String) genericRecord.get("uuid_field");

// In Avro 1.12.1, all of these throw ClassCastException
// because values are now Instant, LocalDate, UUID, etc.

Impact

  • Widespread breakage: Affects anyone using parquet-avro with ANY logical types
  • Code that has worked for years suddenly breaks after a patch version update
  • The breaking nature wasn't clearly documented in Avro's changelog
  • This is a significant behavior change that affects the entire logical type system

Heads up for future avro updates

I apologize if this isn't the right place to report this, please feel free to redirect me if there's a better venue for this discussion. My main goal is to ensure that when parquet-java does consider updating Avro, the team and users are aware of this significant behavioral change.

For Current Users

If you're using parquet-avro and explicitly upgrading Avro to 1.12.1+ in your project, be aware of this breaking change. You'll need to update code that reads logical type fields from GenericRecord.

主要语言
Java
星标
3.1k
派生
1.6k
平均合并
4 天 12 小时
30 天内合并 PR
28

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/parquet-java 的其他 Issue

查看 apache/parquet-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。