blocks|key|314700|text|皮索尔解决了你的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|314701|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.apache.org/solr/SolPython^0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://wiki.apache.org/solr/SolPython" rel="nofollow">pysolr</a> solves your problem.

blocks|key|794952|text|因此，我还没有尝试过，但是http://tenderlove.github.com/texticle/似乎暗示，如果您能够在空间限制内适应，可以使用本机pgsql全文搜索。whoosh的问题在于，您将遇到磁盘空间及其在heroku规则中的持久性问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|794953|另一件事是按照dev+docs：http://devcenter.heroku.com/articles/full-text-search的建议使用加载项。|794954|至于模式，您基本上必须执行全文搜索，并获取记录的数据/ids，然后根据全文结果查询数据存储区(mongo)以获得完整的数据集。这是一个手工过程，但没有什么是太奇怪的。如果搜索不需要完整的记录，您通常可以使用全文信息存储重要的数据，但这会增加全文索引的大小。|794955|entityMap|0|LINK|mutability|MUTABLE|url|http://tenderlove.github.com/texticle/|1|http://devcenter.heroku.com/articles/full-text-search^0|D|12|0|0|G|1H|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

So I've not tried it, but <a href="http://tenderlove.github.com/texticle/" rel="nofollow">http://tenderlove.github.com/texticle/</a> seems to imply that you can use native pgsql fulltext search if you can fit within the space limits. The trouble with whoosh is that you're going to run into issues with disk space and its persistence within heroku rules.

The other thing to do is to work with the add ons as suggested via the dev docs:
<a href="http://devcenter.heroku.com/articles/full-text-search" rel="nofollow">http://devcenter.heroku.com/articles/full-text-search</a>

As for patterns, you basically have to do the fulltext search and get back data/ids of records and then query your data store (mongo) for the full dataset based on the fulltext results. It's a manual process, but nothing that's too strange. If the search doesn't need full records, you can usually get away with stashing the important data with the fulltext information, but that'll increase the size of your fulltext indexing.

blocks|key|794985|text|您考虑过使用Apache+SolR吗？我认为这是免费文本搜索引擎的最佳解决方案，它是免费的、开源的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|794986|要从python中使用SolR，我推荐您使用MySolr库。比pysolr更快更容易使用(您可以看到一些stats+这里)|offset|length|794987|entityMap|0|LINK|mutability|MUTABLE|url|http://mysolr.redtuna.org/|1|http://moliware.com/static/docs/mysolr/user/benchmark.html^0|0|M|6|0|1M|2|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]|$D|U|E|V|1|W]]|A|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]|N|$5|I|J|K|A|$L|O]]]]

Have you considered using Apache SolR? I think it's the best solution for a free-text search engine, it's free and open source.

To use SolR from python I recommend you the <a href="http://mysolr.redtuna.org/" rel="nofollow">MySolr</a> library. Is quite faster and easier to use than pysolr (you can see some stats <a href="http://moliware.com/static/docs/mysolr/user/benchmark.html" rel="nofollow">here</a>)

I am looking to implement (free as in beer) full text searching on a small application on Heroku (minimal number of users, limited dataset). However, I am struggling to find a best pattern for doing so, one option is to use the 10mb limit of xeround, while it lasts (we may exceed this in the near future), the second is to somehow roll my own full text search on MongoDB or CouchDB.

The documents in this application are archived emails that I wish to make searchable from a mailing list, there are approximately 10k such emails, plain text, roughly 700bytes per.

I would prefer fuzzy search capabilities, thus the push for whoosh.

Among my requirements (I should have mentioned earlier, is for it to be free!)

I have not found any patterns for using whoosh with MongoDB in a python, flask application. 

Can anyone provide more information on how to handle full text search in a small heroku, python application?

Full Text Search on Heroku, database and or indexer selection?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我希望在Heroku (用户数量最少、数据集有限)上实现(免费的，在beer中)全文搜索。然而，我很难找到这样做的最佳模式，一种选择是使用10 my的干涉仪限制，当它持续时(在不久的将来我们可能会超过这一点)，第二种方法是以某种方式在MongoDB或CouchDB上滚动我自己的全文搜索。这个应用程序中的文件是存档的电子...

问全文搜索Heroku，数据库和或索引器选择？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问全文搜索Heroku，数据库和或索引器选择？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问全文搜索Heroku，数据库和或索引器选择？
EN