[
https://issues.apache.org/jira/browse/PHOENIX-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083569#comment-16083569
]
Samarth Jain commented on PHOENIX-4012:
---------------------------------------
I guess I can always write my own util to clone the config.
{code}
public static Configuration cloneConfig(Configuration conf) {
Configuration clone = new Configuration(conf);
Iterator<Entry<String, String>> iterator = conf.iterator();
while (iterator.hasNext()) {
Entry<String, String> entry = iterator.next();
clone.set(entry.getKey(), entry.getValue());
}
return clone;
}
{code}
After using this utility, things work fine. So no need to disable server side
upsert select except for the case mentioned in the JIRA title.
> Disable distributed upsert select when table has global mutable secondary
> indexes
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-4012
> URL: https://issues.apache.org/jira/browse/PHOENIX-4012
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
>
> It can be enabled back on when PHOENIX-3995 is fixed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
