Saurabh, another option for you would be to upgrade your phoenix to our
just released 4.7 version. It is possible that you might be hitting a bug
that has been fixed now. Worth a try.
On Fri, Mar 11, 2016 at 4:07 PM, Sergey Soldatov
wrote:
> Hi Saurabh,
> It seems that
Hi,
I had been experimenting with different indexes on Phoenix table to get the
desired performance.
After creating secondary index that create index on one column and include rest
of the fields, it start throwing the following exceptions whenever I access the
table.
Can you point me what