TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Bringing full text search to Elixir's Ecto

86 点作者 philippemnoel7 个月前

4 条评论

mati3657 个月前
That database sounds like scam created by junior programmers that invest the major part of their VC budget money into marketing instead of engineering. I don't believe that they are even fully aware of all functionality of ES that they are comparing to.
评论 #41953039 未加载
评论 #41954609 未加载
评论 #41952911 未加载
sandreas7 个月前
I recently did a quick research about fulltext engines and found it to be very frustrating.<p>The most promising with a comment &#x2F;note:<p><pre><code> ElasticSearch - good, but huge and strange licensing Meilisearch - my favorite, nothing to complain so far QuickWit - good but *nix only TypeSense - good but *nix only Manticore - untested but looks interestung ZincSearch - seems abandoned, issues with ES API compatibility Solr - interesting but a bit old fashioned Sphinx - DB based, old fashioned</code></pre>
评论 #41954219 未加载
评论 #41956218 未加载
yunusabd7 个月前
+1 for replacing ES with ParadeDB. I did this for one of my projects recently and it&#x27;s working just fine for my use case (FTS), with much less overhead. The DXP could use some improvement, but I think they&#x27;ll get there. Good to see ParadeDB getting more traction.
Dowwie7 个月前
There&#x27;s a pre-existing aws-s3 extension allowing for s3 object connectivity. A duckDB extension is very different from this in scope. Also, s3 file access seems to be referred to as data lake access? Confused.