We're updating the issue view to help you get more done. 

Add support for the Instant type in backends and use it to provide support for java.util.Date

Description

Essentially only expose support for Instant from backends, and use bridges in the mapper to add support for Date.

See conversation on hipchat:

1 2 3 4 5 6 7 8 9 10 11 12 [12:26 PM] Yoann Rodière: What I was suggesting yesterday was, we could take advantage of that and, for Dates, use a bridge that converts them to an Instant. That would spare us all the (rather verbose) task of implementing support for Date in the backend, and we will have to implement support for Instant at some point anyway. [12:28 PM] Yoann Rodière: essentially it works like that: entity ---[mapper]---> property value ----[bridge]---> value to index ----[indexManager]---> backend-specific value (Json or Lucene Field) Yes. Instead of this: entity ---[mapper]---> Date ----[bridge]---> Date ----[indexManager]---> backend-specific value (Json or Lucene Field) entity ---[mapper]---> Instant ----[bridge]---> Instant ----[indexManager]---> backend-specific value (Json or Lucene Field) We will have this: entity ---[mapper]---> Date ----[bridge]---> Instant ----[indexManager]---> backend-specific value (Json or Lucene Field) entity ---[mapper]---> Instant ----[bridge]---> Instant ----[indexManager]---> backend-specific value (Json or Lucene Field)

Environment

None

Status

Assignee

Yoann Rodière

Reporter

Yoann Rodière

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Fix versions

Priority

Major