hound-search/hound

Index is apparently limited to 4 GB

Open

#351 opened on 2020年10月1日

GitHub で見る
 (7 comments) (0 reactions) (0 assignees)JavaScript (5,470 stars) (606 forks)batch import
enhancementhelp wanted

説明

:wave: Hound developers!

I am trying to index a pretty large repo (144GB - all current sources of openSUSE), and unsurprisingly the index turns out to be larger than 4GB, thus I hit this fatal message:

https://github.com/hound-search/hound/blob/e3b1b43eb872e47af1de1b0e15d0ec3ac5c51dc4/codesearch/index/write.go#L561

Would it be possible / how hard would it be to support larger indexes?

I only had a brief look at read.go and it seems to me that 32 bit offsets are part of the index file format, so changing that would require re-indexing/converting/supporting two file formats, is that correct?

Thanks for all your efforts on Hound!

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

技術スタック
go
領域
backendsearch
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Go programming languageunderstanding of binary file formatsfamiliarity with Hound's index packageexperience with backward compatibility
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
15
調査方針
The issue is about supporting indexes larger than 4GB by changing the offset size from 32 bit to 64 bit in the index file format. Key files are codesearch/index/write.go (line 561) and read.go. The challenge is backward compatibility; consider supporting two file formats or a migration path. Review the 7 comments in the issue for any suggested approaches or known constraints. No linked PRs exist, so the solution may require designing a new version of the index format.