Displaying 20 results from an estimated 1000 matches similar to: "Term prefixes (was: Xapian Feedback)"
2011 Jul 27
3
Searching using prefixes
Hi guys
I'm trying to figure out how I can use probabilistic searching on a
given field within a document; I've written to the list about this
before, but haven't quite figured out what's required and, following a
little research, I think I understand what I need to do but I'd like a
clarification on this.
o We have a database of a number of documents, with fields: title,
2006 May 26
1
Unicode troubles
Hi,
I've tried to follow all helpful tips I've found in the mailing-list
and I've applied these two utf-8 patches;
http://article.gmane.org/gmane.comp.search.xapian.general/2324
http://article.gmane.org/gmane.comp.search.xapian.general/1927
Now the QueryParser works as I wants it to do, and creates the terms
correctly. But sadly I can't find any documents. If I do this;
$ quest
2013 Sep 02
2
having trouble with prefixes
I've got a small test database setup with one record.
$ delve -r 1 -V /tmp/1/
Values for record #1: 0:DD4F2162FFFF0E43741A4A1C2B8EC0E7 1:./Text_page_scan_2.jpg 2:jpg 3:.jpg
Term List for record #1: E:.jpg P:./Text_page_scan_2.jpg Q:DD4F2162FFFF0E43741A4A1C2B8EC0E7 T:jpg
The terms were added with lines like this:
doc.add_term(string("P:") + path);
Problem is, I can't seem to
2006 Mar 07
2
FLAG_BOOLEAN_ANY_CASE does not work
I have found that lower cased boolean operators such as "and" or "or"
does not work. Of course I never forget setting FLAG_BOOLEAN_ANY_CASE flag.
QP seems to treat them as terms.
Just look at the following tests regardless of search results!
$ python search.py -v woman AND man
Performing query 'Xapian::Query((woman:(pos=1) AND man:(pos=2)))'
0 results
2006 Oct 30
1
QueryParser and prefixes
Hi all,
My app uses prefixes for user-defined labels and directory names.
Since these are
case-sensitive, I chose XLABEL and XDIR respectively. Labels and directories
may start with an upper-case, so a ":" is always inserted between the
prefix and the
term itself. These prefixes are mapped with add_boolean_prefix to
"dir" and "label".
Let's imagine I index a
2015 Dec 28
3
synonym expansion for boolean prefixes.
I have an application for synonyms for tags in in notmuch, which means
synonym expansion for a particular boolean prefix. I have a vague memory
of Olly telling me this doesn't work, but I'm not sure about the
details.
My higher level goal is to support a kind of indirection with tags,
where query tag:foo can really generate tag:bar or tag:fub, depending on
some kind of configuration.
2005 Mar 31
1
omindex and scriptindex question
Hi,
I was researching indexing of text in omindex and scriptindex.
While indexing text with omindex.cc possition of terms is saved with gap.
This is not happening with scriptindex.cc
While this is happening ?
Another question is why in omindex.cc the term possition starts with 0 while
in scriptindex it starts from 1 ?
Code snippet from omindex.cc
// Add postings for terms to the document
2007 Dec 13
1
Omega datevalue search fails during scriptindex flush
Hi,
I'm experiencing weird behaviour in Xapian/Omega.
Here's my situation:
* I'm indexing data through scriptindex, the output is as follows:
*****************
Replace: 6706476
Replace: 6706477
Replace: 6706478
*****************
Since there is no output after entering several enters, I assume scriptindex is indexing data.
* The search I perform on omega is as follows:
2005 Nov 24
1
Case sensitive search
Hi all,
I´ve been developing a search application using Xapian and Omega. When our visitors search on specific keywords it´s noticable that Omega is case sensitive. It will find results on keyword `Asus´ and it will NOT find results on keyword ´asus´.
I´ve been looking through the documentation to find a CGI param to turn this
2016 Jan 05
0
synonym expansion for boolean prefixes.
On Sun, Dec 27, 2015 at 11:24:36PM -0400, David Bremner wrote:
> I have an application for synonyms for tags in in notmuch, which means
> synonym expansion for a particular boolean prefix. I have a vague memory
> of Olly telling me this doesn't work, but I'm not sure about the
> details.
Yes, synonym expansion isn't done for boolean terms (only "probabilistic
2011 Apr 17
3
Report for http://trac.xapian.org/wiki/SupportedPlatforms
Hello :-)
There was probably no good reason to do this build but the Debian 6.0
Squeeze repo version was 1.2.3, we needed 1.2.4 and I didn't think of using
the package from unstable.
Arch: x86_64
Platform: Linux 2.6 Debian 6.0 (Squeeze)
Compiler: gcc version 4.4.5 (Debian 4.4.5-8)
Version: 1.2.4
Status: no known problems
Source: http://oligarchy.co.uk/xapian/1.2.4/xapian-core-1.2.4.tar.gz
2015 Jul 26
1
Get term from document by position
mple (see attachment).
>
> Attachments get stripped out by the mailing list, so I?ve made a private gist of the two files here: <https://gist.github.com/jaylett/ce8455b37e2b84422346>.
>
> Actually, when I run it I get 0 matches, which would explain why you?re just getting the start of the document. However if I adjust things (match the stemming strategy for TermGenerator to
2011 Dec 05
1
pbs with stdin and scriptindex
Hi,
I am trying to use datas written in the stdin to run scriptindex, (I am
working with Windows and not Unix). And Scriptindex does not work, the
database is created but the datas are not indexed.
Thanks by advance
Stephane
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
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
2018 Jul 19
1
choosing between probabilistic and boolean prefixes for terms
Hi all,
public-inbox allows searching for git blob names (e.g. "badc0ffee")
in patches. Initially, I chose to use add_prefix for probabilistic
terms, since I assumed it could be a superset of what boolean
searching offered. Unfortunately, it doesn't seem to be the case
because stemming is interfering.
So switching to boolean filtering seems to work; and it is
fine for mechanical
2008 May 05
2
locate and omega: how to index file names?
hallo,
I'm indexing a filesystem using omindex, and users can query the
database via omega: everything works fine
now I'd like to add an option like "search files by name" and I'm
wondering how to do this
can omega search files by name directly? how should I build the query?
could I use scriptindex to index, eg., the locate database? how?
should I index file names
2018 Feb 24
0
MediaWiki to Omega
I use Omega to index and search an archive of magazine and ebook pdfs
etc. I also have a Wiki (in MediaWiki) that I wanted to include in that
index too.
If it's any use to anybody, I've adapted dbi2omega to export the pages
from MediaWiki and shared it on GitHub - search for mediawiki2omega.
It doesn't do anything very clever, but it might save someone time
figuring out the
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
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