similar to: Make Xapian accept all characters

Ok, but suppose I have a complex query, something like "(a OR b) AND NOT c OR ##". Do I have to parse the query by myself? > Date: Mon, 4 May 2015 03:03:24 +0100 > From: olly at survex.com > To: lautaromedrano at hotmail.com > CC: xapian-discuss at lists.xapian.org > Subject: Re: [Xapian-discuss] Make Xapian accept all characters > > On Sun, May 03, 2015 at

On Sun, May 03, 2015 at 07:34:32PM +0000, Lautaro M wrote: > I'm using Xapian at work (PHP bindings) and I have to make it accept > '##' as a term to index. We have a layer on top of xapian, but as far > as I can tell, Xapian's QueryParser is removing them from the query. > So, if I search for just '##' I get an empty query, after Xapian > parsed it. I've

Hi, I've been using Xapian for a while. But there is a scene I don't know whether supported already. Suppose: 1. Raw query: how to make pizza 2. Parsed query: how AND to AND make AND pizza 3. Documents: d1: how to make pizza at home d2: 3 ways to make pizza d3: make pizza in 4 easy steps Question: 1. During searching process, how to retrieve d2, d3 (although they don't

I tried to register yesterday, twice with 2 email addresses. The website said it sent me mail, I never got a mail. Someone else, please confirm this is broken. A bug I'd like to file is that I'd like an option to search *word. Currently you can only search word*. The example where I would find this useful is searching for urls and email addresses. For example, I want to find emals from

I tried to register yesterday, twice with 2 email addresses. The website said it sent me mail, I never got a mail. Someone else, please confirm this is broken. A bug I'd like to file is that I'd like an option to search *word. Currently you can only search word*. The example where I would find this useful is searching for urls and email addresses. For example, I want to find emals from

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I am working with version 1.2.7 and want to use stemming and synonyms. I use the perl-bindings and get some problems. First of all: the perl-bindings dont allow the QueryParser a third argument when calling parse_query! So i cannot set a default prefix (which perhaps is the solution to my problem, but later more) i have a simple testcase: 3 documents, every document only has one word:

I can't quite connect the dots on this, perhaps someone can help. I'm simply trying to create an in-memory database comprising a single document, so that I can run a load of queries against it and see if any of them match the new document (this is to enable users to have 'subscriptions' to saved searches and be alerted every time a new item is published that matches their

On Thu, 30 Mar 2023 at 04:58, Olly Betts <olly at survex.com> wrote: > > Another option is to import the things you want with `use` and then > you can just use `XapianWritableDatabase` without to prefix it with > `\`. To do that add this after your `namespace literallyanynamespace;` > line: > > use \XapianWritableDatabase; Thank you very much. This then (because

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.

I'm replying to a very old thread (9 years ago) here http://grokbase.com/t/xapian/xapian-discuss/072tprmr6h/php5-query-parsing-bug So not sure if that's going to end up being more or less readable... I have this error : Fatal error: No matching function for overloaded 'new_Query' in /usr/share/php/xapian.php on line 2607 Line 2607 (and surrounding) looks like this and are in

Hi, I'm new to Xapian and wanted to know if it has a specific feature. I want to be able to check the relation between two terms on a page based on how close they are together on the page. I want to use a combination of n-gram based labeling and the "slop" feature found in Elasticsearch. Does Xapian have this/a similar feature? I haven't been able to find any programs that have

Hola, ¿cómo están? Soy estudiante de Ing. en Sistemas de Información y estoy cursando la materia Tecnologías para la Explotación de Datos. Me he decidido a usar R para hacer DM. Estoy recién comenzando con ambos. El asunto es que no he encontrado la implementación en R de uno de los algoritmos que dimos para árboles de decisión, ID3. Ya revisé varios de los paquetes para DM

Hello. There are several problems I couldn't find a solution. 1. QueryParser does not perform stemming I am working with PHP5 and use the xapian wrapper written by Daniel M?nard I build a query using parseQuery. Output of the parsed query shows that terms are not stemmed, although a stemmer is set ( see code snippet) # create a XapianDatabase object to search in $db = new

Good afternoon I would like to ask if is possible somehow give more relevance to the recent documents in search results. I dont want to sort results according to the date, I still prefer relevance, but I would like to see recent documents with better scoring. I was trying to add search query using AND_MAYBE, which should use relevance from both subqueries, but it didnt add any benefit to the

I am suffering for slow searching performance on Xapian. I am using Xapian for indexing about 150,000,000 documents. It was implemented in C++; The performance of searching was not that fast. e.g. Searching a query, which includes about 20 terms, needs 2 secs avg. For searching, I followed such steps: 1. construct a QueryParser for certain string 2. parse the query to get a Xapian::Query

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:');

Hola, ¿como están? Me encuentro haciendo un trabajo de Explotación de Información para la facultad y tengo un inconveniente a la hora de preparar los datos para poder operar con ellos. Tengo un atributo "Titulo Secundario" que cuenta con 139 valores diferentes (al final les dejo algunos de estos valores con la cantidad de ocurrencias de cada uno) y lo que quiero hacer es

Hi to all, First, I would like to say a big thank you for the work which was done on my 'wish bug' to allow mapping one field to multiple prefixes (http://www.xapian.org/cgi-bin/bugzilla/show_bug.cgi?id=93). That's great! I have upgraded to 1.0.4 and I am revisiting my code, replacing the php query parser I wrote with Xapian's one. Everything works well, but I have some