Kontinuation commented on issue #1724:
URL: https://github.com/apache/sedona/issues/1724#issuecomment-2550140873

   I have not reproduced this using similar configurations. Can you try running 
the repro without Sedona but with Kryo serialization enabled?
   
   ```
   from pyspark.sql import SparkSession
   
   spark = (
       SparkSession.builder.master('spark://localhost:5581')
       .config(
           'spark.jars.packages',
           'org.apache.iceberg:iceberg-spark-runtime-3.5_2.12:1.7.1,' 
'org.apache.iceberg:iceberg-aws-bundle:1.7.1,' 
'org.postgresql:postgresql:42.7.4',
       )
       .config('spark.serializer', 'org.apache.spark.serializer.KryoSerializer')
       .config('spark.sql.extensions', 
'org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions')
       .config('spark.sql.catalog.my_catalog', 
'org.apache.iceberg.spark.SparkCatalog')
       .config('spark.sql.catalog.my_catalog.type', 'jdbc')
       .config('spark.sql.catalog.my_catalog.uri', 
'jdbc:postgresql://localhost:5500/data_catalog_apache_iceberg')
       .config('spark.sql.catalog.my_catalog.jdbc.user', 'postgres')
       .config('spark.sql.catalog.my_catalog.jdbc.password', 'postgres')
       .config('spark.sql.catalog.my_catalog.io-impl', 
'org.apache.iceberg.aws.s3.S3FileIO')
       .config('spark.sql.catalog.my_catalog.warehouse', 's3a://data-lakehouse')
       .config('spark.sql.catalog.my_catalog.s3.endpoint', 
'http://localhost:5561')
       .config('spark.sql.catalog.my_catalog.s3.access-key-id', 'admin')
       .config('spark.sql.catalog.my_catalog.s3.secret-access-key', 'password')
       .getOrCreate()
   )
   
   spark.sql('CREATE TABLE my_catalog.table8 (name string) USING iceberg;')
   spark.sql("INSERT INTO my_catalog.table8 VALUES ('Alex'), ('Dipankar'), 
('Jason')")
   ```


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