Skip to content

Conversation

Alibaba-HZY
Copy link
Contributor

Purpose

Linked issue: open #228
Linked issue: open #155

Support spark catalog and introduce some basic classes to support spark read and write

Brief change log

1.Based on #258 and discussion with @XuQianJin-Stars , I resubmitted [support spakr catalog ] and introduce some basic classes(SparkInternalRow,SparkRow,FlussInputPartition) to support spark read and write.
2.support SupportsPartitionManagement in spark table

Tests

com.alibaba.fluss.connector.spark.catalog.SparkCatalogITCase
com.alibaba.fluss.connector.spark.utils.SparkConversionsTest
com.alibaba.fluss.connector.spark.utils.SparkTypeUtilsTest
com.alibaba.fluss.connector.spark.SparkInternalRowTest

API and Format

no

Documentation

no

@Alibaba-HZY
Copy link
Contributor Author

@wuchong cc

@Alibaba-HZY Alibaba-HZY force-pushed the spark-catalog branch 5 times, most recently from abe3482 to be8528e Compare March 10, 2025 03:46
@XuQianJin-Stars
Copy link
Contributor

hi @Alibaba-HZY This PR looks good overall, I will review it later. Thanks.

@wuchong
Copy link
Member

wuchong commented Mar 14, 2025

Sorry, I just merged #597 and causes some conflicts in this PR. The main change of #594 is moving fluss-connectors/fluss-connector-flink to a top-level module fluss-flink with sub-modules for different Flink versions. This can make the module structure much simpler.

Therefore, we can also move fluss-connectors/fluss-connector-flink to a top-level module fluss-spark with sub-modules for different Spark versions.

@Alibaba-HZY
Copy link
Contributor Author

Sorry, I just merged #597 and causes some conflicts in this PR. The main change of #594 is moving fluss-connectors/fluss-connector-flink to a top-level module fluss-flink with sub-modules for different Flink versions. This can make the module structure much simpler.

Therefore, we can also move fluss-connectors/fluss-connector-flink to a top-level module fluss-spark with sub-modules for different Spark versions.

ok i will handle this

@Alibaba-HZY
Copy link
Contributor Author

Sorry, I just merged #597 and causes some conflicts in this PR. The main change of #594 is moving fluss-connectors/fluss-connector-flink to a top-level module fluss-flink with sub-modules for different Flink versions. This can make the module structure much simpler.

Therefore, we can also move fluss-connectors/fluss-connector-flink to a top-level module fluss-spark with sub-modules for different Spark versions.

down

@wuchong wuchong added this to the v0.8 milestone Jun 8, 2025
@MaggieSullivan
Copy link

MaggieSullivan commented Aug 16, 2025

@wuchong @Alibaba-HZY @polyzos Do you mind if I pick this up and make some improvements for v0.8?

@polyzos
Copy link
Contributor

polyzos commented Aug 30, 2025

Since there hasn't been activity for a while now, I'm assigning to you @MaggieSullivan. Thank you for your interest 🥇

@polyzos polyzos assigned polyzos and MaggieSullivan and unassigned polyzos Aug 30, 2025
@polyzos polyzos merged commit 133933d into apache:main Aug 31, 2025
polyzos added a commit to polyzos/fluss that referenced this pull request Aug 31, 2025
@polyzos
Copy link
Contributor

polyzos commented Aug 31, 2025

@Alibaba-HZY Apologies, I tried to rebase this branch as it had way too many conflicts to take a look at and somehow I messed things up big time. I don't know how I managed to merge from my cli, and now seems like changed file tracking is lost .. I'm still trying to figure out if there is something I can do to fix this, but no luck so far 😰

@Alibaba-HZY
Copy link
Contributor Author

@Alibaba-HZY Apologies, I tried to rebase this branch as it had way too many conflicts to take a look at and somehow I messed things up big time. I don't know how I managed to merge from my cli, and now seems like changed file tracking is lost .. I'm still trying to figure out if there is something I can do to fix this, but no luck so far 😰
i think you need revert this pr first i will try solve this conflicts in tomorrow.

@polyzos
Copy link
Contributor

polyzos commented Aug 31, 2025

@Alibaba-HZY The changes from main were reverted immediately. However, I'm not sure how I managed to mess up your PR-branch, and nothing I tried worked.
Would you mind opening a new PR? Again, I'm really sorry for all this inconvenience.

@Alibaba-HZY
Copy link
Contributor Author

Alibaba-HZY commented Aug 31, 2025 via email

@polyzos
Copy link
Contributor

polyzos commented Sep 3, 2025

@Alibaba-HZY, just a reminder, if you can re-open this PR 🙇

@Alibaba-HZY
Copy link
Contributor Author

Alibaba-HZY commented Sep 3, 2025 via email

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

Successfully merging this pull request may close these issues.

5 participants