I don't believe this is related to that bug as I don't set the facet
prefix. I have honestly never seen the issue before either and an
optimize fixed it. I can try to see if I can duplicate the issue
tomorrow, but since I've done the optimize I haven't seen it again.
On Thu, Mar 29, 2012 at 7:45
On Thu, Mar 29, 2012 at 6:33 PM, Jamie Johnson wrote:
> I recently got this stack trace when trying to execute a facet based
> query on my index. The error went away when I did an optimize but I
> was surprised to see it at all. Can anyone shed some light on why
> this may have happened?
I don'
