Skip to content

Support for writing to existing Iceberg tables in S3 from C# service in ECS #1206

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

Open
MPeli opened this issue Apr 16, 2025 · 1 comment
Open

Comments

@MPeli
Copy link

MPeli commented Apr 16, 2025

Hello .NET for Apache Spark team,

We're exploring the possibility of using .NET for Apache Spark to optimize our current data pipeline. Our scenario is as follows:

Current setup:

  • C# service running in Amazon ECS writes data to an Amazon Kinesis stream
  • AWS Glue job reads from this stream and writes to Iceberg tables in S3

Desired setup:

  • C# service running in Amazon ECS writes directly to the same Iceberg tables in S3 that our Glue jobs are currently writing to, bypassing Kinesis and Glue

Our main question:

Is it possible to use .NET for Apache Spark within a C# service running in ECS to write directly to existing Iceberg tables in S3? If so, could you provide a high-level overview of how this might be implemented?

We appreciate any insights or documentation you can provide to help us evaluate the feasibility of this approach.

Thank you for your time and assistance!

@wudanzy
Copy link
Collaborator

wudanzy commented May 7, 2025

I think currently that's not supported, to use Spark you will need to deploy it into a cluster management framework, such as Yarn or Kubernetes, or use the spark standalone cluster. And then you can use it.

In our case, I don't have much knowledge on ECS, but from the name it sounds like a framework that can allow you to run arbitrary services. In such case, you may bring up a spark standalone cluster, e.g. spark master on some machines and spark workers on others.

You will need to prototype on the idea to see whether it works.

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

No branches or pull requests

2 participants