42e3402806
as part of trying to simplify the core elasticRecheck, refactor the query creation into a separate set of query_builder routines. This takes away some of the duplication between the queries, and attempts to add documentation to the uses for each of them. add elasticRecheck fake pyelasticsearch testing build basic fixtures for unit testing that let us fake out the interaction to pyelasticsearch. This uses the json samples added for previous testing as the return results should an inbound query match one of the queries we know about. If the query is unknown to us, return an empty result set. Unit testing for both cases included going all the way from the top level Classifier class. Change-Id: I0d23b649274b31e8f281aaac588c4c6113a11a47
14 lines
227 B
JSON
14 lines
227 B
JSON
{
|
|
"hits": {
|
|
"hits": [],
|
|
"total": 0,
|
|
"max_score": null
|
|
},
|
|
"_shards": {
|
|
"successful": 75,
|
|
"failed": 0,
|
|
"total": 75
|
|
},
|
|
"took": 53,
|
|
"timed_out": false
|
|
} |