Displaying 20 results from an estimated 5000 matches similar to: "Possiible Bug ? indexWriter#doc_countcountsdeleted docs after #commit"
2006 Sep 14
1
Possiible Bug ? indexWriter#doc_count counts deleted docs after #commit
I''m playing with "updating" docs in my index, and I think I''ve found bug
with IndexWriter counting deleted docs. Script and output follow:
=====
require ''rubygems''
require ''ferret''
p Ferret::VERSION
@doc = {:id => ''44'', :name => ''fred'', :email => ''abc at
2006 Sep 14
2
Possiible Bug ? indexWriter#doc_count countsdeleted docs after #commit
Hi David,
> Deleted documents don''t get deleted until commit is called
Ok, but FYI, my experiments show that #commit doesn''t affect #doc_count,
even across ruby sessions.
On a different note, I''d like to request a variation of #add_document
which returns the doc_id of the document added, as opposed to self.
I''m trying to track down an issue with a large
2006 Sep 22
3
Error with :create => true and existing index
I implemented a "reindex" command which simply creates an IndexWriter
with :create => true for a prexisting index.
The "reindexing" seems to start out ok, with several thousand docs
added, then Ferret throws an exception:
IO Error occured: couldn''t rename file "index\_0.tmp" to "index\_0.cfs":
<File exists>
I guess that _0.cfs is held
2006 Aug 28
12
Help with Multiple Readers, 1 Writer scenario
Hi,
I''m building a web server application using Ferret [thanks so much
Dave], Mongrel and Camping which works fine servicing one request at a
time, but serialises searches if more than one request arrives, so I''d
like some advice please about the best way to use multiple readers and
one writer.
Some background ... query requests which in my case are always read
only, arrive via
2006 Nov 22
1
Help with Multiple Readers, 1 Writer scenario
Some time back in September, [sorry to be so slow], Dave wrote:
> When you open an IndexReader on the index it is opened up on
> that particular version (or state) of the index. So any
> operations on the IndexReader (like searches) will only show
> what was in the index at the time you opened it. Any modifications
> to the index (usually through and IndexWriter) that occur
2007 Apr 12
2
Ferret 0.11.4.win32 indexing speed vs Ferret 0.10.9.win32
Firstly, thanks Dave for all your hard work. Ferret Rocks!,
I am just testing 0.11.4.win32 and it seems to work just fine, however
the index creation phase of my app is perhaps 3x slower under 0.11.4 vs
0.10.9
Details follow:
System: windows xp sp2, index on local hard disk, Ruby 1.8.6
Run #1, Ferret 0.10.9
- Reboot
- Build index, 35,000 rows added in 297 seconds
-
Run #2, Ferret 0.11.4
-
2006 Sep 28
3
A few questions about numbers and dates
Hi,
I just noticed that Ferret seems to convert every field to a string
[ruby code appended for those interested], which has thwarted my attempt
to format Dates (to "dd/mm/yyyy") and Floats (to "n.nn") for consumption
further down the line based on the class of the field stored.
I considered pre-formatting Dates and Floats prior to indexing, which
would store the field
2006 Jun 05
6
Ferret Win32 Gem for windows users ...
Hi and thanks for Ferret!
I''m wondering if it would be possible to create a Ferret Win32 gem which
includes the c performance code pre-compiled for those of us without a C
compiler handy ?
Zed Shaw seems to have cracked this particular nut with his Mongrel
Win32 gem.
Alternately, is there a zip of the Win32 .so Ferret needs that I could
download and manually install?
Kind Regards
2007 Mar 05
2
Warming up a new Searcher/Reader (Ferret 0.10.9 win32)
Hi,
I have a largish index [700MB] which is updated from time to time,
requiring me to close and recreate the Ferret::Search::Searcher to use
the latest index.
My problem is that the first few searches on the new index are slow [by
comparison to before the close/recreate], I''m guessing because the new
index is being loaded into RAM by my OS and into Ferret as needed.
I''m
2007 Mar 01
2
FerretHash
Dave, thank you so much for the 0.11 release(s). You have solved many
problems for me. As part of my appreciation for your good works, I am
offering up for public consideration a silly little class that I wrote.
(Code is below.) This class offers a simplified Hash-like interface to
(a very restricted subset of) Ferret. Hence I call it FerretHash.
FerretHash comes with its very own pet Ferret
2006 Sep 15
2
Trouble with "updating" a document
Hi,
I seem to be having trouble updating a doc, ie, deleting then re-adding
to the index.
The following script demonstrates my issue - I''m sure I''m missing
something obvious, but I can''t seem to find the problem. Can someone
point out where I am going wrong please ?
Regards
Neville
===
require ''rubygems''
require ''ferret''
p
2006 May 08
3
Index::Index.new vs. Readers and Writers
Hey gang,
A post on the Rails forum a while back had it sound like you pretty much
had to use the Index Readers & Writers if you were going to be
potentially accessing an index from more than one process. (i.e.
multiple dispatch.fcgi''s, etc)
Is this still the case, or does the main Index class do that black magic
behind the scenes? =)
I was having trouble implementing the
2008 Jan 09
5
Parallel indexing doesn''t work?
Hi,
I''m trying to get parallelized ferret indexing working for my AAF
indices, based on the example in the O''Reilly Ferret shortcut.
However, the resulting indices after merging seem to have no actual
documents.
I went and made minimal changes to the example in the Ferret shortcut
pdf, and indeed can''t get that to work either. I''d appreciate any help
2007 Feb 23
2
bug with boolean query evaluation containing parenthesis and NOT ?
Hi,
The following [simplified] query works well, however a variation which
includes parenthesis seems to fail, in that it returns hits which should
be excluded by the NOT term.
This is surprising because in this simple case, the parenthesis
shouldn''t change the Boolean evaluation ... any pointers?
Working Query: field1:value1 AND NOT field2:value2
Failing Query: field1:value1 AND
2006 Sep 05
4
Ferret 0.10.2 - Index#search_each() and :num_docs
Hi,
I seem to be having trouble getting more than 10 hits from
Index#search_each since upgrading to 0.10.2 (ie, this was working in
0.9.4). Maybe a bug, as the #search_each doesn''t seem to use the options
parameter any more ?
Thanks,
Neville
===========================================
require ''rubygems''
require ''ferret''
p Ferret::VERSION
idx =
2006 Jun 14
3
In memory IndexReader bug?
Hi All,
Hope all is going well.
I''m having trouble with the following code creating an in memory index
reader - it seems to be attempting to read from a file regardless.
Here''s the simple code:
require ''rubygems''
require ''ferret''
a = Ferret::Index::Index.new
r = Ferret::Index::IndexReader.new(nil)
Running the code on my OS X machine
2006 Dec 07
1
Range Query Term parsing bug in 0.10.6 win32 ?
Hi,
I think I''ve found a Range Query Term parsing bug ... the following term
should return names >= ''A'', but instead generates a parsing error
Term: name:[A>
Message: Nil bounds for range. A range must include either lower bound
or an upper bound
However, the slightly larger term, name:[AA> works just fine.
Any pointers please?
Kind Regards
Neville
2012 May 04
0
[LLVMdev] Getting Metadata
Hi.
I have strange case:
This is a code for getting metadata from callsite:
....
CallSite CS(cast<Value>(I->first));
SmallVector<std::pair<unsigned int, MDNode*> , 4> MD;
CS.getInstruction()->getAllMetadata(MD);
CS.getInstruction()->dump();
for (SmallVector<std::pair<unsigned int, MDNode*> , 4>::iterator md = MD.begin(); md!=MD.end(); md++)
2006 May 31
3
Camping and Builder and XML
Hi,
I have built a simple Camping application which indexes an ODBC
datasource using Ferret on startup, then accepts search strings and
renders the resulting hit list in HTML, and it works quite nicely.
The next step was to alternately render the list in XML for consumption
by another application. In Rails, I would simply use Builder in the view
to get the job done, and so I did the same in
2006 Sep 20
8
Understanding boost ?
Hi,
I''m confused about managing field boosting ...
I have set the :boost for the :name field in my docs to 10, via :boost
=> 10
Then I performed a search for ''keith'' over all fields via with
*:(keith*), expecting a doc with Keith in the :name field to come out on
top. But another doc with Keith mentioned in other fields (:comments,
:address) scored higher.
I