generated from camel.apache.org/component
Update wiki Home page for kudu
parent
32ce03d026
commit
26fff6e956
39
Home.md
39
Home.md
@ -1,21 +1,32 @@
|
|||||||
# Deploy the Project on CamelX Platform
|
# Kudu
|
||||||
|
|
||||||
Deploy on CamelX Platform in three steps
|
Interact with Apache Kudu, a free and open source column-oriented data store of the Apache Hadoop ecosystem.
|
||||||
|
|
||||||
## Step 1: Create a release
|
## Metadata
|
||||||
From the project space, click on **"Create a release"**
|
|
||||||
|
|
||||||
The new version is automatically available in the list
|
| Property | Value |
|
||||||
|
|----------|-------|
|
||||||
|
| Scheme | `kudu` |
|
||||||
|
| Support Level | Stable |
|
||||||
|
| Labels | database,iot,cloud |
|
||||||
|
| Version | 4.10.2 |
|
||||||
|
|
||||||
## Step 2: Deploy
|
## Maven Dependency
|
||||||
Click on **"Deploy"**
|
|
||||||
|
|
||||||
- **Version:** Select the desired release
|
```xml
|
||||||
- **Environment:** Choose `Development`, `Staging`, or `Production`
|
<dependency>
|
||||||
- **Configuration:** Select the configuration source
|
<groupId>org.apache.camel</groupId>
|
||||||
- **Resources:** Set CPU and Memory
|
<artifactId>camel-kudu</artifactId>
|
||||||
|
<version>4.10.2</version>
|
||||||
|
</dependency>
|
||||||
|
```
|
||||||
|
|
||||||
## Step 3: Expose
|
## Endpoint Properties
|
||||||
Enable **"Expose"**
|
|
||||||
|
|
||||||
Choose an **API Gateway** (Internal, Public, etc.)
|
| Name | Type | Required | Default | Description |
|
||||||
|
|------|------|----------|---------|-------------|
|
||||||
|
| `host` | string | ✓ | | Host of the server to connect to |
|
||||||
|
| `port` | string | ✓ | | Port of the server to connect to |
|
||||||
|
| `tableName` | string | | | Table to connect to |
|
||||||
|
| `operation` | object | | | Operation to perform |
|
||||||
|
| `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. |
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user