scriptoriumadmin/featurebase
1
0
Fork 0
mirror of https://github.com/featurebasedb/featurebase.git synced 2026-08-28 10:54:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

address CR feedback

Browse source
This commit is contained in:
Matt Jaffee 2018-10-23 13:50:35 -05:00
parent 4eed160b2d
commit 376c2d61ff
No known key found for this signature in database
GPG key ID: 08A3DFFF987B11BF
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/api-reference.md
View file

@ -96,7 +96,7 @@ By default, all bits and attributes (*for `Row` queries only*) are returned. In
### Import Data
`POST /index/<index-name>/field/<field-name>`
`POST /index/<index-name>/field/<field-name>/import`
Supports high-rate data ingest to a particular shard of a particular field. The
official client libraries use this endpoint for their import functionality - it
@ -106,13 +106,13 @@ imports for
<a href="https://github.com/pilosa/java-pilosa/blob/master/docs/imports.md">Java</a>,
and <a href="https://github.com/pilosa/python-pilosa/tree/master/docs/imports.md">Python</a>.
The request payload is protobuf encoded with the following schema. The row or
column Keys fields are used if the field or index is configured for keys
respectively. Otherwise, the RowIDs and ColumnIDs fields are used. They must
have the same number of items, and each index into those two lists represents a
particular bit to be set. Timestamps are optional, but if they exist must also
contain the same number of items as rows and columns. The column IDs must all be
in the shard specified in the request.
The request payload is protobuf encoded with the following schema. The RowKeys
and/or ColumnKeys fields are used if the pilosa field or index are configured
for keys respectively. Otherwise, the RowIDs and ColumnIDs fields are used. They
must have the same number of items, and each index into those two lists
represents a particular bit to be set. Timestamps are optional, but if they
exist must also contain the same number of items as rows and columns. The
column IDs must all be in the shard specified in the request.
```
message ImportRequest {