Github user JamesRTaylor commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/37#discussion_r24786608
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/UpsertCompiler.java ---
@@ -156,7 +157,7 @@ private static MutationState
upsertSelect(PhoenixStatement statement,
column.getMaxLength(), column.getScale(),
column.getSortOrder());
values[i] = ByteUtil.copyKeyBytesIfNecessary(ptr);
}
- setValues(values, pkSlotIndexes, columnIndexes, table,
mutation);
+ setValues(values, pkSlotIndexes, columnIndexes, table,
mutation, statement);
--- End diff --
Note that this statement may have been cloned from the original statement
with a clone of the original connection since this upsertSelect is called in
parallel by multiple threads in a upsert select statement. Is that going to be
ok for linking back to the statement index in your case?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
