I suspect what's happening is that the index format changed
between 3.x and 4.x and somehow the Luke request
handler is getting mixed up. I'm further guessing that
the -1 is just the default value, since it's clearly bogus
it's a flag the luke request handler just didn't see what it
expected...
O
Hi Erick,
I have upgraded from 3.5 to 4.0 on first index build i was able to see the
distinct terms on UI under Schema Browser section. I had to add a new date
field as stored to schema and re-index.
After that all the time on UI for every field i see the distinct term as
"-1".
Can you please adv
I'm afraid you have to give more details, this works fine for me with
the example docs and the example schema.
Best
Erick
On Sun, Oct 28, 2012 at 11:02 AM, adityab wrote:
> Hi
> Deployed 4.0 and while investigating the schema Browser for seeing the
> unique term count for each field observed fol
