Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

Default Date/Time Parsers

  • Capella Operational
  • reference
    +
    Use a date/time parser to tell the Search Service how to interpret date and time data in your documents.

    You can set a default date/time parser for your Search index, or set a date/time parser when you create a single document field mapping with a datetime type.

    The following default date/time parsers are available:

    Date/Time Parser Description

    datetime optional

    The default date/time parser.

    The default date/time parser can parse dates in the following formats:

    • %Y-%m-%dT%H:%M:%S.%N%z:M: For example, a date/time string like 2023-09-15T14:24:50.1567+05:30

    • %Y-%m-%dT%H:%M:%S%z:M: For example, a date/time string like `2023-09-15T14:24:50+05:30

    • %Y-%m-%dT%H:%M:%S: For example, a date/time string like 2023-09-15T14:24:50

    • %Y-%m-%d %H:%M:%S: For example, a date/time string like 2023-09-15 14:24:50

    • %Y-%m-%d %H:%M:%S %z: For example, a date/time string like 2023-09-15 14:24:50 +0530

    • %Y-%m-%d: For example, a date/time string like 2023-09-15

    disabled

    The default date/time parser is disabled.

    unix_micro

    For date/time data formatted as the number of microseconds since the Unix epoch 1970-01-01T00:00:00Z.

    unix_milli

    For date/time data formatted as the number of milliseconds since the Unix epoch 1970-01-01T00:00:00Z.

    unix_nano

    For date/time data formatted as the number of nanoseconds since the Unix epoch 1970-01-01T00:00:00Z.

    unix_sec

    For date/time data formatted as the number of seconds since the Unix epoch 1970-01-01T00:00:00Z.

    See Also