Skip to content

lucene-linguistics: added query clause profile override example #1834

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.

Sign up for GitHub

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

Merged
radu-gheorghe merged 3 commits into from
Jan 28, 2026
Merged

lucene-linguistics: added query clause profile override example #1834

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6428534
lucene-linguistics: added query clause profile override example
radu-gheorghe Jan 27, 2026
6e8f7c2
removed extra line
radu-gheorghe Jan 27, 2026
b81d7fe
fixed inconsistencies
radu-gheorghe Jan 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 25 additions & 5 deletions examples/lucene-linguistics/multiple-profiles/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,9 @@ through the <code>vespa deploy</code> step, cloning `examples/lucene-linguistics
vespa feed ext/*.json
```

## Run test queries
## Run queries

### Basic example

This will confirm that ASCII folding is working on the `title` field, because it will match `åao` with `åäö`:
```bash
Expand All @@ -46,7 +48,21 @@ curl -s -X POST -d '{
"trace.level":2}' -H "Content-Type: application/json" 'http://localhost:8080/search/' | jq .
```

You can also force a different profile for the query via `model.type.profile`. This will match "dubious" with "special" (our test synonym expansion):
### Different profiles for query and index

For the `description` field, [the schema defines a different profile for search time](app/schemas/doc.sd) which does synonym expansion. So it will match "dubious" from the query string with "special" in the index:

```bash
curl -s -X POST -d '{
"yql":"select * from sources * where description contains \"dubious\"",
"presentation.summary": "debug-text-tokens",
"model.locale": "en",
"trace.level":2}' -H "Content-Type: application/json" 'http://localhost:8080/search/' | jq .
```

### Force a different profile for the query

`model.type.profile` defines the profile to use for parsing the query string. This will match "dubious" with "special" (our test synonym expansion) even for the `title` field (which is bound to the `lowerFolding` profile which doesn't do synonym expansion):

```bash
curl -s -X POST -d '{
Expand All @@ -57,12 +73,16 @@ curl -s -X POST -d '{
"trace.level":2}' -H "Content-Type: application/json" 'http://localhost:8080/search/' | jq .
```

For the `description` field, we already use a different profile for search time which already does synonym expansion (as defined in [the schema](app/schemas/doc.sd)). So it will match "dubious" with "special" out of the box:
### Force a different profile for a specific query clause

This works with `userInput()` and the `grammar.profile` annotation:

```bash
curl -s -X POST -d '{
"yql":"select * from sources * where description contains \"dubious\"",
"yql":"select * from sources * where where {defaultIndex:'title', grammar.profile: 'lowerFoldingStemmingSynonyms', grammar:'linguistics'}userInput('dubious')",
"presentation.summary": "debug-text-tokens",
"model.locale": "en",
"trace.level":2}' -H "Content-Type: application/json" 'http://localhost:8080/search/' | jq .
```
```

**NOTE**: The `grammar: 'linguistics'` annotation isn't required in this case, but makes sure that no additional parsing (besides the defined profile) is done. This is useful, for example, with collapsing synonyms (e.g., `wi fi => wifi`). Otherwise, the query becomes `["wi", "fi"]` along the way.