Arthur, You should be able to use filters in your percolator queries so for example you can use a term/terms filter. Also, in ES 1.0 you can shard the percolator query index out so that percolation can distribute that load around for better scalability. The best way is to experiment with it: http://www.elasticsearch.org/downloads/1-0-0-RC1.
I actually worked for a company that did content classification this way, and the percolator was a perfect fit for that use-case. On Tuesday, January 21, 2014 10:01:36 AM UTC-5, Arthur Denning wrote: > > I am considering using the percolator API to classify document, namely, by > posting query like "football", "art" to the percolator, and then when > adding new documents, percolator should return the right tags. My concerns > is, suppose there is thousands of tag to be identified in this way, would > it be a performance nightmare? Is there thousands of query that is > implicitly running behind the scene? > > And what would be the recommended way to tackle these kind of > classification problem in Elasticsearch? > > It seems that Lucene has a classification api. Is it already integrated > elsewhere in Elasticsearch? Is there any roadmap concerning its > implementation? > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a81c8c74-06a2-452c-8c82-3b0358d18380%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
