Every token consist of payload representing our own custom position value.
Use of Custom Plugin:
During processing of Term, we use the term's payload as the position.
During the processing of nextDoc, we only select the document whose queried term has the same position.
Every term wrapped inside this query should have the same position (in case of our same payload information)
Profiling the query:
- Processing is taking time during 'nextDoc' step
Processing of the custom query plugin is taking a longer time.
- Total Docs : ~ 1 Million
- Master Node : 1
- Data Node : 2
Master Node Configuration: 8 vcpu, 61 GB RAM, SSD , (AWS instance: i3.2xlarge)
Data Node Configuration: 8 vcpu, 61 GB RAM, SSD , (AWS instance: i3.2xlarge)
- Is there a way to set term position during indexing ?
- Processing of custom query is taking a longer time. (Comparing this process with span query). Is there some way to increase the performance using this positional approach?