Dug into one of the row that was having a similar problem, throwing
IllegalArgumentException [1] instead of BufferUnderflowException, but both
seemed to be data issue on how the varchar array is stored in an unexpected
format in HBase.
The row looks like:
Thank Jaanai.
At first we thought it was data issue too, but as we restored the table
from snapshot to a separate schema on the same cluster to triage, the
exception no longer happens... Does that give further clue on what the
issue might've been?
0: jdbc:phoenix:journalnode,test> SELECT A, B,
It looks a bug that the remained part greater than retrieved the length in
ByteBuffer, Maybe the position of ByteBuffer or the length of target byte
array exists some problems.
Jaanai Zhang
Best regards!
William Shen 于2018年10月12日周五 下午11:53写道：
>
Hi all,
We are running Phoenix 4.13, and periodically we would encounter the
following exception when querying from Phoenix in our staging environment.
Initially, we thought we had some incompatible client version connecting
and creating data corruption, but after ensuring that we are only
