<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Apr 21, 2014, at 1:24 PM, Chris Burrell <<a href="mailto:christopher@burrell.me.uk">christopher@burrell.me.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span style="font-family: arial, sans-serif; font-size: 13px;">DM>Right now, if we use the same analyzer for search and for index construction across all fields, we can share the same indexes even if we use different index policy adapters.</span><br></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><font face="Verdana, Geneva, Helvetica, Arial, sans-serif">CJB> I'm not sure this is true? If BD is configured to disable headings in the policy adapter, but STEP has headings enabled in the Policy adapter, then the index will contain different content. I.e. STEP will lack headings if BD created the index. BD will not suffer, if STEP has created the index. This would then break the auto-completing aggregation aforementioned. Or am I mis-understanding something?</font></div><br class="Apple-interchange-newline"></blockquote></div><br><div><div>Not really missing anything. There are many modules without headings. Obviously STEP has to cope with not being able to search that module for headings.</div><div><br></div><div>Likewise, if one app wants to allow searching of headings and the index does not have that field, it behaves the same way, the index works properly and does not return a wrong answer. It merely returns no answer. The index is fully compatible between the two applications from a Lucene perspective. Not ideal, but certainly not a broken index.</div></div></body></html>