camel-apache-org/weaviate
camel-apache-org/weaviate
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Update wiki Home page for weaviate

gitea_admin 2026-10-12 05:41:21 +00:00
parent 3361da385b
commit cd75db1e16
1 changed files with 28 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
Home.md

@ -1,21 +1,35 @@
# Deploy the Project on CamelX Platform
# weaviate
Deploy on CamelX Platform in three steps
Perform operations on the Weaviate Vector Database.
## 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 | `weaviate` |
| Support Level | Stable |
| Labels | database,ai |
| Version | 4.20.0 (CEQ 3.36.0) |
## 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.quarkus</groupId>
<artifactId>camel-quarkus-weaviate</artifactId>
<version>4.20.0 (CEQ 3.36.0)</version>
</dependency>
```
## Step 3: Expose
Enable **"Expose"**
## Endpoint Properties
Choose an **API Gateway** (Internal, Public, etc.)
| Name | Type | Required | Default | Description |
|------|------|----------|---------|-------------|
| `collection` | string | ✓ | | The collection Name |
| `apiKey` | string | | | API Key to authenticate to weaviate with |
| `host` | string | | | Weaviate server host to connect to |
| `proxyHost` | string | | | Proxy host to connect to weaviate through |
| `proxyPort` | integer | | | Proxy port to connect to weaviate through |
| `proxyScheme` | string | | | Proxy scheme to connect to weaviate through |
| `scheme` | string | | | Scheme used to connect to weaviate |
| `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. |