Hello,
On our integration testing environment we suddenly have checked out that every time we create a lucene index under oak:index a new node (facets) is created within it,:
oak:index
|_ my_index
|_aggregates
|_indexRules (property index don't have defined the facet parameter)
|_facets (that node is automatically created)
Moreover every time we delete that node it appears again after a couple of seconds. Keeping in mind that we are not using facets on our queries we would like to remove it (forever). Furthermore we have started noticing that queries take longer than before and we are getting hundreds of traces informing that faceting is being performed:
19.06.2017 12:57:52.545 *DEBUG* [16.79.38.118 [1497877054278] POST /etc/acs-tools/explain-query/_
jcr_content.explain.json HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex.perf 51200 ... [took 76ms]
19.06.2017 12:57:52.546 *DEBUG* [16.79.38.118 [1497877054278] POST /etc/acs-tools/explain-query/_jcr_content.explain.json HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex.perf facets retrieved [took 0ms]
19.06.2017 12:58:09.719 *DEBUG* [16.79.38.118 [1497877054278] POST /etc/acs-tools/explain-query/_jcr_content.explain.json HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex loading the next 100000 entries for query *:*
The only recorded change is an upgrade from Apache OAK 1.4.1 to 1.4.15 under a AEM6.2 , but there must be something more we haven't found.
Any help on how to avoid facets node to be regenerated is welcome. After checking out [1] and [2] I haven't found anything.
Regards.
