Navneet Verma
                                            Navneet Verma
                                        
                                    Hi @alisazosimova I can see that you want to do the aggregation on the field type `geo_shape`. We are currently working on building the aggregations on `geo_shape`. Please refer this...
@AlexRuiz7 in the zip folder of k-NN the lib is empty because the content of the lib are platform dependent. Can you please add some details how this is impacting...
@AlexRuiz7 please create an issue in https://github.com/opensearch-project/opensearch-build repo. The maintainers of that repo can ans this question. Right now I am unable to transfer this issue to opensearch-build.
> @navneet1v Easy test: > > 1. create index with > > ``` > {"mappings":{"_source": {"excludes": ["vector_field1"] }, "properties": {"vector_field1": {"type": "knn_vector", "dimension": 2 }, "vector_field2": {"type": "knn_vector", "dimension": 4...
> > My question was how we are ensuring that KNNSubphase is not running during the search and running only during the re-indexing. > > @navneet1v gotcha, I will do...
> @navneet1v @jmazanec15 i rebased it from master. and would you pls review it? > > and i see @navneet1v have an issue: [opensearch-project/OpenSearch#13490](https://github.com/opensearch-project/OpenSearch/issues/13490), i am wondering this pr could...
> > My question was how we are ensuring that KNNSubphase is not running during the search and running only during the re-indexing. > > @navneet1v i tested search source...
> @navneet1v @jmazanec15 > > At [469fbf3](https://github.com/opensearch-project/k-NN/commit/469fbf3af3c2a7956537aa0b8760f70c3eb575e3) i added nested field process logic. and added tests for update, search, reindex, nested scenarios. > > > can we test update use...
> 2nd scenarios i think it is because that we synthetic at `KNNFetchSubPhase` which is in `FetchPhase`. Yes I thought so.
@jmazanec15 this is inline to the thought I had when creating this issue. Do we see any other alternative here? I see one, which is creating a new query clause...