I don't recall any big issues on 4.13.2, but I, admittedly, haven't
followed it closely.
You weren't doing anything weird on your own -- you wrote data via the
JDBC driver? Any index tables?
Aside from weirdness in the client with statistics, there isn't much
I've seen that ever causes a "bad" table. You have to try pretty hard to
"corrupt" a table.
On 7/31/18 11:02 AM, Flavio Pompermaier wrote:
Hi to all,
today I had a very weird, and potentially critical, behavior in my
Phoenix installation (4.13.2 on CDH 5.11.2).
I started upserting rows in a salted table but I fortunately discovered
that some of them were missing (and the PK was unique).
After 3 hours of attempts and debugging I gave up and I deleted and
recreated the table. Now the upserts works like a charm...this is very
bad and I still don't know the source of the problem.
Is there a way to check if a table is in a good state or if there's
something wrong?
Best,
Flavio
