Re: edismax available in solr 3.1?
See this http://www.gettingahead.co.in/blogwp/2011/03/technical/solr/shalini/some-info-about-extended-dismax-query-parser/ - Thanx: Grijesh www.gettinhahead.co.in -- View this message in context: http://lucene.472066.n3.nabble.com/edismax-available-in-solr-3-1-tp2910613p2922128.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: edismax available in solr 3.1?
It's already much better than the old dismax, and probably more stable. If you do not require the ability to lock down what fields people should be allowed to search for, I suggest you start using it right away. If you require to lock that down, I suggest you help out finishing that part of eDismax and then use it :) -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com On 10. mai 2011, at 01.05, cyang2010 wrote: Is it a formal feature that solr 3.1 support? Or still as experimental feature? If it is experimental feature, i would still be hesitating to use it. -- View this message in context: http://lucene.472066.n3.nabble.com/edismax-available-in-solr-3-1-tp2910613p2920975.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: edismax available in solr 3.1?
Jan, is there already an issue for that? It's already much better than the old dismax, and probably more stable. If you do not require the ability to lock down what fields people should be allowed to search for, I suggest you start using it right away. If you require to lock that down, I suggest you help out finishing that part of eDismax and then use it :) -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com On 10. mai 2011, at 01.05, cyang2010 wrote: Is it a formal feature that solr 3.1 support? Or still as experimental feature? If it is experimental feature, i would still be hesitating to use it. -- View this message in context: http://lucene.472066.n3.nabble.com/edismax-available-in-solr-3-1-tp29106 13p2920975.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: edismax available in solr 3.1?
: It's already much better than the old dismax, and probably more stable. : If you do not require the ability to lock down what fields people should : be allowed to search for, I suggest you start using it right away. If : you require to lock that down, I suggest you help out finishing that : part of eDismax and then use it :) Right ... the reason it's marked experimental in 3.1 is because there is are still open questions as to what the default behavior should be, and what new params should be added to change that behavior, which may change between now and whenever edismax is no longer marked experimental But the code most certainly works, and works well -- otherwise we wouldn't have included it in 3.1... https://issues.apache.org/jira/browse/SOLR-2058 https://issues.apache.org/jira/browse/SOLR-2368 -Hoss
Re: edismax available in solr 3.1?
Is it a formal feature that solr 3.1 support? Or still as experimental feature? If it is experimental feature, i would still be hesitating to use it. -- View this message in context: http://lucene.472066.n3.nabble.com/edismax-available-in-solr-3-1-tp2910613p2920975.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: edismax available in solr 3.1?
is edixmax available in solr 3.1? I don't see any documentation about it. if it is, does it support the prefix and fuzzy query? Yes and yes. See snippet taken from changes.txt New Features -- * SOLR-1553: New dismax parser implementation (accessible as edismax) that supports full lucene syntax, improved reserved char escaping, fielded queries, improved proximity boosting, and improved stopword handling. Note: status is experimental for now. (yonik)
edismax available in solr 3.1?
Hi, is edixmax available in solr 3.1? I don't see any documentation about it. if it is, does it support the prefix and fuzzy query? Thanks, cy -- View this message in context: http://lucene.472066.n3.nabble.com/edismax-available-in-solr-3-1-tp2910613p2910613.html Sent from the Solr - User mailing list archive at Nabble.com.