Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
avatica-1.17.0
-
None
-
None
Description
Hi team, recently I encountered a potential bug that after deserialization of serialized ErrorResponse objects, the value of AvaticaSeverity lost, eg. became null.
Here is a simple scala test I used:
val translator = new ProtobufTranslationImpl val response = new Service.ErrorResponse(Lists.newArrayList(), "error message", 500, SqlState.INVALID_SQL_STATEMENT.toString ,AvaticaSeverity.UNKNOWN, null) val parsedSerializedResponse = translator.parseResponse(translator.serializeResponse(response)) assert(response.severity == parsedSerializedResponse.asInstanceOf[Service.ErrorResponse].severity)
This test only fails for AvaticaSeverity.UNKOWN but not FATAL, ERROR and WARNING, so I suspect there is a bug during the serialization/deserialization process.