You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for new write workloads and InfluxDB v3 clients that write line protocol.
48
-
- [`/api/v2/write` endpoint]()
49
-
for InfluxDB v2 clients and bringing existing InfluxDB v2 write workloads to InfluxDB 3.
50
-
- [`/write` endpoint]() for InfluxDB v1 clients and bringing existing InfluxDB v1 write workloads to InfluxDB 3.
58
+
For new workloads, use the [`/api/v3/write_lp` endpoint](#operation/PostWriteLP).
51
59
52
-
All endpoints accept the same line protocol format and process data in the same way.
53
-
Like previous versions, InfluxDB 3 is a schema-on-write database, however tag column definitions for a table are immutable; you can't add tag columns to a table after it's created.
60
+
All endpoints accept the same line protocol format.
54
61
55
62
### Query data
56
63
57
-
InfluxDB 3 supports Flight+gRPC and HTTP requests for querying data.
64
+
Use the HTTP [`/query`](#operation/GetV1ExecuteQuery) endpoint for InfluxDB v1 clients and v1 query workloads using InfluxQL.
65
+
66
+
For new workloads, use one of the following:
58
67
59
-
- HTTP [`/api/v3/query_sql` endpoint]() for new query workloads using SQL.
60
-
- HTTP [`/api/v3/query_influxql` endpoint]() for new query workloads using InfluxQL.
61
-
- Flight SQL and InfluxDB 3 _Flight+gRPC_ APIs for querying with SQL or InfluxQL. For more information about using Flight+gRPC, see [InfluxDB 3 client libraries](https://github.com/InfluxCommunity).
62
-
- HTTP [`/query`]() endpoint for InfluxDB v1 clients and v1 query workloads using InfluxQL.
68
+
- HTTP [`/api/v3/query_sql` endpoint](#operation/GetExecuteQuerySQL) for new query workloads using SQL.
69
+
- HTTP [`/api/v3/query_influxql` endpoint](#operation/GetExecuteInfluxQLQuery) for new query workloads using InfluxQL.
70
+
- Flight SQL and InfluxDB 3 _Flight+gRPC_ APIs for querying with SQL or InfluxQL. For more information about using Flight APIs, see [InfluxDB 3 client libraries](https://github.com/InfluxCommunity).
63
71
64
72
### Server information
65
73
66
-
Server information endpoints are compatible with InfluxDB 1.x and InfluxDB 2.x clients.
74
+
Server information endpoints such as `/health` and `metrics` are compatible with InfluxDB 1.x and InfluxDB 2.x clients.
67
75
- name: Data I/O
68
76
description: Write and query data
69
77
- name: Databases
70
78
description: Create, read, update, and delete database and cache resources
79
+
- description: |
80
+
Most InfluxDB API endpoints require parameters in the request--for example, specifying the database to use.
81
+
82
+
### Common parameters
83
+
84
+
The following table shows common parameters used by many InfluxDB API endpoints.
85
+
Many endpoints may require other parameters in the query string or in the
86
+
request body that perform functions specific to those endpoints.
| `Accept` | string | The content type that the client can understand. |
100
+
| `Authorization` | string | The authorization scheme and credential. |
101
+
| `Content-Length` | integer | The size of the entity-body, in bytes. |
102
+
| `Content-Type` | string | The format of the data in the request body. |
103
+
name: Headers and parameters
104
+
x-traitTag: true
71
105
- name: Processing engine
72
-
description: Manage processing engine triggers and plugins
73
-
- name: Server information
74
-
description: Retrieve server metrics, status, and version information
75
-
- name: Tables
76
-
description: Manage table schemas and data
77
-
- name: Quick start
78
106
description: |
79
-
#### Get started with the InfluxDB HTTP API for InfluxDB 3 Core
107
+
Manage Processing engine triggers, test plugins, and send requests to trigger On Request plugins.
80
108
109
+
InfluxDB 3 Core provides the InfluxDB 3 Processing engine, an embedded Python VM that can dynamically load and trigger Python plugins in response to events in your database.
110
+
Use Processing engine plugins and triggers to run code and perform tasks for different database events.
111
+
112
+
To get started with the Processing engine, see the [Processing engine and Python plugins](/influxdb3/core/processing-engine/) guide.
113
+
- name: Quick start
114
+
description: |
81
115
1. [Check the status](#section/Server-information) of the InfluxDB server.
82
116
83
117
```bash
84
-
curl "http://localhost:9191/health"
118
+
curl "http://localhost:8181/health"
85
119
```
86
120
87
121
2. [Write data](#section/Compatibility-endpoints/Write-data) to InfluxDB.
0 commit comments