Improve search queries

[jamiehewitt15]

Closes: #678

Changes proposed in this PR:

• Improving the search functionality. For example, previously if you searched for "data union" it would not return "DataUnion.App", now this has been corrected.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/oceanprotocol/market/FeenipgDNq7KLgQmXwcQu8gjv5Fc
✅ Preview: https://market-git-issue-678-improve-search-oceanprotocol.vercel.app

[claudiaHash]

The new search works great! Although, I think there might be an issue when combining searching with filtering. For example, selecting ALGORTIHMS I got the following results:

[mihaisc]

The issue we still add in query service.attributes.main.type:algorithm, i saw this in the multinetwork branch. In this case is incorrect and in multi is not optimal ( at this point the difference is minimal ). The correct way is to add a term

 {
       "term":{
               "service.attributes.main.type": "algorithm"
          }
}

[jamiehewitt15]

@claudiaHash Thank you for pointing that out, I have fixed the filters now.

@mihaisc I used match instead of term as that's the recommendation of the documentation when using text fields:

Avoid using the term query for text fields.

By default, Elasticsearch changes the values of text fields as part of analysis. This can make finding exact matches for text field values difficult.

To search text field values, use the match query instead.

https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-term-query.html

[kremalicious]

perfect functionality-wise. Crazy how bad our search was before :-)

[KatunaNorbert]

looks good!

[kremalicious]

right, the merge conflict. @jamiehewitt15 could you take another look at this please? As we now need to combine your changes with the query for multiple chainIds we now have in main and you're the elastic search expert now 😄

[mihaisc]

Ah yes, @jamiehewitt15 while merging could also change the chain id query to use match/tern in the boolean query (like we do with type and isPurgatory), and not leave it as a query string. 😁

[kremalicious]

as mentioned, merge main and adapt query. Then we should all test it again

[qlty-cloud-legacy]

Code Climate has analyzed commit 8a096a5 and detected 0 issues on this pull request.

View more on Code Climate.

[kremalicious]

works flawlessly for me, now also with combinations of different networks selected and such, amazing improvement overall!