-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial text search RFC #12
base: main
Are you sure you want to change the base?
Initial text search RFC #12
Conversation
ccf93df
to
ed543e3
Compare
|
||
In the context of this RFC. | ||
|
||
| Term | Meaning | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add the definition of "stop words"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stop words are used in the search lexicon to indicate words that are ignored for text matching purposes. For our purposes they are effectively "not present". In other words, the text that's actually indexed and queried against is the text that had the stop words removed.
@allenss-amazon, If we are thinking of it as a design, is this also the right place to set the goals for: memory-usage? performance? |
No this isn't the design. this is the user-facing API. Separately, I'm working on a set of design docs which I hope to publish soon, possibly as soon as tomorrow, but hopefully by end of week. There is a proposed set of data structures and algorithms. They directly address expected memory consumption as well as big O complexity of the various update and query components. |
No description provided.