shahrs87 commented on a change in pull request #978:
URL: https://github.com/apache/phoenix/pull/978#discussion_r537120671
##########
File path:
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionScanner.java
##########
@@ -479,6 +486,10 @@ void deleteCForQ(Tuple result, List<Cell> results,
UngroupedAggregateRegionObser
delete.addColumns(deleteCF, deleteCQ, ts);
// force tephra to ignore this deletes
delete.setAttribute(PhoenixTransactionContext.TX_ROLLBACK_ATTRIBUTE_KEY, new
byte[0]);
+ // TODO: We need to set SOURCE_OPERATION_ATTRIB here also. The
control will come here if
Review comment:
> Good question, @shahrs87 . I think we should set the attribute there.
@gjacoby126 I started doing changes for setting source operation attribute
here. When we drop a column, we create delete markers with delete type
"DELETE_COLUMN" for the base table and also we delete metadata for that column
in SYSCAT table. Is it reasonable to have the feature first for just deleting
rows from data table and then we can extend it for drop columns use case.
Please advise. Thank you !
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
