blocks|key|366472|text|使用lucene|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366473|http://lucene.apache.org/java/docs/|offset|length|366474|Java是一个完全用|366475|编写的高性能、全功能的文本搜索引擎库。它是一种适用于几乎任何需要全文搜索的应用程序的技术，尤其是跨平台。|blockquote|366476|366477|366478|它在java和.net中可用。它也可以在php中以zend框架模块的形式提供。|366479|Lucene做了你想做的(对搜索项进行索引)，你必须跟踪lucene索引，但它在性能方面比数据库搜索要好得多。顺便说一句，搜索是由lucene提供支持的。:D|366480|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|Z|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|13|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|16|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|C]]]]

Use lucene, 
<a href="http://lucene.apache.org/java/docs/" rel="noreferrer">http://lucene.apache.org/java/docs/</a>

<blockquote>
 Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform.
</blockquote>

It is available in java and .net. It is also in available in php in the form of a zend framework module.

Lucene does what you wanted(indexing of the searched items), you have to keep track of a lucene index but it is much better than doing a database search in terms of performance. BTW, SO search is powered by lucene. :D

blocks|key|364747|text|这取决于你的网站有多全面，以及你有多想自己做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364748|如果你正在运行一个小型网站的，没有添加自定义搜索的进一步可能性，让谷歌来做这项工作(也许添加一个sitemap)，并使用google+custom+search。|offset|length|style|BOLD|364749|如果您使用sql运行中型站点，请使用sql的搜索功能。|364750|如果您运行一些较重软件堆栈，如J2EE或.Net，请使用强大强大的搜索引擎Lucene或其.Net克隆lucene.Net|364751|如果您想从应用程序中对搜索进行抽象，并能够使用XML和JSON以一种与语言无关的方式对其进行查询，那么可以看看solr。Solr在后台运行lucene，但添加了一个很好的web界面。|364752|entityMap|0|LINK|mutability|MUTABLE|url|https://www.google.com/webmasters/tools/docs/en/protocol.html|1|http://www.google.com/coop/cse/|2|http://lucene.apache.org/java/docs/|3|http://incubator.apache.org/lucene.net/|4|http://lucene.apache.org/solr/^0|0|9|5|1C|7|0|1O|K|1|0|A|4|0|7|6|11|6|2|1F|A|3|0|F|24|1J|4|4|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@$D|17|E|18|1|19]|$D|1A|E|1B|1|1C]]|A|$]]|$1|H|3|I|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1G|8|@$D|1H|E|1I|F|G]]|9|@$D|1J|E|1K|1|1L]|$D|1M|E|1N|1|1O]]|A|$]]|$1|L|3|M|5|6|7|1P|8|@$D|1Q|E|1R|F|G]]|9|@$D|1S|E|1T|1|1U]]|A|$]]|$1|N|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]|X|$5|Q|R|S|A|$T|Y]]|Z|$5|Q|R|S|A|$T|10]]|11|$5|Q|R|S|A|$T|12]]]]

It depends on how comprehensive your web site is and how much you want to do yourself.

If you are running a a small website without further possibilities to add a custom search, let google do the work (maybe add a <a href="https://www.google.com/webmasters/tools/docs/en/protocol.html" rel="noreferrer">sitemap</a>) and use the <a href="http://www.google.com/coop/cse/" rel="noreferrer">google custom search</a>.

If you run a medium site with an sql engine use the search features of your sql engine.

If you run some heavier software stack like J2EE or .Net use <a href="http://lucene.apache.org/java/docs/" rel="noreferrer">Lucene</a>, a great, powerful search engine or its .Net clone <a href="http://incubator.apache.org/lucene.net/" rel="noreferrer">lucene.Net</a>

If you want to abstract your search from your application and be able to query it in a language neutral way with XML/HTTP and JSON APIs, have a look at <a href="http://lucene.apache.org/solr/" rel="noreferrer">solr</a>. Solr runs lucene in the background, but adds a nice web interface to it.

blocks|key|366482|text|您可能希望了解一下xapian和omega前端。它本质上是一个工具包，您可以在其上构建搜索功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|366483|entityMap|0|LINK|mutability|MUTABLE|url|http://xapian.org/|1|http://xapian.org/docs/omega/overview.html^0|9|6|0|G|5|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

You might want to have a look at <a href="http://xapian.org/" rel="nofollow noreferrer">xapian</a> and the <a href="http://xapian.org/docs/omega/overview.html" rel="nofollow noreferrer">omega</a> front end. It's essentially a toolkit on which you can build search functionality.

