Matthew Jaffee
Matthew Jaffee
Need to expose options so that PDK ingestion code can configure go-pilosa to use tracing. Additionally, the usual configuration will probably be that go-pilosa is writing to the same tracing...
Do the taxi import, then issue the following query and observe the result (edited error message for readability): ``` curl 10.1.110.70:10101/index/taxi/query -d'TopN(speed_mph)' curl 10.1.110.70:10101/index/taxi/query -d'TopN(speed_mph)' {"error": "executing: retrieving full counts:...
While doing some multi-cloud benchmarks, I noticed that the taxi import would use a "normal" (~10GB) amount of memory for a long time, and then suddenly over the course of...
currently we have a number of PDK commands for doing ingest, each of which tends to be based around a Source. Each one is pretty much the same with the...
The current Pilosa proxy has a couple limitations. 1. It only translates /query requests, and doesn't forward other requests to Pilosa. 2. It translates rows but not columns. 3. The...
The generic parser currently returns an error any time it fails to parse a field's value, and stops processing for that record. In reality, there are lots of innocuous reasons...
It's not a test, it just reads from kafka
currently, `pdk/import.go` contains import functionality which relies on importing `pilosa/ctl` and using that importer. We should remove this code and use the stuff in `pdk/pilosa.go` which uses the Go client...
The `net` subcommand contains an in-memory nexter implementation, and a generic string mapper. `taxi` has separated its mapping functionality out into a library, and I think it has come kind...
Detailed in a TODO comment as usual. ``` // TODO(jaffee) I think this may be very inefficient. It looks // like we're copying the `ids` and `values` slices over //...