snuyanzin commented on code in PR #28688:
URL: https://github.com/apache/flink/pull/28688#discussion_r3615986350


##########
flink-table/flink-table-runtime/src/main/java/org/apache/flink/table/runtime/functions/SqlJsonUtils.java:
##########
@@ -374,6 +376,78 @@ private static Object errorResultForJsonQuery(
         }
     }
 
+    /** Accepts a pre-parsed context from {@link #jsonParse}. */
+    public static Integer jsonLength(final JsonValueContext parsedInput) {
+        if (parsedInput.hasException()) {
+            return null;
+        }
+        // Whole document: a top-level JSON null literal counts as a scalar 
(length 1).
+        return jsonLengthValue(parsedInput.obj);
+    }
+
+    /** Accepts a pre-parsed context from {@link #jsonParse}. */
+    public static Integer jsonLength(final JsonValueContext parsedInput, final 
String pathSpec) {
+        if (parsedInput.hasException()) {
+            // invalid input JSON
+            return null;
+        }
+        final Matcher matcher = JSON_PATH_BASE.matcher(pathSpec);
+        if (matcher.matches()) {
+            throw new TableRuntimeException(
+                    "JSON_LENGTH does not support lax/strict path modes. "
+                            + "Please refer to the documentation for the 
supported path format.");
+        }
+        final JsonPathContext context = jsonApiCommonSyntax(parsedInput, 
pathSpec);
+        final Object value = context.hasException() ? null : context.obj;
+        if (context.hasException() || value == null) {
+            return pathExists(parsedInput.obj, pathSpec) ? 1 : null;
+        }
+
+        final String pathStr = matcher.matches() ? matcher.group("spec") : 
pathSpec;

Review Comment:
   why do we need to invoke again `matcher.matches()`?
   it is already executed at line 395



-- 
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