-
Notifications
You must be signed in to change notification settings - Fork 21
chore: use exact for fuzziness threshold 1 #1262
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
Draft
larsplessing
wants to merge
13
commits into
main
Choose a base branch
from
chore-use-exact-for-fuzzinessThreshold-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 7 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
6ffdf60
Update cql-functions.js
larsplessing 92b7155
Merge branch 'main' into add-search-mode-text
larsplessing fd83e45
use exact instead of fuzzy
larsplessing e6fe870
Merge branch 'main' into add-search-mode-text
larsplessing b255610
Update fuzzy.test.js
larsplessing cfcda9a
Merge branch 'add-search-mode-text' of https://github.com/cap-js/cds-…
larsplessing 7bf61ba
Merge branch 'main' into chore-use-exact-for-fuzzinessThreshold-1
larsplessing 31a3dcc
define definitions in fuzzy.cds
larsplessing 8338852
Merge branch 'chore-use-exact-for-fuzzinessThreshold-1' of https://gi…
larsplessing 70d0357
Update fuzzy.test.js
larsplessing e529657
Merge branch 'main' into chore-use-exact-for-fuzzinessThreshold-1
larsplessing 14bcfdc
Merge branch 'main' into chore-use-exact-for-fuzzinessThreshold-1
larsplessing 4df106c
Merge branch 'main' into chore-use-exact-for-fuzzinessThreshold-1
larsplessing File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,9 @@ | ||
| using {sap.capire.bookshop.BooksAnnotated as BooksAnnotated} from '../../test/bookshop/db/schema.cds'; | ||
| using {sap.capire.bookshop.BooksAnnotated as BooksAnnotated, sap.capire.bookshop.BooksAnnotatedScore1 as BooksAnnotatedScore1} from '../../test/bookshop/db/schema.cds'; | ||
|
|
||
| annotate BooksAnnotated with @cds.search: {title, descr, currency.code}; | ||
| annotate BooksAnnotated:title with @(Search.ranking: HIGH, Search.fuzzinessThreshold: 0.9); | ||
| annotate BooksAnnotated:descr with @(Search.ranking: LOW, Search.fuzzinessThreshold: 0.9); | ||
| annotate BooksAnnotated:descr with @(Search.ranking: LOW, Search.fuzzinessThreshold: 0.9); | ||
|
|
||
| annotate BooksAnnotatedScore1 with @cds.search: {title, descr, currency.code}; | ||
| annotate BooksAnnotatedScore1:title with @(Search.ranking: HIGH, Search.fuzzinessThreshold: 0.9); | ||
| annotate BooksAnnotatedScore1:descr with @(Search.ranking: LOW, Search.fuzzinessThreshold: 1); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
according to java tests, this is sufficient.
Uh oh!
There was an error while loading. Please reload this page.
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.
@johannes-vogel
For the search mode java also always wraps the search term in wildcards like:
*<term>*.But with placeholders this is not possible.
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.
Does Java use placeholders? Otherwise this opens doors for SQL injection since the search term comes from end user?!
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.
My understanding of the discussions is to always forward the
$searchstring directly into thescorefunction. If customers expect to use wildcard characters like*they should include it inside their search field or the application developer has to include it inside the request.Uh oh!
There was an error while loading. Please reload this page.
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.
@johannes-vogel They are generating prepared statements like SCORE ? IN ... and the value for ? is
*<SearchTerm>*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.
Does that mean Java deviates from the agreement that search is an arbitrary string that is used as is in score function? It looks to me at least that way...
Uh oh!
There was an error while loading. Please reload this page.
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.
@johannes-vogel with
EXACT MINIMAL SCORE 1 search mode 'text'the search term will be interpreted as a whole string. E.g. for the string 'this is a test':search term:
Uh oh!
There was an error while loading. Please reload this page.
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.
Hana colleagues wrote:
@johannes-vogel How should we proceed from here?