svn commit: r1855512 - /lucene/cms/trunk/content/core/corenews.mdtext

[ji...@apache.org]

Author: jimczi
Date: Thu Mar 14 11:42:19 2019
New Revision: 1855512

URL: http://svn.apache.org/viewvc?rev=1855512&view=rev
Log:
fix rendering of java class in corenews

Modified:
    lucene/cms/trunk/content/core/corenews.mdtext

Modified: lucene/cms/trunk/content/core/corenews.mdtext
URL: http://svn.apache.org/viewvc/lucene/cms/trunk/content/core/corenews.mdtext?rev=1855512&r1=1855511&r2=1855512&view=diff
==============================================================================
--- lucene/cms/trunk/content/core/corenews.mdtext (original)
+++ lucene/cms/trunk/content/core/corenews.mdtext Thu Mar 14 11:42:19 2019
@@ -17,19 +17,19 @@ This release contains numerous bug fixes
 Term queries, phrase queries and boolean queries introduced new optimization that enables efficient skipping over non-competitive documents when the total hit count is not needed. Depending on the exact query and data distribution, queries might run between a few percents slower and many times faster, especially term queries and pure disjunctions.
 
 In order to support this enhancement, some API changes have been made:
- * `TopDocs.totalHits` is no longer a long but an object that gives a lower bound of the actual hit count.
- * `IndexSearcher`'s `search` and `searchAfter` methods now only compute total hit counts accurately up to 1,000 in order to enable this optimization by default.
+ * TopDocs.totalHits is no longer a long but an object that gives a lower bound of the actual hit count.
+ * IndexSearcher's search and searchAfter methods now only compute total hit counts accurately up to 1,000 in order to enable this optimization by default.
  * Queries are now required to produce non-negative scores.
 
 #### Codecs
 
  * Postings now index score impacts alongside skip data. This is how term queries optimize collection of top hits when hit counts are not needed.
  * Doc values introduced jump tables, so that advancing runs in constant time. This is especially helpful on sparse fields.
- * The terms index `FST` is now loaded off-heap for non-primary-key fields using `MMapDirectory`, reducing heap usage for such fields.
+ * The terms index FST is now loaded off-heap for non-primary-key fields using MMapDirectory, reducing heap usage for such fields.
 
 #### Custom scoring
 
-The new `FeatureField` allows efficient integration of static features such as a pagerank into the score. Furthermore, the new `LongPoint#newDistanceFeatureQuery` and `LatLonPoint#newDistanceFeatureQuery` methods allow boosting by recency and geo-distance respectively. These new helpers are optimized for the case when total hit counts are not needed. For instance if the pagerank has a significant weight in your scores, then Lucene might be able to skip over documents that have a low pagerank value.
+The new FeatureField allows efficient integration of static features such as a pagerank into the score. Furthermore, the new LongPoint#newDistanceFeatureQuery and LatLonPoint#newDistanceFeatureQuery methods allow boosting by recency and geo-distance respectively. These new helpers are optimized for the case when total hit counts are not needed. For instance if the pagerank has a significant weight in your scores, then Lucene might be able to skip over documents that have a low pagerank value.
 
 Further details of changes are available in the change log available at: