featurebase/test
Matt Jaffee 385381e5f3
fix issue where a shard with no data can cause query to fail
add Distinct test with integer data, and because one of the records
had a null value (and was in a shard by itself), it uncovered this
issue. I added a special error type if a view or fragment is not found
when so that we can match against it and ignore it when calculating
the results for a query.

I also added an implementation within executeCount to handle the
SignedRow case, but discovered that handlePrecalls always dumps the
negative data and that will be a bigger thing to fix
2020-12-23 14:37:03 -06:00
..
cluster.go fix issue where a shard with no data can cause query to fail 2020-12-23 14:37:03 -06:00
field.go database per shard, HolderConfig, rbf bit-wise import speedups. 2020-09-04 13:00:33 -05:00
handler.go remove the last usages of test.NewExecutor and cleanup unused in test package 2018-07-01 07:31:31 -05:00
holder.go blue_green migration. holdbkg.go holder goroutine. 2020-09-11 14:24:15 -05:00
index.go blue_green migration. holdbkg.go holder goroutine. 2020-09-11 14:24:15 -05:00
logger.go lock BufferLogger for reads/writes 2019-11-12 12:15:13 -06:00
pilosa.go Increase test http client timeout 2020-10-06 09:36:31 -06:00
pilosa_test.go testhook: leak auditing infrastructure 2020-08-24 11:26:39 -05:00
transaction.go increase test deadlineSkew to 1s 2020-05-18 19:57:44 -05:00