You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello everyone, thanks for your work on this gem.
I'm looking forward to use it but our use-case is a bit different: we need to filter ~100 contents at a time, then we delete the index and go with the other 100 contents, and so on for thousands of times a day.
I was wondering, is it possible to use in memory indexing instead of writing on file?
Sorry, I think I meant to answer this, but then it totally slipped my mind 🤦♂️
Swapping the file index with the in-memory index is not something that makes sense to me, but making it configurable definitely sounds great! However, since it's very likely I'm going to archive the repo, this and other changes are better be implemented in forks.
hello everyone, thanks for your work on this gem.
I'm looking forward to use it but our use-case is a bit different: we need to filter ~100 contents at a time, then we delete the index and go with the other 100 contents, and so on for thousands of times a day.
I was wondering, is it possible to use in memory indexing instead of writing on file?
I saw that tantivy supports this use-case
https://docs.rs/tantivy/latest/tantivy/struct.Index.html#method.create_in_ram
I've never worked with Ruby and Rust extensions but I can dive into a solution if you tell me that's feasible
UPDATE: I've been playing a bit with the code and it seems that this change does most of the job
a-chris@9c47fc0
Is it something you would like to have on tantiny? Maybe making it configurable while creating a new Index object?
The text was updated successfully, but these errors were encountered: