You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "voon (Jira)" <ji...@apache.org> on 2025/04/08 08:48:00 UTC

[jira] [Updated] (HUDI-9216) 1.x spark reader enforces database from tableConfig instead of defaulting to spark.catalog.currentDatabase as fallback

     [ https://issues.apache.org/jira/browse/HUDI-9216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

voon updated HUDI-9216:
-----------------------
    Fix Version/s: 1.0.2

> 1.x spark reader enforces database from tableConfig instead of defaulting to spark.catalog.currentDatabase as fallback
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDI-9216
>                 URL: https://issues.apache.org/jira/browse/HUDI-9216
>             Project: Apache Hudi
>          Issue Type: Bug
>            Reporter: Vinish Reddy
>            Assignee: Vinish Reddy
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.0.2
>
>
> Hudi as a table format doesn't enforce each table needs to be registered to one catalog. A user can take a hudi basePath, register it their own catalog with the database name of their choice and do spark SQL queries on it. Or am I understanding it incorrectly ? 
> 1.x spark reader tries to return the database as "default" instead of the database found in the sparkSession causing validation failures.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)