hound-search/hound

Index is apparently limited to 4 GB

Open

#351 opened on Oct 1, 2020

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (606 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (5,470 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

: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!

Contributor guide

Research direction
Investigate the index file format in read.go and write.go, replace 32 bit offsets with 64 bit offsets, and ensure backward compatibility with existing indexes.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gobinary file formats
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20