The system information about all Phoenix tables is located in HBase
SYSTEM.CATALOG table. So, if you recreate the catalog you will need to
recreate all tables as well. I'm not sure is there any other way to
fix it.
On Fri, Mar 11, 2016 at 4:25 PM, Saurabh Agarwal (BLOOMBERG/ 731 LEX)
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
FYI, I added Gabriel's excellent answer to our FAQs here:
https://phoenix.apache.org/faq.html#Why_empty_key_value
On Fri, Mar 11, 2016 at 4:10 AM, Ankit Singhal
wrote:
> You may check discussion from below mail chain.
>
You may check discussion from below mail chain.
https://www.mail-archive.com/dev@phoenix.apache.org/msg19448.html
On Fri, Mar 11, 2016 at 3:20 PM, Divya Gehlot
wrote:
>
> Hi,
> I created a table in Phoenix with three column families and Inserted the
> values as shown