I just entered a massive pull request (consisting of a couple of separate commits) for SOLR-75: https://github.com/sakaiproject/nakamura/pull/948
All integration tests are passing, but I expect other problems to show up after it's merged. Given the probable disruption, why am I asking for a merge now? The OAE currently depends on a snapshot build more-or-less randomly taken from the Solr/Lucene trunk a year ago. Now that a more stable version is finally available from the Solr/Lucene team, we should use it. Bugs have been fixed, and clustering and near-real-time options that have been added. Most importantly what we're running doesn't match any available online documentation, and we need all the development help we can get. There are other search changes that we'd like to get into OAE 1.5.0. But because the OAE relies so centrally on Solr/Lucene, it's difficult to maintain the Solr/Lucene version update on its own feature branch. Usually I prefer to err on the side of caution, but in this case I believe it's better to merge early in the development cycle. Best, Ray _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
