-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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-50849][Connect] Add example project to demonstrate Spark Connect Server Libraries #49604
Open
vicennial
wants to merge
4
commits into
apache:master
Choose a base branch
from
vicennial:connectExamples
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,334
−0
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,133 @@ | ||
# Spark Server Library Example - Custom Datasource Handler | ||
|
||
This example demonstrates a modular maven-based project architecture with separate client, server | ||
and common components. It leverages the extensibility of Spark Connect to create a server library | ||
that may be attached to the server to extend the functionality of the Spark Connect server as a whole. Below is a detailed overview of the setup and functionality. | ||
|
||
## Project Structure | ||
|
||
``` | ||
├── common/ # Shared protobuf/utilities/classes | ||
├── client/ # Sample client implementation | ||
│ ├── src/ # Source code for client functionality | ||
│ ├── pom.xml # Maven configuration for the client | ||
├── server/ # Server-side plugin extension | ||
│ ├── src/ # Source code for server functionality | ||
│ ├── pom.xml # Maven configuration for the server | ||
├── resources/ # Static resources | ||
├── pom.xml # Parent Maven configuration | ||
``` | ||
|
||
## Functionality Overview | ||
|
||
To demonstrate the extensibility of Spark Connect, a custom datasource handler, `CustomTable` is | ||
implemented in the server module. The class handles reading, writing and processing data stored in | ||
a custom format, here we simply use the `.custom` extension (which itself is a wrapper over `.csv` | ||
files). | ||
|
||
First and foremost, the client and the server must be able to communicate with each other through | ||
custom messages that 'understand' our custom data format. This is achieved by defining custom | ||
protobuf messages in the `common` module. The client and server modules both depend on the `common` | ||
module to access these messages. | ||
- `common/src/main/protobuf/base.proto`: Defines the base `CustomTable` which is simply represented | ||
by a path and a name. | ||
```protobuf | ||
message CustomTable { | ||
string path = 1; | ||
string name = 2; | ||
} | ||
``` | ||
- `common/src/main/protobuf/commands.proto`: Defines the custom commands that the client can send | ||
to the server. These commands are typically operations that the server can perform, such as cloning | ||
an existing custom table. | ||
```protobuf | ||
message CustomCommand { | ||
oneof command_type { | ||
CreateTable create_table = 1; | ||
CloneTable clone_table = 2; | ||
} | ||
} | ||
``` | ||
- `common/src/main/protobuf/relations.proto`: Defines custom `relations`, which are a mechanism through which an optional input dataset is transformed into an | ||
output dataset such as a Scan. | ||
```protobuf | ||
message Scan { | ||
CustomTable table = 1; | ||
} | ||
``` | ||
|
||
On the client side, the `CustomTable` class mimics the style of Spark's `Dataset` API, allowing the | ||
user to perform and chain operations on a `CustomTable` object. | ||
|
||
On the server side, a similar `CustomTable` class is implemented to handle the core functionality of | ||
reading, writing and processing data in the custom format. The plugins (`CustomCommandPlugin` and | ||
`CustomRelationPlugin`) are responsible for processing the custom protobuf messages sent from the client | ||
(those defined in the `common` module) and delegating the appropriate actions to the `CustomTable`. | ||
|
||
|
||
|
||
## Build and Run Instructions | ||
|
||
1. **Navigate to the sample project from `SPARK_HOME`**: | ||
```bash | ||
cd connect-examples/server-library-example | ||
``` | ||
|
||
2. **Build and package the modules**: | ||
```bash | ||
mvn clean package | ||
``` | ||
|
||
3. **Download the `4.0.0-preview2` release to use as the Spark Connect Server**: | ||
- Choose a distribution from https://archive.apache.org/dist/spark/spark-4.0.0-preview2/. | ||
- Example: `curl -L https://archive.apache.org/dist/spark/spark-4.0.0-preview2/spark-4.0.0-preview2-bin-hadoop3.tgz | tar xz` | ||
|
||
4. **Copy relevant JARs to the root of the unpacked Spark distribution**: | ||
```bash | ||
cp \ | ||
<SPARK_HOME>/connect-examples/server-library-example/resources/spark-daria_2.13-1.2.3.jar \ | ||
<SPARK_HOME>/connect-examples/server-library-example/common/target/spark-server-library-example-common-1.0-SNAPSHOT.jar \ | ||
<SPARK_HOME>/connect-examples/server-library-example/server/target/spark-server-library-example-server-extension-1.0-SNAPSHOT.jar \ | ||
. | ||
``` | ||
5. **Start the Spark Connect Server with the relevant JARs**: | ||
```bash | ||
bin/spark-connect-shell \ | ||
--jars spark-server-library-example-server-extension,spark-server-library-example-common-1.0-SNAPSHOT.jar,spark-daria_2.13-1.2.3.jar \ | ||
--conf spark.connect.extensions.relation.classes=org.example.CustomRelationPlugin \ | ||
--conf spark.connect.extensions.command.classes=org.example.CustomCommandPlugin | ||
``` | ||
6. **In a different terminal, navigate back to the root of the sample project and start the client**: | ||
```bash | ||
java -cp client/target/spark-server-library-client-package-scala-1.0-SNAPSHOT.jar org.example.Main | ||
``` | ||
7. **Notice the printed output in the client terminal as well as the creation of the cloned table**: | ||
```protobuf | ||
Explaining plan for custom table: sample_table with path: <SPARK_HOME>/spark/connect-examples/server-library-example/client/../resources/dummy_data.custom | ||
== Parsed Logical Plan == | ||
Relation [id#2,name#3] csv | ||
|
||
== Analyzed Logical Plan == | ||
id: int, name: string | ||
Relation [id#2,name#3] csv | ||
|
||
== Optimized Logical Plan == | ||
Relation [id#2,name#3] csv | ||
|
||
== Physical Plan == | ||
FileScan csv [id#2,name#3] Batched: false, DataFilters: [], Format: CSV, Location: InMemoryFileIndex(1 paths)[file:/Users/venkata.gudesa/spark/connect-examples/server-library-example/resou..., PartitionFilters: [], PushedFilters: [], ReadSchema: struct<id:int,name:string> | ||
|
||
Explaining plan for custom table: cloned_table with path: <SPARK_HOME>/connect-examples/server-library-example/client/../resources/cloned_data.custom | ||
== Parsed Logical Plan == | ||
Relation [id#2,name#3] csv | ||
|
||
== Analyzed Logical Plan == | ||
id: int, name: string | ||
Relation [id#2,name#3] csv | ||
|
||
== Optimized Logical Plan == | ||
Relation [id#2,name#3] csv | ||
|
||
== Physical Plan == | ||
FileScan csv [id#2,name#3] Batched: false, DataFilters: [], Format: CSV, Location: InMemoryFileIndex(1 paths)[file:/Users/venkata.gudesa/spark/connect-examples/server-library-example/resou..., PartitionFilters: [], PushedFilters: [], ReadSchema: struct<id:int,name:string> | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,112 @@ | ||
<?xml version="1.0" encoding="UTF-8"?> | ||
<!-- | ||
~ Licensed to the Apache Software Foundation (ASF) under one or more | ||
~ contributor license agreements. See the NOTICE file distributed with | ||
~ this work for additional information regarding copyright ownership. | ||
~ The ASF licenses this file to You under the Apache License, Version 2.0 | ||
~ (the "License"); you may not use this file except in compliance with | ||
~ the License. You may obtain a copy of the License at | ||
~ | ||
~ http://www.apache.org/licenses/LICENSE-2.0 | ||
~ | ||
~ Unless required by applicable law or agreed to in writing, software | ||
~ distributed under the License is distributed on an "AS IS" BASIS, | ||
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
~ See the License for the specific language governing permissions and | ||
~ limitations under the License. | ||
--> | ||
|
||
<project xmlns="http://maven.apache.org/POM/4.0.0" | ||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> | ||
<modelVersion>4.0.0</modelVersion> | ||
|
||
<parent> | ||
<groupId>org.example</groupId> | ||
<artifactId>spark-server-library-example</artifactId> | ||
<version>1.0-SNAPSHOT</version> | ||
<relativePath>../pom.xml</relativePath> | ||
</parent> | ||
|
||
<artifactId>spark-server-library-client-package-scala</artifactId> | ||
<packaging>jar</packaging> | ||
|
||
<dependencies> | ||
<!-- Custom Proto definitions are in the common module --> | ||
<dependency> | ||
<groupId>org.example</groupId> | ||
<artifactId>spark-server-library-example-common</artifactId> | ||
<version>1.0-SNAPSHOT</version> | ||
<exclusions> | ||
<exclusion> | ||
<groupId>com.google.protobuf</groupId> | ||
<artifactId>protobuf-java</artifactId> | ||
</exclusion> | ||
</exclusions> | ||
</dependency> | ||
<!-- spark-connect-common contains proto definitions that we require to build custom commands/relations/expressions --> | ||
<dependency> | ||
<groupId>org.apache.spark</groupId> | ||
<artifactId>spark-connect-common_${scala.binary}</artifactId> | ||
<version>${spark.version}</version> | ||
</dependency> | ||
<!-- Dependency on the spark connect client module to interact with the Spark server --> | ||
<dependency> | ||
<groupId>org.apache.spark</groupId> | ||
<artifactId>spark-connect-client-jvm_${scala.binary}</artifactId> | ||
<version>${spark.version}</version> | ||
</dependency> | ||
<!-- Dependency on the scala library --> | ||
<dependency> | ||
<groupId>org.scala-lang</groupId> | ||
<artifactId>scala-library</artifactId> | ||
<version>${scala.version}</version> | ||
</dependency> | ||
|
||
</dependencies> | ||
|
||
<build> | ||
<sourceDirectory>src/main/scala</sourceDirectory> | ||
<plugins> | ||
<!-- Scala --> | ||
<plugin> | ||
<!-- see http://davidb.github.com/scala-maven-plugin --> | ||
<groupId>net.alchim31.maven</groupId> | ||
<artifactId>scala-maven-plugin</artifactId> | ||
<version>4.9.2</version> | ||
<executions> | ||
<execution> | ||
<goals> | ||
<goal>compile</goal> | ||
<goal>testCompile</goal> | ||
</goals> | ||
</execution> | ||
</executions> | ||
</plugin> | ||
|
||
<!-- Shade plugin for creating a fat JAR --> | ||
<plugin> | ||
<groupId>org.apache.maven.plugins</groupId> | ||
<artifactId>maven-shade-plugin</artifactId> | ||
<version>3.5.1</version> | ||
<executions> | ||
<execution> | ||
<phase>package</phase> | ||
<goals> | ||
<goal>shade</goal> | ||
</goals> | ||
<configuration> | ||
<shadedArtifactAttached>false</shadedArtifactAttached> | ||
<promoteTransitiveDependencies>true</promoteTransitiveDependencies> | ||
<createDependencyReducedPom>false</createDependencyReducedPom> | ||
<!--SPARK-42228: Add `ServicesResourceTransformer` to relocation class names in META-INF/services for grpc--> | ||
<transformers> | ||
<transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/> | ||
</transformers> | ||
</configuration> | ||
</execution> | ||
</executions> | ||
</plugin> | ||
</plugins> | ||
</build> | ||
</project> |
30 changes: 30 additions & 0 deletions
30
connect-examples/server-library-example/client/src/main/resources/log4j2.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
<?xml version="1.0" encoding="UTF-8"?> | ||
<!-- | ||
~ Licensed to the Apache Software Foundation (ASF) under one or more | ||
~ contributor license agreements. See the NOTICE file distributed with | ||
~ this work for additional information regarding copyright ownership. | ||
~ The ASF licenses this file to You under the Apache License, Version 2.0 | ||
~ (the "License"); you may not use this file except in compliance with | ||
~ the License. You may obtain a copy of the License at | ||
~ | ||
~ http://www.apache.org/licenses/LICENSE-2.0 | ||
~ | ||
~ Unless required by applicable law or agreed to in writing, software | ||
~ distributed under the License is distributed on an "AS IS" BASIS, | ||
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
~ See the License for the specific language governing permissions and | ||
~ limitations under the License. | ||
--> | ||
|
||
<Configuration status="WARN"> | ||
<Appenders> | ||
<Console name="Console" target="SYSTEM_OUT"> | ||
<PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss} [%t] %-5level %logger{36} - %msg%n" /> | ||
</Console> | ||
</Appenders> | ||
<Loggers> | ||
<Root level="info"> | ||
<AppenderRef ref="Console" /> | ||
</Root> | ||
</Loggers> | ||
</Configuration> |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spark Server
->Spark Connect Server
?