phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno Dumon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5) HRegion.put() on Phoenix table from within endpoint coprocessor fails with NPE
Date Mon, 20 Jan 2014 20:09:19 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876812#comment-13876812
] 

Bruno Dumon commented on PHOENIX-5:
-----------------------------------

I tried it with the HTable from CoprocessorEnvironment and it works (using HBase 0.9.15).
I verified using the debugger that it follows the correct code path in the CoprocessorHConnection.

For future reference, here's the ticket in HBase: https://issues.apache.org/jira/browse/HBASE-9534

CDH4 does not yet have a release that includes this, but I'm fine with the current workaround
of disabling the Indexer, knowing that in future it will be possible using the short-circuited
HTable.

Thanks!

> HRegion.put() on Phoenix table from within endpoint coprocessor fails with NPE
> ------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Bruno Dumon
>         Attachments: phoenix-coprocessor-compatibility-test.tar.gz
>
>
> See also mailing list: http://mail-archives.apache.org/mod_mbox/incubator-phoenix-user/201401.mbox/%3CCAAF1JdirF75oVNDEA9THt2DCZ0f0YOeo%3DRB3ARhQE_iG4fF6bQ%40mail.gmail.com%3E
> I have an HBase table created by Phoenix, onto which I added another CF
> which is unknown to Phoenix.
> I also have a custom endpoint coprocessor, which does puts on this table in
> the CF which is unknown by Phoenix.
> However, this doesn't work, it throws an NPE because the WALEdit contains a
> KeyValue with null bytes, which I found is the BATCH_MARKER added by
> Indexer.prePut. (I'm not using indexes)
> I don't have this problem if I do the put via an HTable, it is only when
> doing the put directly from the coprocessor via HRegion.put().
> *Workaround*: disabling the Indexer coprocessor avoids the issue.
> I will attach a testcase.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message