hcq/influx-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: update to go 1.19 (#465) (#467)

Browse Source 
* chore: upgrade go releaser to v1.13.1 (#464)

* chore: update goreleaser and actually use go 1.19

* chore: format for go 1.19

Co-authored-by: Brandon Pfeifer <bpfeifer@influxdata.com>

Co-authored-by: Brandon Pfeifer <bpfeifer@influxdata.com>
This commit is contained in:
Jeffrey Smith II
2023-01-03 16:16:12 -05:00
committed by GitHub
parent 5546ab6ea7
commit ae62da0b32
17 changed files with 386 additions and 365 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
api/api_write.gen.go
View File

@ -193,8 +193,8 @@ func (r ApiPostWriteRequest) ExecuteWithHttpInfo() (*_nethttp.Response, error) {
}
/*
* PostWrite Write data
* Writes data to a bucket.
- PostWrite Write data
- Writes data to a bucket.
Use this endpoint to send data in [line protocol]({{% INFLUXDB_DOCS_URL %}}/reference/syntax/line-protocol/) format to InfluxDB.
@ -202,27 +202,29 @@ Use this endpoint to send data in [line protocol]({{% INFLUXDB_DOCS_URL %}}/refe
- Does the following when you send a write request:
1. Validates the request and queues the write.
2. If queued, responds with _success_ (HTTP `2xx` status code); _error_ otherwise.
3. Handles the delete asynchronously and reaches eventual consistency.
1. Validates the request and queues the write.
To ensure that InfluxDB Cloud handles writes and deletes in the order you request them,
wait for a success response (HTTP `2xx` status code) before you send the next request.
2. If queued, responds with _success_ (HTTP `2xx` status code); _error_ otherwise.
Because writes and deletes are asynchronous, your change might not yet be readable
when you receive the response.
3. Handles the delete asynchronously and reaches eventual consistency.
To ensure that InfluxDB Cloud handles writes and deletes in the order you request them,
wait for a success response (HTTP `2xx` status code) before you send the next request.
Because writes and deletes are asynchronous, your change might not yet be readable
when you receive the response.
#### InfluxDB OSS
- Validates the request and handles the write synchronously.
- If all points were written successfully, responds with HTTP `2xx` status code;
otherwise, returns the first line that failed.
- Validates the request and handles the write synchronously.
- If all points were written successfully, responds with HTTP `2xx` status code;
otherwise, returns the first line that failed.
#### Required permissions
- `write-buckets` or `write-bucket BUCKET_ID`.
*`BUCKET_ID`* is the ID of the destination bucket.
*`BUCKET_ID`* is the ID of the destination bucket.
#### Rate limits (with InfluxDB Cloud)
@ -235,8 +237,8 @@ For more information, see [limits and adjustable quotas](https://docs.influxdata
- [Optimize writes to InfluxDB]({{% INFLUXDB_DOCS_URL %}}/write-data/best-practices/optimize-writes/)
- [Troubleshoot issues writing data]({{% INFLUXDB_DOCS_URL %}}/write-data/troubleshoot/)
* @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
* @return ApiPostWriteRequest
- @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
- @return ApiPostWriteRequest
*/
func (a *WriteApiService) PostWrite(ctx _context.Context) ApiPostWriteRequest {
return ApiPostWriteRequest{