Spark 3.5: Add utility to load table state reliably#10984
Spark 3.5: Add utility to load table state reliably#10984aokolnychyi merged 1 commit intoapache:mainfrom
Conversation
spark/v3.5/spark/src/main/java/org/apache/iceberg/spark/SparkTableUtil.java
Outdated
Show resolved
Hide resolved
|
|
||
| public static Dataset<Row> loadTable(SparkSession spark, Table table, long snapshotId) { | ||
| SparkTable sparkTable = new SparkTable(table, snapshotId, false); | ||
| DataSourceV2Relation relation = createRelation(sparkTable, ImmutableMap.of()); |
There was a problem hiding this comment.
The snapshotId(and timestamp) could also be supplied as an option in the future Spark versions.
Should we have an method to take options as well?
There was a problem hiding this comment.
We actually bypass the resolution completely and manually create Dataset in this case.
There was a problem hiding this comment.
We may need to pass options in the future but let's add that once there is a use case (we will simply overload this method).
aokolnychyi
force-pushed
the
load-spark-tables
branch
from
1fa595e to
e834e11
Compare
| required(5, "stringCol", Types.StringType.get())); | ||
|
|
||
| @TestTemplate | ||
| public void testLoadingTableDirectly() { |
There was a problem hiding this comment.
This test would previously fail.
There was a problem hiding this comment.
Suggestion: Should we move this test to org.apache.iceberg.spark.TestSparkTableUtil
There was a problem hiding this comment.
I feel it belongs here as it is important to check the action can be invoked without loading tables via the Spark catalog (as that one will set the catalog name correctly).
This is the only test that goes via validationCatalog.
karuppayya
left a comment
karuppayya
left a comment
There was a problem hiding this comment.
lgtm,
left a nitpick, thanks @aokolnychyi for the change and @nastra for reviewing.
|
Thanks, @karuppayya @nastra! |
backport of apache#10984, tests can be backport in together with apache#11106
3 participants
While reviewing #10288, I realized we don't have a reliable way to load Iceberg table state as
Datasetin Spark. We shouldn't useload(table.name())as it is not clear if the name already includes the catalog name. This PR extends what we currently do for metadata tables to regular tables.