Github user cestella commented on the issue:
https://github.com/apache/metron/pull/995
> I'm not following. A patch would only include the field to be added,
changed, or removed.
JSONPatch, the input that we accept for the `patch` command, offers more
than add, change and remove operations. There is also move and add supports
adding into an array. My point is that the format is more complex than just
passing in a list of fields to add, change or remove.
> If for some reason a user is trying to directly update a generated field
that is incorrect and a user error.
Consider this from a user perspective for a moment. How would a user know
if a field is generated or not? If we could determine which fields were
generated to ensure the users aren't given the ability to change them, then we
could whitelist them generally and solve this problem.
I'm not opposed to partial updates, but I don't see that as a solution to
the problem from this PR. It feels like kicking the can down the road and
making it the user's problem, which I don't agree with.
---
