RediSearch – Redis Powered Search Engine
oss.redislabs.com
RediSearch – Redis Powered Search Engine
1–10 of 95 posts
Re: RediSearch – Redis Powered Search Engine
#2EDIT: I did read the article, though I overlooked the link to comparison with Elasticsearch.
Re: RediSearch – Redis Powered Search Engine
#3Any advantages over Elasticsearch? EDIT: I did read the article, though I overlooked the link to comparison with Elasticsearch.
Re: RediSearch – Redis Powered Search Engine
#4Re: RediSearch – Redis Powered Search Engine
#5Re: RediSearch – Redis Powered Search Engine
#6Any advantages over Elasticsearch? EDIT: I did read the article, though I overlooked the link to comparison with Elasticsearch.
Did you even read the article? There's a link in there whith benchmarks it against elasticsearch. Read the conclusion on: https://redislabs.com/blog/search-benchmarking-redisearch-vs...
Re: RediSearch – Redis Powered Search Engine
#7What is this "source available" thing in the first paragraph? You can see our source but can't touch it?
Redis Modules created by Redis Labs (e.g. RediSearch, RedisGraph, RedisJSON, RedisML, RedisBloom) are licensed under the Redis Source Available License (RSAL).
Here is their RSAL license: https://redislabs.com/wp-content/uploads/2019/09/redis-sourc...Re: RediSearch – Redis Powered Search Engine
#8Earlier quoted context omitted.
Did you even read the article? There's a link in there whith benchmarks it against elasticsearch. Read the conclusion on: https://redislabs.com/blog/search-benchmarking-redisearch-vs...
Elastic search adds a huge overhead over Lucene. I suspect the same is true for RediSearch. The test is not testing the engine, but rather the implementation of its distributed aspect.
Re: RediSearch – Redis Powered Search Engine
#9Any advantages over Elasticsearch? EDIT: I did read the article, though I overlooked the link to comparison with Elasticsearch.
Did you even read the article? There's a link in there whith benchmarks it against elasticsearch. Read the conclusion on: https://redislabs.com/blog/search-benchmarking-redisearch-vs...
1. What human languages does it support.
2. In these human languages how does stemming and decompounding work in your implementation.
3. how is word importance determined in your index - TF-IDF? other algorithm? Are least important words automatically dropped from queries?
4. Do you have ability to rank on both the stemmed/decompounded query/results and exact matches? So something like raw field access.
5. Can I create my own semantics - I remember seeing a post on here recently where someone had created a search engine (in Rust I think) that was faster than ElasticSearch but from what I could see you couldn't create your own field names so you were stuck searching in title, description, body, creationDate and a couple other fields which really decreases the usefulness.
I mean these are the things that right away spring to mind to ask about when someone tells me they have a new search engine, and when they show me look at my speed benchmarks I'm thinking "what am I supposed to do with this?"
on edit: formatting
on second edit: So I guess as in most things I am interested in how the product actually fulfills what should be its primary functionality, so how does the search engine function as a search engine, I suppose my questions could be answered with quick - our search engine has feature parity with ElasticSearch / Solr where features A, B, and C are concerned - features D and E will be supported in the future.
Re: RediSearch – Redis Powered Search Engine
#10Any advantages over Elasticsearch? EDIT: I did read the article, though I overlooked the link to comparison with Elasticsearch.
Did you even read the article? There's a link in there whith benchmarks it against elasticsearch. Read the conclusion on: https://redislabs.com/blog/search-benchmarking-redisearch-vs...