From a4c3a607132c78b8975b183dfa46d16b6e07d14a Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Wed, 11 Mar 2026 14:37:54 +0000
Subject: [PATCH] Update wiki Home page for flink

---
 Home.md | 41 +++++++++++++++++++++++++++--------------
 1 file changed, 27 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..30714c1 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,34 @@
-# Deploy the Project on CamelX Platform
+# Flink
 
-Deploy on CamelX Platform in three steps
+Send DataSet jobs to an Apache Flink cluster.
 
-## Step 1: Create a release
-From the project space, click on **"Create a release"**
+## Metadata
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `flink` |
+| Support Level | Stable |
+| Labels | transformation,bigdata |
+| Version | 4.10.2 |
 
-## Step 2: Deploy
-Click on **"Deploy"**
+## Maven Dependency
 
-- **Version:** Select the desired release
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
-- **Configuration:** Select the configuration source
-- **Resources:** Set CPU and Memory
+```xml
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-flink</artifactId>
+    <version>4.10.2</version>
+</dependency>
+```
 
-## Step 3: Expose
-Enable **"Expose"**
+## Endpoint Properties
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `endpointType` | object | ✓ |  | Type of the endpoint (dataset, datastream). |
+| `collect` | boolean |  | `true` | Indicates if results should be collected or counted. |
+| `dataSet` | object |  |  | DataSet to compute against. |
+| `dataSetCallback` | object |  |  | Function performing action against a DataSet. |
+| `dataStream` | object |  |  | DataStream to compute against. |
+| `dataStreamCallback` | object |  |  | Function performing action against a DataStream. |
+| `lazyStartProducer` | boolean |  | `false` | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |