Closed var77 closed 1 year ago
metric | old | new | pct change |
---|---|---|---|
recall (after create) | 0.740 | 0.740 | - |
recall (after insert) | 0.742 | 0.764 | +2.96% |
select bulk tps | 218.594 | 228.773 | +4.66% |
select bulk latency (ms) | 34.397 | 33.716 | -1.98% |
select bulk latency (stddev ms) | 11.556 | 9.489 | -17.89% |
create latency (ms) | 1570.497 | 1456.375 | -7.27% |
insert bulk tps | 13.726 | 14.685 | +6.99% |
insert bulk latency (ms) | 72.843 | 68.082 | -6.54% |
insert bulk latency (stddev ms) | 3.065 | 2.094 | -31.68% |
disk usage (bytes) | 6348800.000 | 6348800.000 | - |
Currently after creating an index with expression, we are not able to query it using <->
operator as the operator usage check fails. I have described the issue in this comment . Should we fix the issue in this PR or work on it in a different PR?
cc: @Ngalstyan4 @dqii
Merging #175 (311b985) into main (e87563a) will decrease coverage by
0.14%
. Report is 1 commits behind head on main. The diff coverage is86.66%
.
Description
When index is being created via expression and
dim
option is not passed we can not infer the array dimensions from the table row. So by this PR we will check if the expression list is not empty when inferring the dimensions, we will evaluate the expression over the first row of the table and try to get the array dimensions from the result.Relates to #174 Issue #162