Lars Hofhansl created PHOENIX-5044:
--------------------------------------
Summary: Remove server side mutation code from Phoenix
Key: PHOENIX-5044
URL: https://issues.apache.org/jira/browse/PHOENIX-5044
Project: Phoenix
Issue Type: Task
Reporter: Lars Hofhansl
This is for *discussion*.
It generally seems to be a bad idea - if well-intentioned - idea to trigger
mutations directly from the server. The main causes are UPSERT SELECT for the
same table and DELETE FROM.
IMHO, it's generally better to allow the client to handle this. There might be
larger network overhead, but we get better chunking, better pacing, and
behavior more in line with how HBase was intended to work.
In PHOENIX-5026 I introduced a flag to disable server triggered mutations in
the two cases mentioned above. I now think it's better to just remove the
server code and also perform these from the client.
(Not that server side reads - aggregation, filters, etc - are still insanely
valuable and not affected by this)
Let's discuss.
[~tdsilva], [[email protected]], [~jamestaylor], [~vincentpoon], [~gjacoby]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
