[ 
https://issues.apache.org/jira/browse/GEODE-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Galen O'Sullivan updated GEODE-4377:
------------------------------------
    Description: 
In the protobuf protocol, we are currently catching EncodingException due to 
values that we can't deserialize or result values that we can't serialize.

Encoding and decoding exceptions should be handled differently, so clients can 
tell if a value was present but could not be serialized.
Encoding and decoding errors should be handled consistently across operation 
handlers.

Probably we could throw Encoding or Decoding exceptions and handle them at a 
higher level than the individual op handler.

  was:
In the protobuf protocol, we are currently catching EncodingException due to 
values that we can't deserialize (or result values that we can't serialize).

Error handling should be consistent, and EncodingExceptions should be thrown by 
the handlers.


> Don't catch encoding exceptions in OperationHandlers
> ----------------------------------------------------
>
>                 Key: GEODE-4377
>                 URL: https://issues.apache.org/jira/browse/GEODE-4377
>             Project: Geode
>          Issue Type: Improvement
>          Components: client/server
>            Reporter: Galen O'Sullivan
>            Priority: Major
>
> In the protobuf protocol, we are currently catching EncodingException due to 
> values that we can't deserialize or result values that we can't serialize.
> Encoding and decoding exceptions should be handled differently, so clients 
> can tell if a value was present but could not be serialized.
> Encoding and decoding errors should be handled consistently across operation 
> handlers.
> Probably we could throw Encoding or Decoding exceptions and handle them at a 
> higher level than the individual op handler.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to