Delete system.stat entries. It should fix the issue.
On Mar 1, 2018 3:04 AM, "Azharuddin Shaikh"
wrote:
> We are using phoenix(4.8-Version) to perform read operation on our
> Hbase(1.2.3 - Version) table but suddenly after 7 months from deployment we
> are stuck
He appears! Thanks for weighing in. Comments inline..
On Thu, Mar 1, 2018 at 3:55 PM, Lukáš Lalinský wrote:
> I'm fine with including the code. The license already matches Phoenix, is
> there anything else that you would need regarding that?
There's an official IP clearance
I'm fine with including the code. The license already matches Phoenix, is
there anything else that you would need regarding that?
Releasing Python code involves building the source distribution package and
uploading it to PyPI. If you end up using the python-phoenixdb project, I
can give you full
Re-opening the thread as I can extend help towards the IP clearance
process[1] to include python-phoenixdb[2] if Lukas Lalinsky and community
agrees to it.
I found both the repositories[2][3] on par but we should let first Lukáš
Lalinský (the original owner) to confirm if he agrees to contribute
Hi,
Have you experienced this Duplicate records issue again on your hbase
cluster.
Also, have you tried increasing your guidepost value for your phoenix.
Let me know if you have any specific solution to avoid this apart from
dropping system.* tables to resolve this issue.
Thanks,
Azharuddin
We are using phoenix(4.8-Version) to perform read operation on our
Hbase(1.2.3 - Version) table but suddenly after 7 months from deployment we
are stuck in an serious issue where suddenly phoenix is showing the table
count as '16232555' but when we perform count using Hbase Shell it is
reflecting