update. I think this is a symptom of a problem with the Lucene index I'm trying to create. When I delete my index, the CMS works fine, but the queries are not optimized.
Its strange. if I redeploy the code setting my lucene index. Everything seems fine including my lucene property index, until I restart the instance. At which point the CMS is utterly fubar... until I delete my oak:index. then CMS is functional. Then I redeploy the package (again) with the index. The index seems like it works, and everything is fine (until a restart happens).
<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:oak="http://jackrabbit.apache.org/oak/ns/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" xmlns:st="http://www.st.com/nt/st" jcr:primaryType="nt:unstructured"> <lsaNews jcr:primaryType="oak:QueryIndexDefinition" async="async" compatVersion="2" evaluatePathRestrictions="{Boolean}true" reindex="{Boolean}true" type="lucene"> <indexRules jcr:primaryType="nt:unstructured"> <nt:base jcr:primaryType="nt:unstructured" includePropertyTypes="all"> <properties jcr:primaryType="nt:unstructured"> <featured jcr:primaryType="nt:unstructured" name="jcr:content/featured" nodeName="featured" ordered="{Boolean}true" propertyIndex="{Boolean}true" type="Boolean"/> <releaseDate jcr:primaryType="nt:unstructured" name="jcr:content/releaseDate" nodeName="releaseDate" ordered="{Boolean}true" propertyIndex="{Boolean}true" type="Date"/> </properties> </nt:base> </indexRules> </lsaNews> </jcr:root>I have SO question in case anyone can point to resources for adding Lucene Indexes to a cqblueprint archetype project
http://stackoverflow.com/questions/29836289/how-to-setup-lucene-index-for-aem
