Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spark: 4.0 snapshot support #11583

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

huaxingao
Copy link
Contributor

No description provided.

import org.apache.spark.sql.catalyst.util.truncatedString
import org.apache.spark.sql.connector.iceberg.catalog.Procedure

case class IcebergCall(procedure: Procedure, args: Seq[Expression]) extends LeafCommand {
Copy link
Member

@pan3793 pan3793 Nov 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spark 4 already supports CALL syntax, and also brings the Call logical/physics plan node, instead of renaming it to IcebergCall, why not migrate the Iceberg procedures to the upstream procedure API?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is already very big. I want to make minimal changes to ensure that the current stored procedure continues to function, which is why I've renamed this to IcebergCall to avoid conflicts with Spark's CALL syntax. I think it probably better to migrate the Iceberg procedures in a follow-up PR.

@manuzhang
Copy link
Contributor

#11257 is no longer valid?

@huaxingao
Copy link
Contributor Author

@manuzhang The old PR has some conflicting files. If I rebase, it will also pick up changes for Spark 3.5, which I don't want. So, I opened a new PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants