Displaying 20 results from an estimated 300 matches similar to: "How to enable stemming with default_op set to OP_NEAR"
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
2008 Sep 16
0
[PATCH] Add set_max_wildcard_expansion method to the queryparser.
---
search-xapian/XS/QueryParser.xs | 6 ++++++
search-xapian/Xapian/QueryParser.pm | 7 +++++++
xapian-core/include/xapian/queryparser.h | 3 +++
xapian-core/queryparser/queryparser.cc | 6 ++++++
xapian-core/queryparser/queryparser.lemony | 9 +++++++++
xapian-core/queryparser/queryparser_internal.h | 4 +++-
6 files changed, 34
2009 Jun 01
2
Xapian .lemony files
Hi All,
I wanted to add a small tweak to my installation of the Query Parser.
Should I be editing queryparser.lemony? I tried that and the make
didn't include my change. I applied the same change to
queryparser_internal.cc and it worked fine. Is the .lemony file
something used internally and I can ignore? Or do I need to run
something prior to make to convert the files?
Thanks,
Mike Boone.
2009 Jan 15
2
Xapian core build failure under gcc 2.95
Hi,
Under gcc 2.95 Xapian fails to build like so:
g++ -DHAVE_CONFIG_H -I. -I./common -I./include
-I/home/dsainty/not-backed-up/pkgsrc/textproc/xapian/work/.buildlink/include
-Wall -W -Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align
-Wno-long-long -Wformat-security -fno-gnu-keywords -Wundef -O2 -c
queryparser/queryparser_internal.cc
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!
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"),
2009 Dec 13
1
Combined search in multiple fields help
Hello,
I want to let user specify by drop down list to what fields his query will be searched. For example "Full-text" or "Title+Author", then user enters search query as usual (without using prefixes). But how to modify query so it cover two fields in a right way?
For a starter how I think about modifying query to limit it just to single globally selected field:
1. after
2016 Dec 29
2
NEAR non-leaf subqueries
Hi,
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 currently support leaf subqueries
Because Recoll expands the terms to their stem siblings at query time, its
NEAR queries
2010 Jan 19
1
QueryParser: aliases and OP_AND
Hello,
I'm wondering about how the QueryParser parses a query containing an "alias" when the default operator is OP_AND
(by "alias", I mean a search field mapped to multiple term prefixes).
With the following php code :
<?php
$parser=new XapianQueryParser();
$parser->set_default_op(XapianQuery::OP_AND);
$parser->add_prefix('alias', 'AUT1:');
2012 Jan 05
1
Enhance synonyms feature of the query parser (patch included)
Very few people seem to be using synonym in Xapian, I recently found some problems in the use of synonyms.
Normally, I think we should not contain any prefix info in synonym table except that 'Z'.
For example, I have the following synonyms and prefix info:
db.add_synonym("search", "find");
db.add_synonym("Zsearch", "Zfind");
2006 Apr 05
1
build error : xapian-core-0.9.4_svn6707 with UTF-8 patch
This is another error different from the previous posting.
I want to compile xapian-core-0.9.4_svn6707 with UTF-8 patch.
But I failed to compile it due to the following errors.
Environment : CentOS 4.3 x86_64
Sungsoo Kim
----------------------------------
g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I../common -I../api
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
2006 Mar 03
1
xapian-0.9.4 queryparser build errors after applying utf-8 patch
I have encountered the following build errors after applying xapian-qp-utf8-0.9.2.patch.
There is no build error before the patch.
- CentOS 4.2 64 bit version (RHEL 4.0.2 compatible)
- AMD Opteron dual processor
Can anybody tell me what I am missing?
Thanks!
Sungsoo Kim
--------------------------------------------------
[root at saturn queryparser]# make
make all-am
make[1]: Entering
2007 Oct 01
3
How to beat Google aka Xapian & Natural Language Processing.
Xapians!
If tomorrow Xapian search engine would achieved the same performance
and result in searches as Google we would not be able to beat Google,
because we would create only a copy of the searches that already
exists from Google search engine. However there is a way to beat
anyone, and there is a way to beat Google successfully as well just do
not give up. Some see it as implementing Ajax, or
2005 Feb 24
2
mutable Query objects
There's a bit of an API glitch with Query objects at present. This code
shows it off:
Xapian::Database("/path/to/db");
Xapian::Enquire enquire(db);
// make a simple query
Xapian::Query myquery(Xapian::Query::OP_NEAR, phrase, phrase + 2);
enquire.set_query(myquery);
// Now change the query - this shouldn't affect the query enquire
// will run, but it does.
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
2006 Feb 07
1
Omega
Are there any options to forming queries with Omega? For instance can
you specify a proximity search like "file near 5 manager"? If so, where
might I find this documented? I don't see it in the docs directory.
Thanks
Jim.
2011 Mar 23
1
how to change the default operator?
Hi all,
I'm sorry to bother you guys with such a rookie question. I tried to change the default boolean operator by editing the file queryparser.h like this:
void set_default_op(Query::op OP_AND);
However, after rebuilding I tested it with the query "grad school" and it still worked with the OP_OR as default, like this:
Parsed query is: Xapian::Query((Zgrad:(pos=1) OR
2010 Oct 28
1
hypens in words + NEAR + 3 terms + AND_MAYBE => crash
Probably an uncaught malformed query - the following form of search queries
causes a crash for me (core 1.2.3, Perl API, 64bit Debian Lenny, self-compiled):
x-y NEAR test NEAR test
The first term can be anything with a hyphen in it but word characters at the
beginning and end ("3--3" will do). The other 2 terms can be anything.
"test NEAR x-y NEAR test" will not cause a
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,
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