-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zqd: Multipart log ingest #1336
Conversation
d20e354
to
c0b2e29
Compare
note: This will break brim master. I am working on an update there. |
General question... with this API it's now possible to post one or more files with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Yep! Good thinking from @alfred-landrum 😎 |
Will hold off on merging until we have accompanying changes on brim. |
607cb1e
to
d599d65
Compare
@brimsec/zq this is ready for another review. Now that both multipart and the former post path methods exist, this can go in without any brim dependent changes. |
98bc1fb
to
b0b92b3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Delete the empty files named file and file2.
0b59639
to
f0e1a47
Compare
Allow ingest of log data through streaming multi-part http request. The files are submitted as an http multipart request. JSON typing can be submitted as part of the request- it should be given the form value of "json_type_config". For http 1.1 the server cannot send responses back while the requester is sending data. As a result remove status updates and transmit any wires in the server responses. Clients that want to know the amount of data sent while the request is in flight will have to keep track the bytes written over the wire themselves. The zapi post commands have been reformatted. They are as such: - postpcap - post a pcap file to a space - postpath - post paths that will be opened and read by zqd. - post - stream log data to zqd over the network. Closes #1084
f0e1a47
to
8494a9c
Compare
Co-authored-by: Noah Treuhaft <noah.treuhaft@gmail.com>
Co-authored-by: Noah Treuhaft <noah.treuhaft@gmail.com>
Co-authored-by: Noah Treuhaft <noah.treuhaft@gmail.com>
45915ae
to
6b90064
Compare
ppl/zqd/handlers_test.go
Outdated
"#0:record[_path:string,ts:time,uid:bstring]", | ||
"0:[conn;2;CBrzd94qfowOqJwCHa;]", | ||
} | ||
const src1 = `#0:record[_path:string,ts:time,uid:bstring] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: align these first lines on the left side of the file
6b90064
to
e62a727
Compare
Rearrange zqd log post endpoint so log files are transmitted over
the network instead of opened from a locally available file.
The files are submitted as an http multipart request. JSON typing
can be submitted as part of the request- it should be given the
form value of "json_type_config".
For http 1.1 the server cannot send responses back while the
requester is sending data. As a result remove status updates and
transmit any wires in the server responses. Clients that want to
know the amount of data sent while the request is in flight will
have to keep track the bytes written over the wire themselves.
Closes #1084