ndimiduk commented on a change in pull request #4177:
URL: https://github.com/apache/hbase/pull/4177#discussion_r822525634



##########
File path: 
hbase-http/src/main/java/org/apache/hadoop/hbase/http/gson/ByteArraySerializer.java
##########
@@ -0,0 +1,38 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.hadoop.hbase.http.gson;
+
+import java.lang.reflect.Type;
+import org.apache.hadoop.hbase.util.Bytes;
+import org.apache.yetus.audience.InterfaceAudience;
+import org.apache.hbase.thirdparty.com.google.gson.JsonElement;
+import org.apache.hbase.thirdparty.com.google.gson.JsonPrimitive;
+import org.apache.hbase.thirdparty.com.google.gson.JsonSerializationContext;
+import org.apache.hbase.thirdparty.com.google.gson.JsonSerializer;
+
+/**
+ * Serialize a {@code byte[]} using {@link Bytes#toString()}.
+ */
[email protected]
+public final class ByteArraySerializer implements JsonSerializer<byte[]> {
+
+  @Override
+  public JsonElement serialize(byte[] src, Type typeOfSrc, 
JsonSerializationContext context) {
+    return new JsonPrimitive(Bytes.toString(src));

Review comment:
       @apurtell 
   
   After some research, my understanding is that Gson handles escaping 
characters according to the JSON RFC's definition of String values. We are 
free, according to the RFC, to encode more aggressively than what Gson does, 
but it appears to implement the minimum plus some additional characters related 
to html. My test demonstrates that there are some binary values that are not 
encoded and that do not render well (at least on this machine).
   
   We may chose to escape a wider range of code points, or we my consider some 
alternative encoding for binary values, such as base64 with perhaps some prefix.
   
   I have made every effort to declare this API as IA.Private, so we are free 
to evolve it as we choose, so long as we can maintain a sufficient level of 
backward compatibility for our guarantees. Thus I would prefer to press forward 
with landing this initial implementation of the feature and continue this 
encoding discussion as a follow-on effort.
   
   Please advise.
   
   https://datatracker.ietf.org/doc/html/rfc4627#section-2.5
   
https://github.com/google/gson/blob/gson-parent-2.8.9/gson/src/main/java/com/google/gson/stream/JsonWriter.java#L133-L163




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to