search for: with_positions

Displaying 5 results from an estimated 5 matches for "with_positions".

Did you mean: with_positional
2019 Nov 21
5
Extending the nbdkit python plugin
We have an nbdkit plugin that lets you write NBD servers in Python. An example of an existing Python plugin is here: https://github.com/libguestfs/nbdkit/blob/master/plugins/python/example.py#L1 This morning I tried to modify the plugin to use the newer nbdkit API (version 2). One of the things that would change would be passing flags parameters to some functions, eg: def pwrite (h, buf,
2007 Nov 14
1
Problem indexing text with spelling enabled in Perl
...88, word=@0xbff97724, freqinc=1) at ./include/xapian/ base.h:154 #1 0xb7becf47 in Xapian::TermGenerator::Internal::index_text (this=0xa553970, itor= {p = 0xab2d69f " North Face Windwall 1 Jacket boys", end = 0xab2d6c1 "", seqlen = 1}, weight=3, prefix=@0xbff977ac, with_positions=true) at queryparser/termgenerator_internal.cc:207 #2 0xb7bebf0c in Xapian::TermGenerator::index_text (this=0x9b12d68, itor=@0xbff9779c, weight=3, prefix=@0xbff977ac) at queryparser/ termgenerator.cc:90 #3 0xb7c6b6d6 in XS_Search__Xapian__TermGenerator_index_text () from /usr/local/lib/...
2007 Dec 17
1
Crashes with spelling enabled and perl.
...in Xapian::WritableDatabase::add_spelling (this=0x9d77de0, word=@0xbf846fa0, freqinc=1) at ./include/xapian/ base.h:154 #1 0x0032608a in Xapian::TermGenerator::Internal::index_text (this=0x9d77dc8, itor={p = 0x0, end = 0x9cb5db8 "", seqlen = 0}, weight=1, prefix=@0xbf84703c, with_positions=true) at queryparser/ termgenerator_internal.cc:207 #2 0x0032506c in Xapian::TermGenerator::index_text (this=0x9c94cd0, itor=@0xbf84702c, weight=1, prefix=@0xbf84703c) at queryparser/ termgenerator.cc:90 #3 0x0017100e in XS_Search__Xapian__TermGenerator_index_text (my_perl=0x9c78008, cv=0x9...
2007 Mar 09
5
memory leak in index build?
...ms'' require ''ferret'' require ''set'' dir = "temp_index" if ARGV.first=="-p" ARGV.shift prefix=ARGV.shift end fi= Ferret::Index::FieldInfos.new fi.add_field :name, :index => :yes, :store => :yes, :term_vector => :with_positions %w[data field1 field2 field3].each{|fieldname| fi.add_field fieldname.to_sym, :index => :yes, :store => :no, :term_vector => :with_positions } i = Ferret::Index::IndexWriter.new(:path=>dir, :create=>true, :field_infos=>fi) list=Dir["/usr/share/man/*/#{prefix}*....
2006 Jun 04
20
Proposal of some radical changes to API
...you store offsets, always store offsets 5. Once you store norms, always store norms So currently if you add a field like this (I''ll use the newer notation as it''s easier to type); doc << Field.new(:field, "data...", :index => :yes, :term_vector => :with_positions_offsets) And later add a field like this; doc << Field.new(:field, "diff...", :index => :no, :term_vector => :no) This field will be indexed and it''s term vectors will be stored regardless. This is good because if you are using TermVectors in a particular field...