unsupported symbol error after migration with geolocation as field name
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- The word "geolocation" is not a reserved word in Liferay Portal 6.2 but in DXP it is.
- If a field name at Liferay Portal 6.2 is "geolocation", after the upgrade to DPX it could generated an Elasticsearch error like this:
-
ERROR [liferay/search_writer/SYSTEM_ENGINE-76][BulkDocumentRequestExecutorImpl:53] failure in bulk execution:_[1]: index [liferay-842907], type [LiferayDocumentType], id [com.liferay.journal.model.JournORTLET_7863163], message [MapperParsingException[failed to parse field [ddm__keyword__879923__geolocation] of type [geo_point]
- An structure with this field will not work
Environment
- Liferay DXP 7.0, 7.1, 7.2
Resolution
- This behaviour is cause because this field has de label "localizable":false
- To avoid this error just need to define the label localizable as true:
"localizable":true
Did this article resolve your issue ?