| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds `prefix:[true|false]` annotation support to the `fuzzy`
query operator in the YQL and JSON query languages. Fuzzy
prefix matching semantics are wired through to the matcher
implementations for both indexed and streaming search.
Example usage:
{maxEditDistance:1,prefix:true}fuzzy("foo")
Will match `foo`, `foobar`, `foxtrot`, `zookeeper` and so on.
It can be combined with the existing prefix locking feature:
{maxEditDistance:1,prefixLength:2,prefix:true}fuzzy("foo")
Which will match `foo`, `foobar`, `foxtrot` etc, but _not_
`zookeeper` since the locked prefix (`fo`) does not match.
Due to the complexities involved with extending the legacy binary
query stack representation, signalling prefix matching for the
fuzzy term is done by pragmatically adding a new, generic "prefix
matching" term-level flag. This is currently ignored for
everything except fuzzy query items.
Modernizing the query stack format to make it more extensible
(i.e. move encoding to Protobuf) is on the backlog...!
|
| |
|
|
|
|
|
|
| |
of the ObjectMapper.
Unless special options are used, use a common instance, or create via factory metod.
|
| |
|
|
|
|
|
|
|
| |
Add the missing constructs to SchemaInfo to be able to use
it in place of IndexFacts for validation, and rewrite QueryValidator
to use it. The new validation (for prefix search on indexes) is disabled
until this is verified, so this should be a no-op.
|
| |
|
| |
|
|
|
|
|
|
|
| |
vespa-engine/revert-23039-bratseth/weakand-by-default-take-2"
This reverts commit 4b3adbb89f52bb20f2f220fcf1480673cae0881d, reversing
changes made to d204179b218af2fdf4b251ede3a465ffabbf6557.
|
| |
|
|
|
|
|
|
|
| |
vespa-engine/revert-23032-bratseth/weakand-by-default"
This reverts commit 1b00635b293901abaef45aca022647c01e840b6b, reversing
changes made to 0fd0ba6d04f642095e35ff828e6d7ee334a4bdb8.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Remove most usage of org.json:json Maven artifact.
This library does not have a compatible license.
Some usage is still left as it's part of our container-search public API.
We'll need a major release to fix that.
See https://github.com/vespa-engine/vespa/issues/14762 for more details.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add IllegalInputException to signal cases where we know the exception
is caused by illegal input received from the requestor.
- Only skip logging for IllegalInputException instead of the superclass
IllegalArgumentException as that is also used to signal illegal
arguments to methods due to bugs which are otherwise hard to debug.
- Throw IllegalInputException rather than IllegalArgumentException
where appropriate.
- Deprecated QueryException as it was only used to be able to separate
between query string and query parameter exceptions, and not doing
that consistently, and is in a package we don't want more use of.
- Clean up some cases where the wrong exception was thrown.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* targetHits is now the preferred annotation replacing
targetNumHits (for wand,weakand,nearestneighbor), the
old name still works as an alias
* note: targetNumHits is still produced when serializing to YQL
* debugging/trace output will print the "targetHits" form
* add nearestNeighborItem support to SelectParser
* implement disclose() in nearestNeighborItem
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- Serialize annotated range and weightedset with bracing
- Parse Infinity in ranges
- Better error messages in range parsing
|
| |
|
| |
|
|
|
|
|
|
|
| |
vespa-engine/revert-6557-revert-6553-revert-6512-henrhoi/object-structured-grouping"
This reverts commit 506ea9c1367748ddd4ff20203fc13211d635f5a6, reversing
changes made to 4f6b34dcf9ad904f0ddb89eb506f5920360d5344.
|
|
|
|
| |
objects, accessable from…"""
|
|
|
|
|
|
|
|
|
|
| |
- Deep copy the grouping structure on query copy.
It is mutable but we have neglected doing this right until now.
- Fix a bug in the previous commit where the last constructed Query.Model was shared between all instances.
- Fix a bug in the previous commit where the query string instead of the query tree was reset when a new select
expression is set.
- Don't use deprecated method.
- Clean up Javadoc and formatting.
|
|
|
|
| |
accessable from…""
|
|
|
|
| |
from…"
|
|
|
|
| |
query.getSelect().getGrouping()
|
| |
|
| |
|
|
|
|
| |
grouping-parameter and setting the query's groupingrequest when parameter is present
|
|
|
|
| |
need some cleaning and removal of unuses code
|
|
on a SelectParser which will parse the SELECT parameters to a QueryTree. Also added a new type for queryies 'SELECT', and will now use the SelectParser when getting the QueryTree. Started on testing the same testcases as in YQLParser, looks promising.
|