Kadir OZDEMIR created PHOENIX-5991:
--------------------------------------
Summary: IndexRegionObserver should not overwrite mutation
timestamps set by clients
Key: PHOENIX-5991
URL: https://issues.apache.org/jira/browse/PHOENIX-5991
Project: Phoenix
Issue Type: Improvement
Reporter: Kadir OZDEMIR
Assignee: Kadir OZDEMIR
Fix For: 4.x
Phoenix client can set mutation timestamps for connections with scn. For
example, it sets the timestamp for delete mutations. IndexRegionObserver does
not check if the timestamp is set for mutations and overwrites them with its
current time. While Phoenix does not support setting arbitrary timestamps on
the client side for all operations, setting a timestamp for delete mutations is
harmless even for tables with indexes. Instead of blindly overwriting mutations
timestamps, IndexRegionObserver can leave the determination of which timestamp
values are allowed for which operations and sets the timestamp for mutations
only when they are not set by Phoenix client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
