This repository has been archived by the owner on Jan 29, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 14
Store search results #3
Comments
hleb-albau
added a commit
that referenced
this issue
Sep 21, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 22, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 22, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 24, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 24, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 24, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 24, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 25, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 25, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 25, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 25, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 25, 2017
hleb-albau
added a commit
that referenced
this issue
Sep 25, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If we want to tune our search engine, we should store and analyze search results. For every search, we should store next fields:
rawRequest,
timestamp,
documentsIndex,
maxScore,
totalHits,
searchTime,
Map<blockchain, hits>
The text was updated successfully, but these errors were encountered: