-
**Describe the bug**
A clear and concise description of what the bug is.
I get this error when I try to run the following code:
response = mq.index(index).search(q='', limit=K, search_method="lexic…
-
For example, #1849
When you corrupt your moarvm memory by doing un-thread-safe things, you get one of a variety of "MoarVM Panic: Internal bla bla", which gives you zero clue what might be going wr…
-
### Is your feature request related to a problem?
OpenSearch 2.10 introduced the ability to do [hybrid querying](https://opensearch.org/blog/hybrid-search/), where you can use multiple queries and no…
-
**Describe the bug**
When specifying `attributes_to_retrieve` and using Lexical search, tensor fields are not returned in the hits.
**To Reproduce**
Consider an index `my-index`, with fields:
-…
-
the following produces ConfigException.UnresolvedSubstitution;
I went through HOCON.md again, still have no answer; what am I missing, please?
```
{
test = [
{
some-id = 123…
-
# Search: Query Matching via Lexical, Graph, and Embedding Methods
An overview and comparison of the various approaches, with examples from industry search systems.
[https://eugeneyan.com/writing/se…
-
so in the search bar, or in the Search terms: of Detailed Search if you include any of the following characters in your search
" or { or }
you get a error
in this example i search for " and i am…
-
We were thinking that it would be much easier to find (grammatical) gloss tags if we separated grammatical from lexical glosses. Right now, it is still marginally doable, but once we have more data on…
-
`*lexic: word*`
Maybe even keep multiple around, one per search? Or is this not a good idea?
minad updated
3 years ago
-
For certain search terms like "a", "an", "the" or "in", "on", "at", it is better for a user to see a brief grammar explanation than any lexical entries. (It might be desirable to show _grammatical_ en…