You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ArrowScan to_table fails if the data is mixed between dict-encoded strings and plain strings.聽#3260
We have recently updated our functions to call the pyiceberg table.append() function with dict encoded arrow tables. Now we have in our iceberg tables mixed data from before this change, (where our data still is stored as string) and after the change, where the data is stored as dict-encoded strings.
If we now call to_arrow() of a DataScan class, on this table we get this error:
pyarrow.lib.ArrowTypeError: Unable to merge: Field col has incompatible types: string vs dictionary<values=string, indices=int32, ordered=0>
Here is a minimal example that reproduces this error:
I am happy to provide a bugfix PR, but I need a small guidance on the best approach.
One idea is to cast each batch in to_table to the arrow_schema. The more performant way is to check for each batch, if the schema is different. If they are different, then find the dict_encoded col and only cast that one to string.
Willingness to contribute
I can contribute a fix for this bug independently
I would be willing to contribute a fix for this bug with guidance from the Iceberg community
I cannot contribute a fix for this bug at this time
Thanks a lot, @lukaswelsch, for opening the issue!
Here's some additional context which also might be helpful:
This issue becomes really problematic when working with iceberg tables "living" in AWS Athena/Trino if these tables or their parts often get optimized for performance through an Athena's OPTIMIZE query (or the one from Trino).
Because, as it turned out, if optimization procedure mentioned above finds parquet files eligible for optimization, it rewrites them in a way that all dict-encoded string columns (if there were any) again become a plain string ones. It also seems like there is no way to influence this optimization behavior as of now (or at least, I'm not aware of it). So any table created using dictionary_encode() and being continuously optimized for performance in Athena/Trino inevitably enters that mixed dict-encoded string + plain string at some point and the incremental scans start failing.
This still reproduces on main (b32392d) and 0.12.0. A common way to hit it is a pandas Categorical column, followed by a normal append:
importpandasaspd, pyarrowaspa# table has a string column `status`tbl.append(pa.Table.from_pandas(pd.DataFrame({"id": [1, 2], "status": pd.Categorical(["new", "done"])}), preserve_index=False))
tbl.append(pa.Table.from_pandas(pd.DataFrame({"id": [3], "status": ["new"]}), preserve_index=False))
tbl.scan().to_arrow() # ArrowTypeError: Unable to merge: Field status has incompatible types: large_string vs dictionary<values=string, indices=int8, ...>tbl.scan().to_pandas() # sametbl.scan().to_polars() # same
to_arrow_batch_reader() works because it casts each batch to the table schema, but to_table concatenates the per-file tables as they are.
@Fokko, would you be open to a fix in ArrowScan.to_table that decodes dictionary columns to plain strings before concatenating, unless the column is listed in dictionary_columns? This matches to_arrow_batch_reader(), and Iceberg has no dictionary type, so string is what the schema says. It is a small change (about 10 lines plus tests).
One behavior change to flag: a table where every file was written from categorical data currently comes back as category in to_pandas(). With this fix it would come back as a plain string dtype unless the column is passed in dictionary_columns.
The same error came up in #2250, where you asked what outcome users expect; the answer there was the type from the table schema, which is what this fix returns. Three earlier PRs for this (#3444, #3667, #3849) were closed as stale without review. If this direction works for you, I'm happy to open a PR and credit those authors.
Activity
anna-dv commentedon Apr 27, 2026
Thanks a lot, @lukaswelsch, for opening the issue!
Here's some additional context which also might be helpful:
This issue becomes really problematic when working with iceberg tables "living" in AWS Athena/Trino if these tables or their parts often get optimized for performance through an Athena's OPTIMIZE query (or the one from Trino).
Because, as it turned out, if optimization procedure mentioned above finds parquet files eligible for optimization, it rewrites them in a way that all
dict-encoded stringcolumns (if there were any) again become aplain stringones. It also seems like there is no way to influence this optimization behavior as of now (or at least, I'm not aware of it). So any table created usingdictionary_encode()and being continuously optimized for performance in Athena/Trino inevitably enters that mixeddict-encoded string + plain stringat some point and the incremental scans start failing.The interesting thing here is though, before seeing the error message from the issue above (
pyarrow.lib.ArrowTypeError: ...), one also gets a warning from pyiceberg that Iceberg does not have a dictionary type. <class 'pyarrow.lib.DictionaryType'> will be inferred as string on read., but seems like this inference is never happening and the read still fails afterwards.Looking forward to the updates on this one and would also be happy to help if needed! 鉁岋笍
hzmsh commentedon Oct 15, 2026
This still reproduces on
main(b32392d) and 0.12.0. A common way to hit it is a pandasCategoricalcolumn, followed by a normal append:to_arrow_batch_reader()works because it casts each batch to the table schema, butto_tableconcatenates the per-file tables as they are.@Fokko, would you be open to a fix in
ArrowScan.to_tablethat decodes dictionary columns to plain strings before concatenating, unless the column is listed indictionary_columns? This matchesto_arrow_batch_reader(), and Iceberg has no dictionary type, sostringis what the schema says. It is a small change (about 10 lines plus tests).One behavior change to flag: a table where every file was written from categorical data currently comes back as
categoryinto_pandas(). With this fix it would come back as a plain string dtype unless the column is passed indictionary_columns.The same error came up in #2250, where you asked what outcome users expect; the answer there was the type from the table schema, which is what this fix returns. Three earlier PRs for this (#3444, #3667, #3849) were closed as stale without review. If this direction works for you, I'm happy to open a PR and credit those authors.