Solr1.3

Solr 1.3 has not yet been released.

If you found a link to this page in some documentation it was there to alert you to the fact that it described a feature that is expected to be included in the Solr 1.3 release when it eventually happens. Jira can show you issues that have been (or hope to be) incorporated into the 1.3 release

As preparations for the 1.3 release are made, this wiki will be used for any strategic planning.

After the 1.3 release is made, this wiki will provide some information about the release

About the release date ( from the mailing archives): There isn't a specific date so far, but I'd like to say that only once in the year or so I've been working with the SVN head build of Solr have I noticed a bug get committed. And it was fixed very quickly once it was found. I think if you need to have development features you're probably safe to use the SVN head, but remember that it is dev, and you should *always* test new builds before actually using them.

Notes About The Release

@Deprecation

In Solr 1.3, many classes were moved around. Although classes compiled against 1.2 will run in 1.3, updating class references is recommended.

Specifically:

• many classes from org.apache.util moved to org.apache.common.util

• many classes from org.apache.solr.request moved to org.apache.solr.common.params

• org.apache.solr.request.StandardRequestHandler moved to org.apache.solr.handler.StandardRequestHandler and is a subclass of org.apache.solr.handler.SearchHandler

• org.apache.solr.request.DisMaxRequestHandler moved to org.apache.solr.handler.DisMaxRequestHandler and deprecated in favor of adding 'defType=dismax' to StandardRequestHandler init params

TODO: Items Before the Release

TODO: Misc

• update example (single and multicore) solrconfig.xml and schemaxml files to make sure they use "best practices" (ie: remove references to deprecated classes like DisMaxRequestHandler)

• review the various things that put the "experimental" warning in the response ... decide if they are still experimental.

• resolve multicore logging prefix. I think otis suggested moving to the end for consistent log file parsers  core.log.info(core.getLogId()+ ... 

• code coverage reports are generally low, but some of the new classes in 1.3 that have frighteningly low coverage -- in many cases these seem like pretty important classes and/or high profile plugins. numbers below as of May 26...

  • BinaryResponseWriter (66.7%)

  • BoostedQuery (53.8%)

  • BoostedQuery.CustomScorer (50%)

  • DocumentBuilder (35%)

  • FastInputStream (52.5%)

  • FastOutputStream (67.3%)

  • FastWriter (31%)

  • FieldQParserPlugin (60%)

  • HttpCommComponent (59.2%)

  • HttpCommComponent.SimpleSolrResponse (50%)

  • LuceneQueryOptimizer (7.9%)

  • MoreLikeThisComponent (23.8%)

  • MoreLikeThisHandler (18.8%)

  • MoreLikeThisHandler.InterestingTerm (0%)

  • MoreLikeThisHandler.MoreLikeThisHelper (9.6%)

  • MultiCore (41.3%)

  • MultiCoreHandler (49.5%)

  • PHPResponseWriter (0%)

  • PHPSerializedResponseWriter (0%)

  • PHPSerializedWriter (0%)

  • PHPWriter (0%)

  • QueryComponent (63.1%)

  • QueryDocValues (0%)

  • QueryElevationComponent (76.7%)

  • SearchComponent (53.3%)

  • ShardDoc (0%)

  • ShardFacetCount (0%)

  • ShardFieldSortedHitQueue (57.3%)

  • ShardFieldSortedHitQueue.ShardComparator (66.7%)

  • SolrDocument (64.1%)

TODO: User Docs

SearchComponents

• does SearchComponent wiki page still need work?

Pluggable Query Parsers

• mention new parser selection syntax on SolrQuerySyntax

• mention how to write custom ones on SolrPlugins

TODO: SolrJ

This will be the first official release - we should make sure the API is something we want to live with...

currently only:

• q.addSortField( name, order );

  • no

  q.setSortField( name, order );

TODO: Audit APIS of Major Additions since 1.2

There have been a lot of major changes since 1.2, we should audit the APIs to make sure they are resonable:

• solrj

• multi-core

• search components

  • are we happy with ResponseBuilder.java? Are the correct fields public/private?

  • are we happy with the way "last-components" and "first-components" works?

• distributed search