Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
6.2.X EE, 7.0.X, 7.1.X, 7.2.X, Master
-
7.2.x, 7.1.x, 7.0.x, 6.2.x
-
Committed
-
3
-
027 - Sandshrew
Description
FileUtil.extractText is not working correctly in case of configuring text.extraction.fork.process.enabled=true in portal-ext.properties
Steps to reproduce
- Before starting Liferay, configure text.extraction.fork.process.enabled=true in portal-ext.properties
- Create a docx or odt file with content:
This is a test
- Create a site
- Attach created file to document library in previous created site
- Get indexed data from elasticsearch, opening following URL: (note: set your groupId)
http://localhost:9200/_search?q=%2BgroupId:<<YOUR_GROUPID>>+%2BentryClassName:com.liferay.document.library.kernel.model.DLFileEntry&pretty
- Review "content_en_US" field of each returned document:
- Expected behavior: the document has a "This is a test" text in "content_en_US" field
- Wrong behavior: the document doesn't have any text in "content_en_US"
- Expected behavior: the document has a "This is a test" text in "content_en_US" field
Attachments
Issue Links
- relates
-
LPE-16800 FileUtil.extractText is not working correctly when text.extraction.fork.process.enabled=true
-
- Closed
-
- Testing discovered
-
LPS-96652 An ExceptionInInitializerError is thrown in case of enabling text.extraction.fork.process.* in portal-ext.properties
- Closed
-
LPS-96654 LPS-70810 is reproduced in case of enabling text.extraction.fork.process.* in portal-ext.properties
- Closed
-
LPS-96779 Tika writes some warnings traces due to missing libraries
- Closed
-
LPS-96932 Thumbnails and Previews are not generated and an error is thrown with some PDFs generated from scanned documents
- Closed