mirror of https://github.com/apache/lucene.git
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/lucene-solr
This commit is contained in:
commit
88c3c3c580
|
@ -36,8 +36,70 @@ import org.apache.lucene.util.mutable.MutableValueDate;
|
|||
import org.apache.lucene.util.mutable.MutableValueLong;
|
||||
import org.apache.solr.search.QParser;
|
||||
import org.apache.solr.uninverting.UninvertingReader;
|
||||
import org.apache.solr.update.processor.TimestampUpdateProcessorFactory;
|
||||
import org.apache.solr.util.DateMathParser;
|
||||
|
||||
/**
|
||||
* FieldType that can represent any Date/Time with millisecond precision.
|
||||
* <p>
|
||||
* Date Format for the XML, incoming and outgoing:
|
||||
* </p>
|
||||
* <blockquote>
|
||||
* A date field shall be of the form 1995-12-31T23:59:59Z
|
||||
* The trailing "Z" designates UTC time and is mandatory
|
||||
* (See below for an explanation of UTC).
|
||||
* Optional fractional seconds are allowed, as long as they do not end
|
||||
* in a trailing 0 (but any precision beyond milliseconds will be ignored).
|
||||
* All other parts are mandatory.
|
||||
* </blockquote>
|
||||
* <p>
|
||||
* This format was derived to be standards compliant (ISO 8601) and is a more
|
||||
* restricted form of the
|
||||
* <a href="http://www.w3.org/TR/xmlschema-2/#dateTime-canonical-representation">canonical
|
||||
* representation of dateTime</a> from XML schema part 2. Examples...
|
||||
* </p>
|
||||
* <ul>
|
||||
* <li>1995-12-31T23:59:59Z</li>
|
||||
* <li>1995-12-31T23:59:59.9Z</li>
|
||||
* <li>1995-12-31T23:59:59.99Z</li>
|
||||
* <li>1995-12-31T23:59:59.999Z</li>
|
||||
* </ul>
|
||||
* <p>
|
||||
* Note that <code>DatePointField</code> is lenient with regards to parsing fractional
|
||||
* seconds that end in trailing zeros and will ensure that those values
|
||||
* are indexed in the correct canonical format.
|
||||
* </p>
|
||||
* <p>
|
||||
* This FieldType also supports incoming "Date Math" strings for computing
|
||||
* values by adding/rounding internals of time relative either an explicit
|
||||
* datetime (in the format specified above) or the literal string "NOW",
|
||||
* ie: "NOW+1YEAR", "NOW/DAY", "1995-12-31T23:59:59.999Z+5MINUTES", etc...
|
||||
* -- see {@link DateMathParser} for more examples.
|
||||
* </p>
|
||||
* <p>
|
||||
* <b>NOTE:</b> Although it is possible to configure a <code>DatePointField</code>
|
||||
* instance with a default value of "<code>NOW</code>" to compute a timestamp
|
||||
* of when the document was indexed, this is not advisable when using SolrCloud
|
||||
* since each replica of the document may compute a slightly different value.
|
||||
* {@link TimestampUpdateProcessorFactory} is recommended instead.
|
||||
* </p>
|
||||
*
|
||||
* <p>
|
||||
* Explanation of "UTC"...
|
||||
* </p>
|
||||
* <blockquote>
|
||||
* "In 1970 the Coordinated Universal Time system was devised by an
|
||||
* international advisory group of technical experts within the International
|
||||
* Telecommunication Union (ITU). The ITU felt it was best to designate a
|
||||
* single abbreviation for use in all languages in order to minimize
|
||||
* confusion. Since unanimous agreement could not be achieved on using
|
||||
* either the English word order, CUT, or the French word order, TUC, the
|
||||
* acronym UTC was chosen as a compromise."
|
||||
* </blockquote>
|
||||
*
|
||||
* @see TrieDateField
|
||||
* @see PointField
|
||||
*/
|
||||
public class DatePointField extends PointField implements DateValueFieldType {
|
||||
|
||||
public DatePointField() {
|
||||
|
|
|
@ -528,9 +528,9 @@ abstract class FacetFieldProcessor extends FacetProcessor<FacetField> {
|
|||
}
|
||||
|
||||
protected SimpleOrderedMap<Object> refineFacets() throws IOException {
|
||||
List leaves = asList(fcontext.facetInfo.get("_l"));
|
||||
List<List> skip = asList(fcontext.facetInfo.get("_s"));
|
||||
List<List> missing = asList(fcontext.facetInfo.get("_m"));
|
||||
List leaves = asList(fcontext.facetInfo.get("_l")); // We have not seen this bucket: do full faceting for this bucket, including all sub-facets
|
||||
List<List> skip = asList(fcontext.facetInfo.get("_s")); // We have seen this bucket, so skip stats on it, and skip sub-facets except for the specified sub-facets that should calculate specified buckets.
|
||||
List<List> missing = asList(fcontext.facetInfo.get("_m")); // We have not seen this bucket, do full faceting for this bucket, and most sub-facets... but some sub-facets should only visit specified buckets.
|
||||
|
||||
// For leaf refinements, we do full faceting for each leaf bucket. Any sub-facets of these buckets will be fully evaluated. Because of this, we should never
|
||||
// encounter leaf refinements that have sub-facets that return partial results.
|
||||
|
|
|
@ -366,13 +366,9 @@ public abstract class FacetProcessor<FacetRequestT extends FacetRequest> {
|
|||
}
|
||||
}
|
||||
|
||||
// TODO: rather than just have a raw "response", perhaps we should model as a bucket object that contains the response plus extra info?
|
||||
void fillBucket(SimpleOrderedMap<Object> bucket, Query q, DocSet result, boolean skip, Map<String,Object> facetInfo) throws IOException {
|
||||
|
||||
// TODO: we don't need the DocSet if we've already calculated everything during the first phase
|
||||
boolean needDocSet = freq.getFacetStats().size() > 0 || freq.getSubFacets().size() > 0;
|
||||
|
||||
// TODO: put info in for the merger (like "skip=true"?) Maybe we don't need to if we leave out all extraneous info?
|
||||
boolean needDocSet = (skip==false && freq.getFacetStats().size() > 0) || freq.getSubFacets().size() > 0;
|
||||
|
||||
int count;
|
||||
|
||||
|
|
Loading…
Reference in New Issue