-
Our `Rope` currently offers good performance for inserting or deleting large amounts of text from random positions in the `Rope`. Because `Rope` indexing is faster than `String` indexing, and we don't…
hawkw updated
7 years ago
-
## About
Coming from GH-53, there are a few backlog items, and there will be more.
## Details
- [ ] Features: Improve feature pages which are a bit thin, yet.
- Origin: https://github.com/crat…
amotl updated
1 month ago
-
I see lm-studio in general settings but not in QA settings.
So far it works great for chat with lm-studio but I can't get it to work with QA mode.
Being able to use a local LLM to index my entir…
-
-
### Search first
- [X] I searched and no similar issues were found
### What Happened?
I was using Logseq like I normally do for work, typing out notes in the new Journal entry today. After a few ho…
-
**Project description**
A query and indexing engine for Redis, providing secondary indexing, full-text search, vector similarity search and aggregations.
**Metadata**
* homepage URL: https://…
-
search по име да ползва fulltext indexing, тоест трябва ни indexing
Възможности:
http://blog.lostpropertyhq.com/postgres-full-text-search-is-good-enough
http://dev.mikamai.com/post/77171462056/easy-f…
-
Finding terms within X positions of the start of a field is currently possible via `intervals` queries, although it only really works for single-valued fields. It is not at all possible to find a ter…
-
Bill reported that he was unable to search for Keynes 12 in the global search box in the home page. The same is true for the "Text" field in Advanced Search. We need to see how @Conal-Tuohy setup the…
-
We should support incremental indexing of large corpuses. We can already save a corpus
to an io.Writer and load a corpus from an io.Reader, but once we have a large, saved
Corpus, there is no way to …