Displaying 20 results from an estimated 1000 matches similar to: "NumberValueRangeProcessor documentation"
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
2015 Sep 09
2
custom ValueRangeProcessor in Perl?
Hello, I'm using the XS Perl bindings packaged with Debian stable
and am interested in implementing my a custom ValueRangeProcessor
(using DateTimeX::Easy for human-friendly date parsing)
Unfortunately, I'm not sure if it's possible with the
add_valuerangeprocessor API via Perl.
Reading the XS/*ValueRangeProcessor.xs source files, I'm seeing
"process_value_range"
2004 Sep 29
1
Tinderbox
We've lost tinderbox (last build 25th), which is presumably why the
following wasn't caught:
----------------------------------------------------------------------
/s1/james/projects/xapian/xapian/xapian-core/extra/queryparser.yy: In
function
`int yylex()':
/s1/james/projects/xapian/xapian/xapian-core/extra/queryparser.yy:443:
`class
std::basic_string<char,
2007 Jun 23
1
Test failures
Tinderbox is showing failures in Search::Xapian on atreus with g++ 4.1
(which looks like tests out of date at a *very* cursory examination,
and in any case everyone should know about); I'm also getting
different test failures on the same system -- valgrind (I assume) is
finding potential memory leaks for every test against the remotetcp
backend.
(Incidentally, I've just installed
2012 Aug 23
0
[LLVMdev] % in tablegen
Hi,
I am facing an issue with tablegen.
tablegen complains about not finding a register when % is used in the
instruction string.
error: unable to find register for '' (which matches register prefix)
I have copied an example (not the original). Note that i added %prefix_
before $sp register. Tablegen seems to interpret % as placeholder for
inserting register. Is there any way to make
2004 Oct 22
1
Re: [Xapian-commits] Changes in xapian/xapian-bindings/ xapian/xapian-bindings/python/docs/
On Thu, Oct 21, 2004 at 05:45:42PM +0100, Olly Betts wrote:
> Log message:
> python/docs/bindings.html: Remove documentation explicitly saying
> how we wrap Xapian::QueryParser and Xapian::Stem since we wrap them
> exactly as we wrap everything else we don't mention! Also mention
> simpleexpand example.
The point of this comment was to highlight that they exist within the
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
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
2009 Jan 02
2
Deprecated Realtime application, what's to be gained ???
Hi,
After seeing in "pbx/ael/ael-test/ael-test5/extensions.ael" some
interesting use case of RealTime
to store extension data (forwardto, dnd, ...) i started to play with it.
To my surprise the two applications RealTime() / RealtimeUpdate() have
been deprecated in favor
of the REALTIME() function. While it's not a big deal for the write part
since it's only a matter a
shifting
2013 Jul 21
1
dovecot fts solr plugin
Hello list,
* apache-solr-3.6.2
* dovecot-2.1.7
I configured fts_solr for dovecot, but I have two issues
When doing a search request within telnet 127.0.0.1 143 it connects to solr.
Jul 21, 2013 4:38:15 PM org.apache.solr.core.SolrCore execute
INFO: [] webapp=/solr path=/select
params={rows=1&q=box:10361d30f8c4ea51ad7c00002ecaff3b+user:"
tom at
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
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
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
2015 Mar 05
0
Dovecot Full Text Search results in SolrException: undefined field text [SERIOUS]
In your schema.XML check you have defined:
<field name="text" type="text_general" indexed="true" stored="false"
multiValued="true"/>
On 05/03/2015 7:11 PM, "Kevin Laurie" <superinterstellar at gmail.com> wrote:
> Hello,
> My dovecot constantly runs into this error.
> I want to fix this one last time, I am tired of
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 Oct 31
3
No search results using Searcher
I just started using Ferret and I successfully indexed some documents. I
can search this index using the following code:
index = Index::Index.new(:path => path)
index.search_each("something") do |doc, score|
print "##{doc} #{index[doc][''url'']} - #{score}"
print "\n"
end
However, when I try to use Search::Searcher and QueryParser
2010 Nov 02
1
How to make QueryParser select entire word like "H.O.T"
Hi,
I'm using xapian to build my search engine, but met with a problem.
The code snippet is like:
----------------------Code begin-------------------------------------------------------------
Xapian::QueryParser qp;
qp.add_prefix("Singer", "S");
Xapian::Query query = qp.parse_query("Singer:s.h.e",
2006 Apr 11
2
setting the default operator on a QueryParser
Hi all,
Thanks to the authors for the amazing work on Ferret! I have a question
about setting up the standard operators on a QueryParser. I would like
my parser to default to AND queries rather than the default OR.
In Java I would simply do:
QueryParser parser = new QueryParser("contents", new
StandardAnalyzer());
parser.setDefaultOperator(QueryParser.Operator.AND);
But I