featurebase/http
Seebs c7e4bc0fd0 refactoring experiment
I'm not actually sold on this, but I'm not entirely unsold on it. It seems like
it does reduce the amount of duplication a lot, but also it's sort of a mess.

In the process, noticed that it makes more sense to grab the whole cluster
rather than just the nodes for an arbitrary shard for the shard==^0 case,
because then if we have an API (but no Qcx), we can be reasonably confident
that we'll be able to pick the local node for loopback even if we aren't
using the API directly.

Have thought about whether we should create our own Qcx in cases like that
but I really don't like the idea of automatically creating a Qcx.
2021-11-05 13:06:38 -05:00
..
client.go refactoring experiment 2021-11-05 13:06:38 -05:00
client_test.go Import/ImportValue API rework and improvements 2021-11-05 13:06:38 -05:00
error.go Fix linter issues: vet 2018-07-19 11:37:50 -05:00
handler.go fix govet and gofmt errors in existing code 2021-10-29 13:14:27 -05:00
handler_internal_test.go Add schema endpoint 2021-08-19 09:50:59 -05:00
handler_test.go ingest and ingest/codec testing work 2021-08-19 09:50:59 -05:00
translator.go FeatureBase Renaming: changing go.mod module name for featurebase 2021-07-19 09:20:30 -07:00
translator_test.go FeatureBase Renaming: changing go.mod module name for featurebase 2021-07-19 09:20:30 -07:00