nastra commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2681166064
I looked into this with a fresh Spark 3.5.4 installation and using Iceberg
1.5.0 against a REST catalog and I'm not able to reproduce this issue.
[SPARK-43324](https://github.co
set92 commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2673967103
@nastra I don't know how to ask this without it sound wrong. But is Iceberg
ready for production? Because I would say that `UPDATE` is a common command to
run, and it has been broke al
Syed-bug commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2507785079
@jurossiar Thanks a lot for all the information...I have fixed the issue by
changing the jars..
--
This is an automated message from the Apache Git Service.
To respond to the mes
jurossiar commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2507769859
@Syed-bug The issue is with spark-version: 3.5. I though you had the issue
and wanted to be able to update tables. :)
Refers to my comments:
- https://github.com/apache/
Syed-bug commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2507125686
@jurossiar I am getting nosuchtable exception now ...
Spark version 3.4.1
Scala version:2.12
iceberg-spark-runtime jar version is 3.4.2.12-1.6.1.jar
hadoop-aws jar versi
jurossiar commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2506240731
Using this jar versions I can update iceberg tables:
spark-version: 3.4
scala-version: 2.12
iceberg-version: 1.6.1
awssdk-version: 2.20.131
--
This is an automated mes
Syed-bug commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2506095447
@jurossiar can you tell me the jars which u have used for 3.4.1 spark
version for updating the iceberg table.In 3.4.1 version...I am getting this
error...just wanna check on the ja
soumilshah1995 commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2433444077
+1
--
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 u
jurossiar commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2324860967
I'm wondering if you have any update on this issue? -> Previous comments:
https://github.com/apache/iceberg/issues/9960#issuecomment-2197375635
I've just tried using:
spark-v
dcdata1234 commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2283699352
Any update on this I am using currently INTO glue ETL and facing same error
able to do all operation just for merge statement and update statement facing
this issue
Spark 3.3.0
suisenkotoba commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2002451738
@nastra yes I use full identifier including catalog name. How can I make
sure the table is indeed an iceberg table. I checked the table has metadata
tables like snapshots, part
nastra commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-1999227549
@suisenkotoba that catalog isn't enabled by default. Are you using the full
identifier when updating (e.g. `UPDATE TABLE ..)
or are you using `USE ` prior to the update stmt?
--
Th
suisenkotoba commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-1999156293
```
.set(f'spark.sql.catalog.{catalog}', 'org.apache.iceberg.spark.SparkCatalog')
.set(f'spark.sql.catalog.{catalog}.type', 'hive')
```
this `{catalog}` configured he
nastra commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-1999150225
In your example you configured two catalogs. Which of those catalogs are you
using when you're creating and updating that table?
--
This is an automated message from the Apache Git
suisenkotoba commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-1999144318
> you're performing an UPDATE against a non-Iceberg table.
hmm that's strange. the table is created like this:
```
ddl = f"""
CREATE TABLE IF NOT EXISTS {table
nastra commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-1999091358
The `UPDATE TABLE is not supported temporarily` is an indication that you're
performing an `UPDATE` against a non-Iceberg table. The error itself is coming
from
[Spark](https://githu
suisenkotoba commented on issue #9960:
URL: https://github.com/apache/iceberg/issues/9960#issuecomment-1998860930
Traceback:
```
Py4JJavaError: An error occurred while calling o86.sql.
: org.apache.spark.SparkUnsupportedOperationException: UPDATE TABLE is not
supported temporarily.
17 matches
Mail list logo
