similar to: xapian.InvalidArgumentError: Term too long (> 245)?

I upgraded to latest xapian version and I have started getting xapian.InvalidArgumentError: Term too long (> 245): XTEXT... This issue was not there in 1.0.16 but it is in the latest version. Any solutions. thanks

Hi all, I've come across a very strange bug with Xapian 1.0.9.0 and the Turkish query parser when trying to index a string (as posting) that looks like this: "...bir araya getiren CD'leri son teknolojiyle piyasaya...". The actual offending bit of the string is: 'leri It throws the message I have shown below. The real annoyance is that I can't seem to catch it because it

xapian 1.0.16 threw xapian.InvalidArgumentError: Term too long (> 245) but in our testing xapian 1.26 is not throwing this exception. Did it change? Ashish

James, I would like to propose to change the following code while indexing a term that is larger than 245 characters and then crashing and aborting the entire index, we could rather truncate the term to 245 characters and continue with indexing. if (tname.size() > MAX_SAFE_TERM_LENGTH) throw Xapian::InvalidArgumentError("Term too long (> " STRINGIZE(MAX_SAFE_TERM_LENGTH) "):

I am using xapian-bindings-1.0.16.tar.gz ./configure --prefix=$HOME PYTHON=/usr/bin/python PYTHON_LIB=/Library/Python/2.6/site-packages --with-python --without-ruby --without-php --without-tcl and I get configure: error: Can't find xapian-config, although the xapian-core runtime library seems to be installed. If you've installed xapian-core from a package, you probably need to install

Hi all, We've struck a problem when using remote queries and hoping someone can offer some guidance. I haven't managed to get a C++ reproduction in the test suite, but I have got a demo that fails using Python: import xapian db = xapian.remote_open('localhost', 8100) qp = xapian.QueryParser() qp.set_database(db) query = qp.parse_query('test') enq =

On Mon, Jul 11, 2016 at 02:02:56PM -0700, Kevin Duraj wrote: > You are saying that when I search for "delve Xapian 1.4" on Google, a > company worth of 491 Billion of Dollars and you saying that their top > of the search result has nothing to do with Xapian. > > https://www.google.com/search?q=xapian+delve&ie=utf-8&oe=utf-8#q=delve+xapian+1.4 Well, I'm not

Sorry if this is a repost .. I have edited my query a little bit and my previous post was too long and so was waiting approval(I cancelled it) Ok. Another question.. I have installed the Search ::Xapian on my local machine. Now I'm trying to install it on a machine where i dont have root access. So while running configure of the Xapian library I gave the -prefix option and everything installed

I've just found some items in my Xapian database which aren't being indexed, when the terms are quite long. Example term: Frotherham_doncaster_and_south_humber_mental_health_nhs_foundation_trust It represents that the Freedom of Information request was made to a particular public body. It results in pages like this not correctly showing results:

I'm preparing a pull request for the master branch and noticed that `make check` on a clone of the xapian repository fails badly. I haven't merged my changes and built from e24cc6018de0. Is is just me or is there something broken in the master branch? Running test './apitest' under valgrind Running tests with backend "none"... Running test: defaultctor1...

I wrote: > I think it's a bug. Or at least QueryParser uses a rather delicate rule > for when to add a ":" between the prefix and the term, which scriptindex > doesn't implement. The rule is undocumented (except in the code) so > it's arguable who is correct. I've been looking at this some more. We need some way to distinguish the term prefix from the term

Hi all, I've been a Lucene user for the past year, but lately, with most of my project moving to Python, I really love Xapian's clean python binding. I can't seem to see how to boost a query term using Xapian's query syntax. In Lucene, there is "hello^4 world^.2" to boost "hello" and suppress "world". However, digging through Xapian's

Hi Olly I will try to work on : http://trac.xapian.org/wiki/GSoCProjectIdeas#Project:LearningtoRank I will be taking a Machine Learning class the next semester and I hope that this project will help me supplement my learning in Machine Learning and also gain a bit of knowledge in IR. If you can give me ideas on how to get around with the code for LTR project, it will be awesome. I can look at

Hi Maybe I can start off with Hanxiao's branch but I can see there are two repos. https://github.com/v-hasu/xapian/tree/gsoc2014-evaluation https://github.com/v-hasu/xapian/tree/gsoc2014 which one should I pick? I have already successfully built xapian from the git repository ( https://github.com/xapian/xapian) Since I am new to ML (well I dont know anything about it?), should I read the

Now imagine my situation and probably others too, when we are working with big data. I select 1 billion of YouTube videos, and then I index it with Xapian. Now a kid uploads Pokemon video and for some reason, the kid keeps pressing a single key on the keyboard until the term become 500 characters long (e.g., EEEEEEE). Xapian index is running and after it has indexed 500 million documents,

Hi All I am Manu and recently came across the Xapian project. I will like to contribute to Xapian that gets me introduced to Information Retrieval. I have a basic knowledge of C++. Can you suggest me and help me choose a task that can be good for beginners. Thanks a lot Best Regards Manu Gupta

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

Hi~ Manu I was glad to see you were interested in Xapian, especially the learning to rank project. There are two branch in my repo. The one named gsoc2014 is followed the thought of Parth's work in which we not assign the test set for each ranking and in another one gsoc2014-evaluation we assign the training set and test set explicitly so that we can get the evaluation score of each ranking

I'd suggest that a good thing to look at would be functional tests of the metrics and algorithms in Hanxiao Sun's work from this summer. You'll generally need to go either to the original paper, or find an alternative implementation, to build up a series of tests that demonstrate that the implementation is doing what it is supposed to. Xapian-core contains a test framework which it

On 5/12/2014 12:04 AM, "James Aylett" <james-xapian at tartarus.org> wrote: > As Parth mentioned, you need to remove xapian-bindings/.nobootstrap in order to have that built from git. ITYM xapian-letor/.nobootstrap here. Cheers, Olly -------------- next part -------------- An HTML attachment was scrubbed... URL: