Elasticsearch's has already solved this problem. It would be a shame not to use it. Many changes are necessary, but many can be accelerated by adopting their solutions. It's even better here because you can then ensure backward compatibility with Elasticsearch. It tests it and the solution works. I can choose how to choose the value. There is a min and max search fix, Elasticsearch's was a bug in these functions when it comes to Storage.FLATTENED, I corrected that these functions would work the same as for Storage.NESTED. But the solution turns out to be effective and solves my problem. This can be supplemented with the option of defining a comparator when using native LuceneSearch sort predicates. Extend native instructions with the ability to download a multi value comparator. |