"* New 'cursorMark' request param for efficient deep paging of sorted result sets. See http://s.apache.org/cursorpagination";
At the end of the linked doco there is an example that doesn't make sense to me, because it mentions "sort=timestamp asc" and is then followed by pseudo code that sorts by id only. I understand that cursorMark requires that "sort clauses must include the uniqueKey field", but is it really just 'include', or is it the only field that sort can be performed on? ie. can sort be specified as 'sort=timestamp asc, id asc'? I am assuming that if the index is changed between requests than we can still 'miss' or duplicate documents by not sorting on the id as the only sort parameter, but I can live with that scenario. cursorMark is still attractive to us since it will prevent the SolrCloud cluster from crashing when deep pagination requests are sent to it... I'm just trying to explore all the edge cases our business area are likely to consider. Ta, Greg On 27 February 2014 02:15, Simon Willnauer <sim...@apache.org> wrote: > February 2014, Apache Solr(tm) 4.7 available > > The Lucene PMC is pleased to announce the release of Apache Solr 4.7 > > Solr is the popular, blazing fast, open source NoSQL search platform > from the Apache Lucene project. Its major features include powerful > full-text search, hit highlighting, faceted search, dynamic > clustering, database integration, rich document (e.g., Word, PDF) > handling, and geospatial search. Solr is highly scalable, providing > fault tolerant distributed search and indexing, and powers the search > and navigation features of many of the world's largest internet sites. > > Solr 4.7 is available for immediate download at: > http://lucene.apache.org/solr/mirrors-solr-latest-redir.html > > See the CHANGES.txt file included with the release for a full list of > details. > > Solr 4.7 Release Highlights: > > * A new 'migrate' collection API to split all documents with a route key > into another collection. > > * Added support for tri-level compositeId routing. > > * Admin UI - Added a new "Files" conf directory browser/file viewer. > > * Add a QParserPlugin for Lucene's SimpleQueryParser. > > * Suggest improvements: a new SuggestComponent that fully utilizes the > Lucene suggester module; queries can now use multiple suggesters; > Lucene's FreeTextSuggester and BlendedInfixSuggester are now supported. > > * New 'cursorMark' request param for efficient deep paging of sorted > result sets. See http://s.apache.org/cursorpagination > > * Add a Solr contrib that allows for building Solr indexes via Hadoop's > MapReduce. > > * Upgrade to Spatial4j 0.4. Various new options are now exposed > automatically for an RPT field type. See Spatial4j CHANGES & javadocs. > https://github.com/spatial4j/spatial4j/blob/master/CHANGES.md > > * SSL support for SolrCloud. > > Solr 4.7 also includes many other new features as well as numerous > optimizations and bugfixes. > > Please report any feedback to the mailing lists > (http://lucene.apache.org/solr/discussion.html) > > Note: The Apache Software Foundation uses an extensive mirroring network > for distributing releases. It is possible that the mirror you are using > may not have replicated the release yet. If that is the case, please > try another mirror. This also goes for Maven access. >
