SEDONA-725 Add pyflink to Sedona.

[Imbruced]

Did you read the Contributor Guide?

• Yes, I have read the Contributor Rules and Contributor Development Guide

• No, I haven't read it.

Is this PR related to a ticket?

• Yes, and the PR name follows the format [SEDONA-XXX] my subject.

• Yes, and the PR name follows the format [GH-XXX] my subject.

• No:

  • this is a documentation update. The PR name follows the format [DOCS] my subject
  • this is a CI update. The PR name follows the format [CI] my subject

What changes were proposed in this PR?

How was this patch tested?

Did this PR include necessary documentation updates?

• Yes, I am adding a new API. I am using the current SNAPSHOT version number in vX.Y.Z format.
• Yes, I have updated the documentation.
• No, this PR does not affect any public API so no need to change the documentation.

[jiayuasu]

this is so cool. Do you think we'd better put pyflink as a new Python module to avoid conflicts with pyspark?

[james-willis]

should we keep the tool we use consistent across the project? we are using pipenv in the rest of the project AFAIK.

[Imbruced]

I plan to propose uv as a base tool for Python dependencies in Sedona. I think uv is the future https://github.com/astral-sh/uv
It's way more popular now and faster than, pipenv and poetry

[jbampton]

We were using Ruff - An extremely fast Python linter and code formatter, written in Rust, in our pre-commit framework but we changed to black.

It seems that Astral is modern popular fast tooling.

https://astral.sh/

https://github.com/astral-sh/ruff

#1368

https://github.com/psf/black

[jiayuasu]

Overall LGTM. Can you break this PR into 2 PRs? The first PR moves all Sedona PySpark stuff to Sedona Spark folder. The second PR adds the PyFlink. Does it make sense?

[Copilot]

Pull Request Overview

This PR updates the Sedona documentation and GitHub workflows to reflect the new pyflink and Sedona Spark APIs. It changes the import paths in various tutorial and API documentation files and adds concurrency configurations to multiple GitHub workflow files, as well as introducing a new pyflink test workflow.

• Updated import statements in tutorials and API docs to use sedona.spark modules.
• Fixed minor documentation typos in comments.
• Added concurrency configurations to workflows and introduced a new pyflink workflow.

Reviewed Changes

Copilot reviewed 225 out of 225 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
docs/tutorial/sql.md	Updated import paths and sample code for Sedona Spark modules; potential naming issue in function call.
docs/tutorial/rdd.md	Updated import paths for Spark modules in RDD-based tutorials and fixed spelling errors in comments.
docs/tutorial/geopandas-shapely.md	Updated import path for geoarrow to use sedona.spark.
docs/tutorial/files/stac-sedona-spark.md	Updated Stac client import to the Sedona Spark variant.
docs/tutorial/concepts/clustering-algorithms.md	Updated DBSCAN import to use sedona.spark.stats.
docs/setup/install-python.md	Updated Sedona registrator imports to use sedona.spark.
docs/api/sql/Visualization_SedonaPyDeck.md	Updated SedonaPyDeck import to use sedona.spark.
docs/api/sql/Visualization_SedonaKepler.md	Updated SedonaKepler import to use sedona.spark.
docs/api/sql/Raster-visualizer.md	Updated SedonaUtils import to use sedona.spark.
GitHub Workflows	Added concurrency configurations and updated Python test flags for skipping flink.
.github/workflows/pyflink.yml	Introduced a new workflow for Sedona Pyflink testing.

Comments suppressed due to low confidence (3)

docs/tutorial/sql.md:744

• The function is imported as 'add_binary_distance_band_column' but called using camelCase. Please update the function call to use snake_case for consistency.

weighted_df = addBinaryDistanceBandColumn(df, distance_radius)

docs/tutorial/rdd.md:172

• There is a typo in the comment: 'gemeotries' should be 'geometries'.

consider_boundary_intersection = False  ## Only return gemeotries fully covered by the window

docs/tutorial/rdd.md:291

• There is a typo in the comment: 'gemeotries' should be 'geometries'.

consider_boundary_intersection = False ## Only return gemeotries fully covered by the window

[Imbruced]

Overall LGTM. Can you break this PR into 2 PRs? The first PR moves all Sedona PySpark stuff to Sedona Spark folder. The second PR adds the PyFlink. Does it make sense?

Yeah, sure. I'm sorry for not getting back to you sooner. Can we merge this one first? #1924 It's helping to not spawn a lot of jobs in the CI

[jiayuasu]

@Imbruced Just merge that PR 😎