blocks|key|366187|text|实现这一点的最佳方法将取决于您如何构建页面。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366188|如果它们经常由许多不同的记录组成(就像我想象的那样)，那么索引方法可能会提供更好的结果，除非您投入大量工作在数据库端有效地重建页面。|366189|使用索引方法的缺点是周转时间。有一些变通方法(比如Google的sitemap+)，但要正确使用它们也很复杂。|366190|如果你使用数据库路径，也要知道现代搜索引擎系统如果有链接数据要处理的话会运行得更好，所以找到一个可以理解数据库中“页面”之间的链接的系统将会有积极的效果。|366191|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

The best way to approach this will depend on how you construct your pages.

If they're frequently composed from a lot of different records (as I imagine stack overflow pages are), the indexing approach is likely to give better results unless you put a lot of work into effectively reconstructing the pages on the database side.

The disadvantage you have with the indexing approach is the turn around time. There are workarounds (like the Google's sitemap stuff), but they're also complex to get right.

If you go with database path, also be aware that modern search engine systems function much better if they have link data to process, so finding a system which can understand links between 'pages' in the database will have a positive effect.

blocks|key|366508|text|如果你使用的是微软平台，你可以使用索引服务。这很容易与IIS网站集成。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366509|它具有所有的基本功能，如全文搜索，排名，排除和包括某些文件类型，您可以添加自己的元信息，以及通过元标签在html页面。|366510|在谷歌上搜索一下，你会发现很多！|366511|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If you are on Microsoft plattform you could use the Indexing service. This integrates very easliy with IIS websites. 

It has all the basic features like full text search, ranking, exlcude and include certain files types and you can add your own meta information as well via meta tags in the html pages.

Do a google and you'll find tons!

blocks|key|3374189|text|这与你的问题有点正交，但我强烈推荐RESTful搜索的想法。也就是说，为了执行从未执行过的搜索，网站将查询发布到/searches/。要重新运行搜索，网站将获取/searches/{some+id}|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3374190|关于这一点，可以找到一些很好的文档，例如here。|offset|length|3374191|(也就是说，我喜欢在可能的地方建立索引，尽管它是一种优化，因此可能还为时过早。)|3374192|entityMap|0|LINK|mutability|MUTABLE|url|http://woss.name/2007/07/22/convention-for-restful-search-in-rails/^0|0|K|4|0|0|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]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

This is somewhat orthogonal to your question, but I highly recommend the idea of a RESTful search. That is, to perform a search that has never been performed, the website POSTs a query to /searches/. To re-run a search, the website GETs /searches/{some id}

There are some good documents to be found regarding this, for example <a href="http://woss.name/2007/07/22/convention-for-restful-search-in-rails/" rel="nofollow noreferrer">here</a>.

(That said, I like indexing where possible, though it is an optimization, and thus can be premature.)

blocks|key|3161367|text|如果您的应用程序使用Java堆栈，并且您正在使用Hibernate，那么您可以使用Compass+Framework来维护数据库的可搜索索引。指南针框架在幕后使用Lucene。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3161368|唯一的问题是你不能复制你的搜索索引。因此，您需要使用集群数据库来保存索引表，或者使用Compass+Framework2.x中添加的较新的基于网格的索引存储机制。|3161369|entityMap|0|LINK|mutability|MUTABLE|url|http://hibernate.org/|1|http://www.compass-project.org/|2|http://lucene.apache.org/^0|O|9|0|15|H|1|29|6|2|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]|$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

If you application uses the Java EE stack and you are using <a href="http://hibernate.org" rel="nofollow noreferrer">Hibernate</a> you can use the <a href="http://www.compass-project.org" rel="nofollow noreferrer">Compass Framework</a> maintain a searchable index of your database. The Compass Framework uses <a href="http://lucene.apache.org" rel="nofollow noreferrer">Lucene</a> under the hood.

The only catch is that you cannot replicate your search index. So you need to use a clustered database to hold the index tables or use the newer grid based index storage mechanisms that have been added to the Compass Framework 2.x.

I want to implement search functionality for a website (assume it is similar to SO). I don't want to use Google search of stuff like that.

My question is:

How do I implement this?

There are two methods I am aware of:

<ol>
<li>Search all the databases in the application when the user gives his query.</li>
<li>Index all the data I have and store it somewhere else and query from there (like what Google does).</li>
</ol>

Can anyone tell me which way to go? What are the pros and cons?

Better, are there any better ways to do this?

How do I implement Search Functionality in a website?

我想实现一个网站的搜索功能(假设它类似于SO)。我不想用谷歌搜索那样的东西。我的问题是：我如何实现这一点？我知道有两种方法：在用户发出查询时搜索应用程序中的所有数据库。索引我拥有的所有数据，并将其存储在其他位置，然后从其他位置进行查询(就像谷歌所做的那样)。谁能告诉我该走哪条路？好处和坏处是什么？更好的是，有没有更好的方法呢？

问如何在网站中实现搜索功能？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在网站中实现搜索功能？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在网站中实现搜索功能？
EN