[
https://issues.apache.org/jira/browse/PHOENIX-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077332#comment-16077332
]
James Taylor commented on PHOENIX-3994:
---------------------------------------
I think that's a reasonable solution (and not just for 0.98). In this case, we
can copy the Configuration and set state on it that will determine the RPC
priority (i.e. have a new Phoenix config specifically for RPC priority that's
set on the new config in the code). We can still set the priority if the table
is a Phoenix system table (as that can be based on the table name).
In this way, we can have a different priority for UPSERT SELECT versus the
batch mutate call since we control the getting of the HConnection ourselves.
> Index RPC priority still depends on the controller factory property in
> hbase-site.xml
> -------------------------------------------------------------------------------------
>
> Key: PHOENIX-3994
> URL: https://issues.apache.org/jira/browse/PHOENIX-3994
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.11.0
> Reporter: Sergey Soldatov
> Priority: Critical
> Attachments: PHOENIX-3994.patch
>
>
> During PHOENIX-3360 we tried to remove dependency on
> hbase.rpc.controllerfactory.class property in hbase-site.xml since it cause
> problems on the client side (if client is using server side configuration,
> all client request may go using index priority). Committed solution is using
> setting the controller factory programmatically for coprocessor environment
> in Indexer class, but it comes that this solution doesn't work because the
> environment configuration is not used for the coprocessor connection
> creation. We need to provide a better solution since this issue may cause
> accidental locks and failures that hard to identify and avoid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
