com.plumtree.server.search
Class PTSFieldType

java.lang.Object
  com.plumtree.server.search.PTSFieldType

public class PTSFieldType
extends java.lang.Object

An enumeration of field types supported by Plumtree Search.

Field Summary

static PTSFieldType	BOOLEAN Field type for boolean fields.
static PTSFieldType	DATETIME Field type for date/time fields.
static PTSFieldType	FLOAT Field type for floating-point fields.
static PTSFieldType	INT Field type for integer fields.
static PTSFieldType	STRING Field type for String fields.

Method Summary

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

STRING

public static final PTSFieldType STRING

Field type for String fields.

INT

public static final PTSFieldType INT

Field type for integer fields.

IMPORTANT: The search server stores all numeric types (integers, floats, and date-times) as 32-bit floating-point numbers, so large integers can suffer roundoff error when indexed. Integer fields are best used for result sorting (see IPTSQueryRequest.setResultsOrderBy). If you must have reliable storage of exact values, look them up post-search query in some other repository, such as a database.

FLOAT

public static final PTSFieldType FLOAT

Field type for floating-point fields.

IMPORTANT: The search server stores all numeric types (integers, floats, and date-times) as 32-bit floating-point numbers. If you need 64-bit (double) precision, store the full double value in some other repository, and look it up after doing your search query.

BOOLEAN

public static final PTSFieldType BOOLEAN

Field type for boolean fields.

DATETIME

public static final PTSFieldType DATETIME

Field type for date/time fields.

IMPORTANT: The search server stores all date-times as 32-bit floating-point values representing the number of minutes since 01-Jan-2000 00:00:00. Dates that are significantly far from this moment in time will suffer roundoff error. Date-time fields are best used for result sorting (see IPTSQueryRequest.setResultsOrderBy) or applications where high precision is not required (e.g. showing a "last-modified date" that does not need to be exact). If you need storage of exact times, store the full date-time value in some other repository, such as a database, and look it up after doing your search query.