amrishlal commented on issue #9282:
URL: https://github.com/apache/hudi/issues/9282#issuecomment-1663107557

   @rmnlchh @ad1happy2go I am looking at the following part of the stack trace:
   
   ```
   Cause: java.lang.IllegalArgumentException: For input string: "null"
   at scala.collection.immutable.StringLike.parseBoolean(StringLike.scala:330)
   at scala.collection.immutable.StringLike.toBoolean(StringLike.scala:289)
   at scala.collection.immutable.StringLike.toBoolean$(StringLike.scala:289)
   at scala.collection.immutable.StringOps.toBoolean(StringOps.scala:33)
   at 
org.apache.spark.sql.execution.datasources.parquet.ParquetToSparkSchemaConverter.(ParquetSchemaConverter.scala:70)
   at 
org.apache.spark.sql.execution.datasources.parquet.HoodieParquetFileFormatHelper$.buildImplicitSchemaChangeInfo(HoodieParquetFileFormatHelper.scala:30)
   ```
   The stack trace seems to indicate that there was a problem while trying to 
convert a string value into boolean (see code line at [spark v3.3.2 
ParquetSchemaConverter.scala:70](https://github.com/apache/spark/blob/5103e00c4ce5fcc4264ca9c4df12295d42557af6/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetSchemaConverter.scala#L70)
 which I have pasted below):
   
   `conf.get(SQLConf.LEGACY_PARQUET_NANOS_AS_LONG.key).toBoolean)`
   
   This line seems to indicate that you need to set 
`spark.sql.legacy.parquet.nanosAsLong` to enter 'true' or 'false' to avoid this 
exception from coming up (see definition of 
[LEGACY_PARQUET_NANOS_AS_LONG](https://github.com/apache/spark/blob/5103e00c4ce5fcc4264ca9c4df12295d42557af6/sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala#L3462C87-L3462C87)
 here). Please let me know if this doesn't fix the issue.
   


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