Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

MapperParsingException while indexing work objects of a class

SA-48394

Summary



When searching for any work object, records are not available for the work object. However, the work object is available in the System.


Error Messages



Type: java.lang.IllegalArgumentException
Message: Invalid format: "50L0-11-00" is malformed at "L0-11-00"

Stack

at org.joda.time.format.DateTimeParserBucket.doParseMillis(DateTimeParserBucket.java:187)
at org.joda.time.format.DateTimeFormatter.parseMillis(DateTimeFormatter.java:826)
at org.elasticsearch.index.mapper.core.DateFieldMapper$DateFieldType.parseStringValue(DateFieldMapper.java:366)
at org.elasticsearch.index.mapper.core.DateFieldMapper.innerParseCreateField(DateFieldMapper.java:534)
at org.elasticsearch.index.mapper.core.NumberFieldMapper.parseCreateField(NumberFieldMapper.java:241)
at org.elasticsearch.index.mapper.FieldMapper.parse(FieldMapper.java:321)
at (:)

Type: MapperParsingException[failed to parse [SelectedSalesAreas]]; nested

Message: IllegalArgumentException[Invalid format: "50L0-11-00" is malformed at "L0-11-00"];


Steps to Reproduce

  1. Log in to application.
  2. Search for any work object from the Case Worker portal.


Root Cause



The ElasticSearch Dynamic Template Configuration was set such that all the Dates are entered as strings. All the fields must be mapped to type String, despite their structure. For example:
  1. When the Date field has the structure 10-10-2017, where the last 4 digits is the year, the Date is type cast as a String.
  2. When a field has the structure 2H17-10-10, where the four digits (year) at the beginning includes an alpha character, the ElasticSearch property casts this as a String.
  3. When a field has the structure 2017-10-10, where the four digits at the beginning do not include an alpha character, the ElasticSearch ignores the Dynamic Template setting. It sets the field as a Date.


Resolution



Apply HFix-39473.


Suggest Edit

Published February 20, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us