> Sorry for the delay in my reply. I have been working on the features yet to > be added to the plugin and this is the current status of the project: > I managed to fix the pagination of results, in order to retrieve a specified > number of results per page. Previously, the plugin retrieved all Solr results > that matched the query, and paginated them afterwards (which wasn’t very > efficient). > > There was a problem with wildcard searching (Solr allows it by default, > however due to the fact that I am using the existing DefaultQueryParser, not > all wildcards worked). But I managed to fix this, and Solr wildcards now work.
Nice. I'll take a look at it. > There is now a trac-admin command to generate a Solr schema at the desired > location (I followed your advice and allowed the user to provide a path via > the Terminal). This works, the schema can be generated, however there is a > problem which I am hoping on fixing tomorrow. The user can provide a schema > path when using the command, however I also need the path when instantiating > the Sunburnt instance, and at the moment the path is not updated in the > module that deals with Sunburnt. So once I fix this, the plugin should be > able to use the generated schema for Solr requests. Based on the sunburnt docs[1]: schemadoc: By default, sunburnt will query the solr instance for its currently active schema. If you want to use a different schema for any reason, pass in a file object here which yields a schema document. Is there a specific reason why you need the path to schema file when instantiating sunburnt instance? Anze [1] http://opensource.timetric.com/sunburnt/connectionconfiguration.html
