Displaying 20 results from an estimated 4000 matches similar to: "NEAR non-leaf subqueries"
2017 Jan 04
2
NEAR non-leaf subqueries
Olly Betts writes:
> On Thu, Dec 29, 2016 at 07:21:41PM +0100, Jean-Francois Dockes wrote:
> > Xapian 1.2 supports a query like:
> >
> > (A OR B) NEAR (C OR D)
> >
> > and distributes the factors to create something like:
> >
> > (A NEAR 2 C) OR (B NEAR 2 C) OR (B NEAR 2 C) OR (A NEAR 2 C)
> >
> > Xapian 1.4 rejects such
2017 Jan 20
2
NEAR non-leaf subqueries
Olly Betts writes:
> On Thu, Jan 12, 2017 at 07:53:21PM +0100, Jean-Francois Dockes wrote:
>
> > Recoll also supports multi-word synonyms which could potentially
> > generate PHRASE subqueries inside NEAR queries, but this
> > understandably already did not work with 1.2, so the multi-word
> > expansions are only used when proximity is not involved (by the way,
2017 Jan 04
0
NEAR non-leaf subqueries
On Thu, Dec 29, 2016 at 07:21:41PM +0100, Jean-Francois Dockes wrote:
> Xapian 1.2 supports a query like:
>
> (A OR B) NEAR (C OR D)
>
> and distributes the factors to create something like:
>
> (A NEAR 2 C) OR (B NEAR 2 C) OR (B NEAR 2 C) OR (A NEAR 2 C)
>
> Xapian 1.4 rejects such a query with the error message.
>
> OP_NEAR and OP_PHRASE only
2017 Jan 12
2
NEAR non-leaf subqueries
Olly Betts writes:
> On Wed, Jan 04, 2017 at 07:29:58AM +0100, Jean-Francois Dockes wrote:
> > Olly Betts writes:
> > > The ticket has a patch which attempts to handle the OR case (which seems
> > > to be the part you actually care about) but this suffers from issues with
> > > object lifetimes which get a bit involved in the details. Since there
>
2017 Jan 20
0
NEAR non-leaf subqueries
On Fri, Jan 20, 2017 at 03:35:13PM +0100, Jean-Francois Dockes wrote:
> Olly Betts writes:
> > On Thu, Jan 12, 2017 at 07:53:21PM +0100, Jean-Francois Dockes wrote:
> >
> > > Recoll also supports multi-word synonyms which could potentially
> > > generate PHRASE subqueries inside NEAR queries, but this
> > > understandably already did not work with
2011 May 27
1
Does OP_NEAR works with stemming?
Hi All,
I used the OP_NEAR operator for queryparser, and when I searched for "apple store" from my own collection, the query is parsed as "Zappl:(pos=1) NEAR 11 Zstore:(pos=2)" but retrieved nothing. However, if I type in "Apple Store", the query is parsed as Xapian::Query((apple:(pos=1) NEAR 11 store:(pos=2))) and some results are showed. I'm not sure whether
2006 Nov 15
1
Composition of NEAR and OR
The following piece of code triggers an 'unimplemented' exception with the
message:
"Can't use NEAR/PHRASE with a subexpression containing NEAR or PHRASE"
Xapian::Query or1(Xapian::Query::OP_OR,
Xapian::Query("one"),
Xapian::Query("two"));
Xapian::Query or2(Xapian::Query::OP_OR,
Xapian::Query("three"),
2017 Jan 20
0
NEAR non-leaf subqueries
On Thu, Jan 12, 2017 at 07:53:21PM +0100, Jean-Francois Dockes wrote:
> Olly Betts writes:
> > On Wed, Jan 04, 2017 at 07:29:58AM +0100, Jean-Francois Dockes wrote:
> > > I'd rather go back to 1.2 than used a patched 1.4 by the way.
> >
> > Once we have a working patch, it should be mergable into 1.4.x (I can't
> > see why any ABI changes would be
2018 Sep 30
1
xapian parser bug?
On Sun, Sep 30, 2018 at 09:05:25AM -0300, David Bremner wrote:
> if (str.find (' ') != std::string::npos)
> query_str = '"' + str + '"';
> else
> query_str = str;
>
> return parser.parse_query (query_str, NOTMUCH_QUERY_PARSER_FLAGS, term_prefix);
I wouldn't recommend trying to generate strings to feed to
2017 Jan 12
0
NEAR non-leaf subqueries
On Wed, Jan 04, 2017 at 07:29:58AM +0100, Jean-Francois Dockes wrote:
> Olly Betts writes:
> > The ticket has a patch which attempts to handle the OR case (which seems
> > to be the part you actually care about) but this suffers from issues with
> > object lifetimes which get a bit involved in the details. Since there
> > wasn't a working patch when we got to making
2011 Dec 14
1
How to enable stemming with default_op set to OP_NEAR
Hi All,
I know that from version 1.2.6, if default_op is OP_NEAR or OP_PHRASE then stemming of the terms is disabled, since positional information isn't indexed for stemmed terms by default. However, I would like to try using OP_NEAR as default_op with stemming because I think the near operator is somehow different from exact phrase. Then I wanna see how the search results looks with this
2011 Dec 07
2
How to choose the proximity between search words
Hi,
I'd like to know how we can choose the distance between two words that we search
in a text. I know there is an "op_near" operator but I don't know how I can
specified that the number of words between the two specified words should not
exceed 10 or 20 or x words.
I'm really sorry for my terrible English, I hope I'm understandable!
2011 Jul 14
1
'phrase' default-op mixed with hyphenated words
Hi all,
I've come across an issue caused when I try to set the query parser's
default op to OP_PHRASE: Xapian raises an Unimplemented Error if the
query contains hyphenated words or other terms that implicitly
generate a phrase.
This can be shown with the following Python extract:
>>> from xapian import *
>>> qp = QueryParser()
>>>
2011 Sep 04
5
Ranking and term proximity
Hi,
I was reading an article recently about how google ranks results
(among many other things of course) based on the proximity of the
search terms in the source documents. In addition, the position of
the search terms in the search query string itself is also taken into
consideration when determining how important each term is.
Does Xapian do something similar - at least for the first part?
2006 Dec 06
1
Bug and patch for +terms with wildcards
In current Xapian SVN HEAD, there is a bug in the query parser concerned
with the handling of wildcard terms with a "+" prefix. Specifically,
a query such as "+foo* bar" will be parsed by the query parser into
Xapian::Query("bar") if there are no terms in the database which start
"foo". Instead, since the "+" term cannot be matched, I believe
2016 Apr 12
2
Xapian 1.3.5 snapshot performance and index size
Olly Betts writes:
> On Mon, Apr 11, 2016 at 09:54:36AM +0200, Jean-Francois Dockes wrote:
> > The question which remains for me is if I should run xapian-compact
> > after an initial indexing operation. I guess that this depends on the
> > amount of expected updates and that there is no easy answer ?
>
> I think it's not obvious whether it's a good plan
2009 Dec 07
1
Autocomplete for phrases
Hi all.
We are trying to use Xapian to index the titles of around ten million
documents (music catalogue) and then do auto-complete style search on
this index. After poking around we can't quite get the combination of
QueryParser flags and search query that will give back the results we
want. The closest we have can take a very long time (because it is
searching for, and building a list of,
2011 Aug 10
1
subqueries in sqlQuery function (package RODBC)
Hi R users.
sorry for missing example and if question is to general but I am wondering
if it is possible to execute subqueries in function sqlQuery (package RODBC)
with opened connection with Excel or SQL server 2000. I couldn't find any
example of this.
And if it is possible what should be a correct syntax for this query:
SELECT ct,COUNT(*) as n
FROM (SELECT COUNT(*) AS ct FROM children
2016 Apr 11
2
Xapian 1.3.5 snapshot performance and index size
Olly Betts writes:
> On Sun, Apr 10, 2016 at 04:47:01PM +0200, Jean-Francois Dockes wrote:
> > Some might notice the 50% index size increase. Excessive index size is
> > already one relatively rare, but recurring complaint. Except if I did
> > something wrong: I'm actually quite surprised by it.
>
> Did you try compacting the resulting databases?
>
>
2007 Jun 19
2
Deleted documents not deleted
I seem to be seeing cases where I call db.delete_document(somedocid) with
no error, then flush() and delete the database object, but the document is
still there after process exit. The write lock is normally deleted, so it
appears that the database close finished normally.
If I then then call delete_document(somedocid) from another
command/process, this time it goes away.
I've been seeing