[
https://issues.apache.org/jira/browse/SPARK-61826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SPARK-61826:
-----------------------------------
Labels: pull-request-available (was: )
> Projects generated by spark-pipelines init lose their tables after the run
> and fail the second run with LOCATION_ALREADY_EXISTS
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-61826
> URL: https://issues.apache.org/jira/browse/SPARK-61826
> Project: Spark
> Issue Type: Bug
> Components: Declarative Pipelines
> Affects Versions: 4.3.0
> Reporter: Sudhanva Huruli
> Priority: Major
> Labels: pull-request-available
>
> spark-pipelines init writes a spec without a catalog setting, so a run uses
> the in-memory session catalog. When the run ends the tables are forgotten,
> but their folders stay under spark-warehouse/, so the second spark-pipelines
> run fails with LOCATION_ALREADY_EXISTS and the tables cannot be queried from
> spark-sql or pyspark after the run. The generated spark-pipeline.yml should
> set spark.sql.catalogImplementation: hive so metadata persists in a local
> metastore_db/.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]