Author: yonik
Date: Sun Oct 18 21:41:54 2009
New Revision: 826531
URL: http://svn.apache.org/viewvc?rev=826531&view=rev
Log:
javadoc - add ord/rord warnings
Modified:
lucene/solr/trunk/src/java/org/apache/solr/search/function/OrdFieldSource.java
lucene/solr/trunk/src/java/org/apache/solr/search/function/ReverseOrdFieldSource.java
Modified:
lucene/solr/trunk/src/java/org/apache/solr/search/function/OrdFieldSource.java
URL:
http://svn.apache.org/viewvc/lucene/solr/trunk/src/java/org/apache/solr/search/function/OrdFieldSource.java?rev=826531&r1=826530&r2=826531&view=diff
==============================================================================
---
lucene/solr/trunk/src/java/org/apache/solr/search/function/OrdFieldSource.java
(original)
+++
lucene/solr/trunk/src/java/org/apache/solr/search/function/OrdFieldSource.java
Sun Oct 18 21:41:54 2009
@@ -36,6 +36,9 @@
* <p>
* WARNING: ord() depends on the position in an index and can thus change when
other documents are inserted or deleted,
* or if a MultiSearcher is used.
+ * <br>WARNING: as of Solr 1.4, ord() and rord() can cause excess memory use
since they must use a FieldCache entry
+ * at the top level reader, while sorting and function queries now use entries
at the segment level. Hence sorting
+ * or using a different function query, in addition to ord()/rord() will
double memory use.
* @version $Id$
*/
Modified:
lucene/solr/trunk/src/java/org/apache/solr/search/function/ReverseOrdFieldSource.java
URL:
http://svn.apache.org/viewvc/lucene/solr/trunk/src/java/org/apache/solr/search/function/ReverseOrdFieldSource.java?rev=826531&r1=826530&r2=826531&view=diff
==============================================================================
---
lucene/solr/trunk/src/java/org/apache/solr/search/function/ReverseOrdFieldSource.java
(original)
+++
lucene/solr/trunk/src/java/org/apache/solr/search/function/ReverseOrdFieldSource.java
Sun Oct 18 21:41:54 2009
@@ -38,6 +38,11 @@
* <p>
* WARNING: ord() depends on the position in an index and can thus change
when other documents are inserted or deleted,
* or if a MultiSearcher is used.
+ * <br>
+ * WARNING: as of Solr 1.4, ord() and rord() can cause excess memory use
since they must use a FieldCache entry
+ * at the top level reader, while sorting and function queries now use entries
at the segment level. Hence sorting
+ * or using a different function query, in addition to ord()/rord() will
double memory use.
+ *
* @version $Id$
*/
