This PR mainly did the following 3 things:
- Refactor NewEtcdKV API
- Add unittests for `kv/etcd/`, raise the coverage
up to 94%
- Correct some APIs from version to revision
The old NewEtcdKV() API took `clientv3.Client` as
one of the input, making everyone who using this API
had to create a new `clientv3.Client`. So there're a lot
of repeated codes everywhere.
Meanwhile, someplace didn't even check whether the
`clientv3.New()` returned error or not, and the old API
also didn't check whether the clientv3.Client was Nil.
This caused issue#6955.
Ectd's version and revision have nothing alike, they
represent different concepts, but our APIs kind of
mixed them all up. So I correct those APIs' names.
Resolves: #6955
Signed-off-by: yangxuan <xuan.yang@zilliz.com>
* fix seek on pulsar msgstream
Signed-off-by: yefu.chen <yefu.chen@zilliz.com>
* test seek on pulsar msgstream
Signed-off-by: yefu.chen <yefu.chen@zilliz.com>
* msg-seek test test
Signed-off-by: yefu.chen <yefu.chen@zilliz.com>
* add pure pulsar client seek test
Signed-off-by: yefu.chen <yefu.chen@zilliz.com>
* optimize msgstream unittest
Signed-off-by: yudong.cai <yudong.cai@zilliz.com>
* get data service segment info channel name from config file directly
Signed-off-by: yudong.cai <yudong.cai@zilliz.com>
Pass a parameter `IsExpr` from proxy to query node, so query
node can create search plan according to the variable `IsExpr`.
It makes `segcore` unnecessary to distinguish `dsl` or `expr`
using dynamic exception. When `IsExpr` is set to true, query
node will call `CreatePlanByExpr` according to the passed
information about expression. Otherwise query node will keep
still to use `CreatePlan` according to the `dsl` information. At
the same time, this pr adds some unittests to `CreatePlanByExpr`,
these unittests translate already exist case with `dsl` to case with
`expr`.
Signed-off-by: dragondriver <jiquan.long@zilliz.com>
