On Mon, Oct 11, 2010 at 3:33 AM, Lukas Kahwe Smith <m...@pooteeweet.org>wrote:
> > On 11.10.2010, at 07:03, Israel Ekpo wrote: > > > I am currently working on a couple of bug fixes for the Solr PECL > extension > > that will be available in the next release 0.9.12 sometime this month. > > > > http://pecl.php.net/package/solr > > > > Documentation of the current API and features for the PECL extension is > > available here > > > > http://www.php.net/solr > > > > A couple of users in the community were asking when the PHP extension > will > > be moving from beta to stable. > > > > The API looks stable so far with no serious issues and I am looking to > > moving it from *Beta* to *Stable *on November 20 2010 > > > > If you are using Solr via PHP and would like to see any new features in > the > > extension please feel free to send me a note. > > > > I would like to incorporate those changes in 0.9.12 so that user can try > > them out and send me some feedback before the release of version 1.0 > > > > Thanks in advance for your response. > > > we already had some emails about this. > imho there are too many methods for specialized tasks, that its easy to get > lost in the API, especially since not all of them have written documentation > yet beyond the method signatures. > > also i do think that there should be methods for escaping and also > tokenizing lucene queries to enable "validation" of the syntax used etc. > > see here for a use case and a user land implementation: > http://pooteeweet.org/blog/1796 > > regards, > Lukas Kahwe Smith > m...@pooteeweet.org > > > > Thanks Lukas for your feed back. Could you clarify the part about too many methods for specialized task? From feedback that I have received so far, most users like the specialization and and a small fraction do not. So it might be a matter of preference. I decided to add the specialized methods in the SolrQuery class because at the time, that was what most of the users wanted to see in the API. They cannot be removed now. As per the documentation, all of the methods are documented with at least a brief heading or summary of what it is supposed to do. http://php.net/solr The user needs to understand first which query parameters they need to send to Solr and then they can use one of the SolrQuery methods for that purpose. Additional information is available from Solr Tutorials and the wiki itself. If one choses not to use a specialized method there is always the get(), set() and add() methods that allows you to pass the parameter values directly instead of using a specialized method for that parameter. For escaping queries, we already have the following method SolrUtils::escapeQueryChars http://www.php.net/manual/en/solrutils.escapequerychars.php http://www.php.net/manual/en/class.solrutils.php As per the tokenization, it is not clear exactly what you were referring to. I think it is best for the analysis of any of the tokens to be handled at the server layer. There are tools in the admin interface for analyzing and breaking down the query components into tokens. I also took a look at your blog but I could not immediately the use case you were referring to. A little more detail on this will be helpful. Thanks Lukas for your input. -- °O° "Good Enough" is not good enough. To give anything less than your best is to sacrifice the gift. Quality First. Measure Twice. Cut Once. http://www.israelekpo.com/
