dawidwys commented on a change in pull request #13763:
URL: https://github.com/apache/flink/pull/13763#discussion_r513253682



##########
File path: 
flink-formats/flink-avro/src/main/java/org/apache/flink/formats/avro/typeutils/AvroSchemaConverter.java
##########
@@ -297,17 +299,22 @@ private static DataType convertToDataType(Schema schema) {
         * @return Avro's {@link Schema} matching this logical type.
         */
        public static Schema convertToSchema(LogicalType logicalType) {
-               return convertToSchema(logicalType, "record");
+               return convertToSchema(logicalType, "record", true);
        }
 
        /**
         * Converts Flink SQL {@link LogicalType} (can be nested) into an Avro 
schema.
         *
         * @param logicalType logical type
         * @param rowName     the record name
+        * @param top         whether it is parsing the root record,
+        *                    if it is, the logical type nullability would be 
ignored
         * @return Avro's {@link Schema} matching this logical type.
         */
-       public static Schema convertToSchema(LogicalType logicalType, String 
rowName) {
+       public static Schema convertToSchema(
+                       LogicalType logicalType,
+                       String rowName,
+                       boolean top) {

Review comment:
       > I don't think we should let each invoker to decide whether to make the 
data type not null, because in current codebase, we should always do that, make 
the decision everyone is error-prone and hard to maintain.
   
   I agree making the same decision over and over again at multiple location is 
error prone and hard to maintain and that's what I want to avoid.




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

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


Reply via email to