Liferay allows Expando Fields with a . in the name but throws an exception when attempting to index them

• Type: Bug
• Status: Closed
• Resolution: No Longer Reproducible
• Affects Version/s: 7.1.10 DXP FP10, 7.1.X, Master
• Fix Version/s: None
• Component/s: Portal Services > Expando, Search Infrastructure
• Labels:
  • 7.2-must
  • ee-ts
  • sme-must-7.2
• Fix Priority: 4
• Sprint: Search | S02 Sprint 18, Search | S02 Sprint 19
• Git Pull Request: https://github.com/BryanEngler/liferay-portal/pull/349

Steps to reproduce

1. Startup the portal and login as omni-admin
2. Create a Web Content Article Custom Field with the name 'journal.expando' with type: Text Field - Indexed

• To create a Custom Field see: https://dev.liferay.com/fr/discover/portal/-/knowledge_base/7-1/custom-fields
• Control Panel >> Configuration >> Custom Fields || Web Content Article

3. Create a Web Content Article and populate the Custom Field and Save.

• To create a Web Content Article see: https://dev.liferay.com/fr/discover/portal/-/knowledge_base/7-1/creating-web-content
• Liferay DXP >> Content >> Web Content Basic Web Content
• add Title
• scroll down the page and open MEATADATA
• in the field labeled journal.expando type "123456"
• click Publish

Expected result: content is saved and indexed without errors
Actual result: The following exception occurs:

ERROR [http-nio-8080-exec-4][ExpandoBridgeIndexerImpl:303] Indexing journal.expando
java.lang.IllegalArgumentException: Name must not contain .: expando_custom_fields_journal.expando

---

Backport/release info:
 Requires full reindex
 7.0.x backport requires a unique fix, because it comes with Elasticsearch 2.4 by default, which doesn't support dots in field names.