Coming back to HSEARCH-2639 Open , I guess we would address this use case with a field bridge with a standard LongEncoding, except we would use a custom encoding implementation for Elasticsearch: {{.withEncoding( ElasticsearchLongAsDateEncoding.builder().build() }}.