By analysing class BlobExtractor, which extract Blob properties of document model, the expected propery name for the main blob of a document of type File is file:content.
So, an expected configuration to exclude that blob property would be:
<?xml version="1.0"?> <component name="default-repository-config"> <extension target="org.nuxeo.ecm.core.blob.BlobManager" point="configuration"> <blobprovider name="default"> <class>org.nuxeo.ecm.core.blob.binary.DefaultBinaryManager</class> <property name="path">/home/vdutat/Workspaces/binaryStores/postgresql-vdutat-sandbox-710</property> <property name="key"></property> </blobprovider> </extension> <extension target="org.nuxeo.ecm.core.storage.sql.RepositoryService" point="repository"> <repository name="default" label="label.default.repository"> <pool minPoolSize="0" maxPoolSize="20" blockingTimeoutMillis="100" idleTimeoutMinutes="10" /> <clustering id="" enabled="false" delay="1000" /> <noDDL>false</noDDL> <ddlMode>compat</ddlMode> <aclOptimizations enabled="true"/> <pathOptimizations enabled="true"/> <idType>varchar</idType> <indexing> <fulltext disabled="false" searchDisabled="false" analyzer="english"> <index name="default"> <!-- all props implied --> <excludeField>file:content</excludeField> </index> <index name="title"> <field>dc:title</field> </index> <index name="description"> <field>dc:description</field> </index> </fulltext> </indexing> <usersSeparator key="," /> </repository> </extension> </component>
Nevertheless, the above excludeField configuration is rejected during the Nuxeo Platform startup with the following error message:
2016-03-31 18:21:54,344 ERROR [localhost-startStop-1] [org.nuxeo.ecm.core.storage.FulltextConfiguration] Ignoring property 'file:content' with bad type ComplexTypeImpl(content) in fulltext configuration: default
NXP-18750 introduced changes that changed how the configuration is loaded.
- depends on
-
NXP-18750 Factor out fulltext configuration from VCS into generic storage code
- Resolved