-
Notifications
You must be signed in to change notification settings - Fork 252
Rf/zenko 250 portmdsearchtest #1218
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
Conversation
| const userMetadata = { food: 'pizza' }; | ||
| const updatedUserMetadata = { food: 'cake' }; | ||
|
|
||
| runIfMongo('Basic search', () => { |
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.
this is cool 👍
| Key: masterKey, Metadata: userMetadata }, | ||
| err => { | ||
| // give ingestion pipeline some time | ||
| // setTimeout(() => done(err), 45000); |
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.
just curious, why were the timeouts originally used? Is this the same as the timeout applied in the npm run command ft_search?
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.
The current implementation of MD search queries the mongo MD backend, and, as such, it does not require the wait time. (@rahulreddy confirm/elaborate this statement?)
setTimeout was originally used here when MD search was using Clueso. As for how it relates to the npm command timeout: the npm timeout is set to a larger number to make sure this timeout wait does not expire the test.
| try { | ||
| ast = parser.parse(searchParams); | ||
| ast = parser.parse(searchParams, (operator, operands) => { | ||
| switch (operator) { |
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.
why not just an if/else?
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.
had more cases, but they turned out redundant. will clean up after more reviews
vrancurel
left a comment
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 you please include a MD-Search.Design.Md document explaining the design + a basic usage of the API and the command line tool, including differences with SQL.
I am up for not having to support backticks for quoting variables containing dashes because it is error prone (cf demo)
415afb0
bb06afa to
415afb0
Compare
Do it again human slave!:point_right: :runner: (Oh and the pull request has been updated, by the way.)
|
PR has been updated. Reviewers, please be cautious. |
415afb0 to
53c6fc8
Compare
|
PR has been updated. Reviewers, please be cautious. |
|
and the design ! |
|
I have split the documentation into another PR #1220 |
53c6fc8 to
70868ff
Compare
|
PR has been updated. Reviewers, please be cautious. |
70868ff to
5a6bba6
Compare
|
PR has been updated. Reviewers, please be cautious. |
5a6bba6 to
28c7a1b
Compare
|
PR has been updated. Reviewers, please be cautious. |
28c7a1b to
628724e
Compare
|
PR has been updated. Reviewers, please be cautious. |
6d67e98
628724e to
6d67e98
Compare
|
PR has been updated. Reviewers, please be cautious. |
|
Documentation: #1220