quickwit-oss/tantivy

Tantivy should work without a store/fieldnorm/position file

Open

#124 创建于 2017年4月24日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)Rust (8,354 star) (499 fork)batch import
enhancementgood first issue

描述

Currently tantivy creates empty file even if the schema does not requires them (e.g. no field in the schema is stored for instance). The segment reader also needlessly opens and mmaps these files. jwolfe lost a bit of time when writing a converter from a different search index to tantivy.

贡献者指南

技术栈
rust
领域
backend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Rust programmingfile I/O concepts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Examine the segment reader code in Tantivy that creates and opens store, fieldnorm, and position files. The issue suggests that these files are created even when the schema doesn't require them. Start by locating where these files are initialized (likely in the segment or index writer). Then, modify the logic to conditionally create and open them based on the schema's stored fields, field norms, and positions. Also review the reader side to avoid mmap'ing unnecessary files. Check the repository's git history for any partial attempts or discussions around this issue. Update existing tests to verify the new behavior.