search for: xiangqianzsh

Displaying 9 results from an estimated 9 matches for "xiangqianzsh".

2018 Jan 22
2
How to get the serialise score returned in Xapian::KeyMaker->operator().
...rce.html > >You may find that's faster because it'll mean sorting by doubles instead >of strings. We realise our score function using PostingSource instead of using KeyMaker, we reference your python example and source code of xapian, the simple demo is here. https://github.com/xiangqianzsh/xapian_leaning/blob/master/postingsource/ExternalWeightPostingSource.h But we found that using PostingSource is more slower than KeyMaker. I think the reason maybe: We only use one Xapian::Query of PostingSource and the upper bound of our get_weight() can not work on a single PostingSource. So so...
2018 Jun 09
1
output debug information of LOGCALL_CTOR/LOGCALL_VOID/...
On 9 Jun 2018, at 07:37, 张少华 <xiangqianzsh at 163.com> wrote: > Many functions in xapian can be traced when they are called using LOGCALL_CTOR/LOGCALL_VOID/... and I want to output the debug information. In xapian-core/HACKING in the source code there's a section on this. As well as pass --enable-log to configure, you also need...
2018 Feb 08
7
How to ensure thread-safety
Hi, I have read the concurrency webpage from the Xapian documentation: http://getting-started-with-xapian.readthedocs.io/en/latest/concepts/concurrency.html But it is still not clear to me how to ensure thread-safety when using libxapian (C++ API). Usually when doing multi-threading many threads can read the same variable concurrently without locking provided none of the threads modifies the
2018 Jan 24
0
How to get the serialise score returned in Xapian::KeyMaker->operator().
On Tue, Jan 23, 2018 at 12:55:31AM +0800, 张少华 wrote: > We realise our score function using PostingSource instead of using > KeyMaker, we reference your python example and source code of xapian, > the simple demo is here. > https://github.com/xiangqianzsh/xapian_leaning/blob/master/postingsource/ExternalWeightPostingSource.h I'd just put the get_weight() and get_maxweight() implementations into your ExternalWeightPostingSource class - the WeightSource class doesn't seem to serve a useful purpose and just adds virtual method call overheads (...
2018 Apr 08
0
core dumped when using MatchAll in multi-threads
...y> constructQuery() { Xapian::Query black_list("BLt1"); return std::make_shared<Xapian::Query>(Xapian::Query::OP_AND_NOT, Xapian::Query::MatchAll, black_list); } I have wrote a demo to reproduce our problems, you can click this link for the detail. https://github.com/xiangqianzsh/xapian_leaning/tree/master/matchall_coredump How we solve this problems?
2017 Dec 15
5
How to get the serialise score returned in Xapian::KeyMaker->operator().
HI, all, I am a user of Xapian, and now I have a problem in using it. After using boolean terms to get some candidates of documents (still too much), we want sorted them by self-defined function which is used in Xapian::KeyMaker->operator(). But how can I get the serialise score in Xapian::MSetIterator object. c++ code likes this: class SortKeyMaker : public Xapian::KeyMaker { std::string
2018 Jan 11
0
use xapian.Query.OP_VALUE_RANGE or use xapian.MatchDecider?
HI, We have an index database of products, about 20 million. We had constructed the title and description of products into posting list, and also stored some values of properties into slot, such as the price, comment count, production date, click number of the products. Now we want select some products which satisties specific condition, such as contain the term of "shirt" and
2018 Jan 15
0
How to get the serialise score returned in Xapian::KeyMaker->operator().
Thanks for you reply. In our case, we want to get a weight using the user' properties(age, gender, price preference) and products' properties(price, comment count, purchased amount among different gender or range of age). So our weight function is complex, no matter we use KeyMaker or PostingSource, six to eight values in slot will be used. But we find that using doc.get_value(slot)
2018 Jun 09
0
output debug information of LOGCALL_CTOR/LOGCALL_VOID/...
HI, Many functions in xapian can be traced when they are called using LOGCALL_CTOR/LOGCALL_VOID/... and I want to output the debug information. So, I first install xapian and enable log, using commands as follow ``` cd xapian-core-1.4.5 # xapian source code downloaded ./configure --enable-log=yes --enable-assertions=yes make sudo make install ``` But there isn't any debug information when I