SOLVED: Import of ACP fails to build Lucene Index

[rliu]

When importing an ACP file, has anyone noticed that the Lucene indexes are not being built? The configuration in my content model is such that the all my properties are:

                    
<index enabled="true">
    <atomic>true</atomic>
    <stored>true</stored>
    <tokenised>true</tokenised>
</index>
‍‍‍‍‍‍‍

Was the intent not to trigger the building of the Lucene indexes for imported spaces? If so, this is so problematic for my project.

[rliu]

My mistake… I added this stanza to my web-client-config-custom.xml file and with my custom properties and it did the job.

<config>
    <client>
        <simple-search-additional-attributes>
            <qname>some custom property</qname>
        </simple-search-additional-attributes>
    </client>
</config>
‍‍‍‍‍‍‍‍