ParquetWriter/ParquetReader should parse options directly from supplied Configuration
- 主要语言
- Java
- 星标
- 3.1k
- 派生
- 1.6k
- 平均合并
- 3 天 12 小时
- 30 天内合并 PR
- 33
描述
As a Parquet user, my expectation is that ParquetWriter/ParquetReader will automatically parse any options passed in the supplied Configuration. For example:
```
Configuration conf = new Configuration();
conf.setBoolean(ParquetOutputFormat.BLOOM_FILTER_ENABLED, true);
ParquetWriter writer = AvroParquetWriter.builder(path)
.withSchema(Car.SCHEMA$)
.withConf(conf)
.build();
```
However, the above code results in a ParquetWriter where `bloomFilterEnabled` is set to false-the expected way to configure this is to use `ParquetWriter#withBloomFilterEnabled` directly.
IMO, when `ParquetWriter#withConf` is invoked, it should also delegate to `encodingPropsBuilder` and set any Configured properties.
**Reporter**: [Claire McGinty](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=clairemcginty) / @clairemcginty
#### PRs and other links:
- [GitHub Pull Request #1157](https://github.com/apache/parquet-mr/pull/1157)
**Note**: *This issue was originally created as [PARQUET-2351](https://issues.apache.org/jira/browse/PARQUET-2351). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*
贡献指南
这个仓库没有索引到贡献指南
调研方向
从 ParquetWriter 和 ParquetReader 开始,重点关注 withConf 以及示例中提到的配置选项 ParquetOutputFormat.BLOOM_FILTER_ENABLED。查看 GitHub Pull Request #1157,并验证提供的 Configuration 值会被遵循,而不是要求使用直接的 builder 选项。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java
- 领域
- data-engineering
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100