When changed
store.getSmallestReadPoint()
to
((HStore)store).getHRegion().getReadpoint(IsolationLevel.READ_COMMITTED)
coprocessor behavior is correct. This is taken from coprocessor example
code. We have recently upgraded hbase version (from 0.94.x to 1.0.0) and
missed out that coprocesso
>>store.getSmallestReadPoint()
This is the problem. At the time of write some other readers (opened
in past) were present, then all those are present readPnts and u will
get min of all such read points.
Its a pity that we are not passing the read point to the CP pre hook.
That is obtained in Re
I have new information after some more debugging:
I am sure coprocessor is not filtering out values in get/put hooks.
The observed behavior is:
We create non-existing cell via PUT and immediately after the call
returns, we are trying to get the created cell value via GET. The GET
is done eve
Can you provide us the code u have written for the pre hooks + the
custom filter code. You sure the filter is not filtering out this
recent cell? Add some logs there and check?
-Anoop-
On Thu, Mar 31, 2016 at 12:57 PM, Jozef Vilcek wrote:
> Test was done via hbase shell prompt. I am not sure o
Test was done via hbase shell prompt. I am not sure on it's behavior. Can
it hide some timeouts and return nothing? I hope not.
I will try to reproduce it with java API.
Coprocessor does not do anything asynchronous in it's hooks. It is hooked
only on preStoreScannerOpen, preFlushScannerOpen, preC
Hi Ted,
I am not very familiar with "unit test using simplified coprocessor".
If you can point me to an example, I can give it a shot. Altough, as I
said, observed behavior is not deterministic and happens not on all
regions.
>Is it possible to come up with unit test showing this behavior using
Do you wait for the Put to return before you issue the Get? Or have you
disabled auto flushing on your table instance -- HTable.setAutoFlush(false)?
Coprocessor hooks executed on the Put and Get paths are blocking, so unless
you're overriding normal processing in the prePut() hook and doing
somet
Is it possible to come up with unit test showing this behavior using simplified
coprocessor ?
Thanks
> On Mar 29, 2016, at 5:42 AM, Jozef Vilcek wrote:
>
> Hi,
>
> I need a help to shed some light on following observation:
>
> Through hbase shell I do PUT to a non existing cell (create) and
Hi,
I need a help to shed some light on following observation:
Through hbase shell I do PUT to a non existing cell (create) and immediate
GET.
When doing this against hbase table without a coprocessor, every GET shows
the value immediately. When I enable a coprocessor on the table and perform
the
