Michael Bell wrote:
> How best to diagnose?
>
>> Call your java process this way
>>java -XX:HeapDumpPath=. -XX:+HeapDumpOnOutOfMemoryError
>> and drag'n'drop the resulting java_pid*.hprof into eclipse.
>> You will get an outline by class for the number and size of allocated
>> objects.
Just lo
On Saturday 03 September 2011 20:09:54 Michael Bell wrote:
> 2011-08-30 13:01:31,489 [TP-Processor8] ERROR
> com.gwava.utils.ServerErrorHandlerStrategy - reportError:
> nastybadthing ::
> com.gwava.indexing.lucene.internal.LuceneSearchController.performSear
>chOperation:229 :: EXCEPTION : java.lang
On Sunday 12 June 2011 22:12:01 Michael McCandless wrote:
> Anyway, I don't think that's a good tradeoff, in general, for our
> users, because very few apps truly require immediate consistency from
> Lucene (can anyone give an example where their app depends on
> immediate consistency...?
For data
On Tuesday 18 January 2011 22:04:01 Grant Ingersoll wrote:
Where do you get your Lucene/Solr downloads from?
[x] ASF Mirrors (linked in our release announcements or via the Lucene
website)
[] Maven repository (whether you use Maven, Ant+Ivy, Buildr, etc.)
[] I/we build them from source via an
On Monday 09 August 2010 21:16:30 Mark Miller wrote:
> Lucid Imagination Presents a free technical webinar: Mastering the
> Lucene Index
> Wednesday, August 11, 2010 11:00 AM PST / 2:00 PM EST / 20:00 CET
>
> Sign up here:
> http://www.eventsvc.com/lucidimagination/081110?trk-AP
Did this work for
On Wednesday 17 March 2010 18:42:10 mark harwood wrote:
> Not the fastest thing in the world but works:
>
> Term startTerm=new Term("myFieldName","");
> TermEnum te=reader.terms(startTerm);
> BitSet docsRead=new BitSet(reader.maxDoc());
>
Hello
Is there an api that indicates whether a field is multivalued, just like
IndexReader.getFieldNames(IndexReader.FieldOption fldOption) does it
for fields beeing indexed/stored/termvector?
Of course I could track it at index time.
Stefan
---
Hello
For a source code (git repo) search engine I choose to use an ngram
analyzer for substring search (something like "git blame").
This worked fine except it didn't find some strings. I tracked it down
to the analyzer. When the ngram analyzer yielded about 1000 terms it
stopped yielding mor
On Wednesday 02 December 2009 16:20:28 Stefan Trcek wrote:
> On Wednesday 02 December 2009 15:50:45 archibal wrote:
> > -optionnally i want to have a central server which index all data
> > (name of files, folders and file content) on network and i would
> > like to connect
On Wednesday 02 December 2009 15:50:45 archibal wrote:
>
> -optionnally i want to have a central server which index all data
> (name of files, folders and file content) on network and i would like
> to connect via a browser on the central server ? are there project
> who does this or something like
On Monday 30 November 2009 18:51:34 Nick Burch wrote:
> On Mon, Nov 30, 2009 at 12:22 PM, Stefan Trcek
wrote:
> > I'd do, but was not successful to get the svn repo some months ago.
> > I have to claim the sys admin for any svn repo to open a door
> > through th
On Tuesday 01 December 2009 11:07:41 Michael McCandless wrote:
> OK -- none of IndexSearcher's search methods needed tweaking? Just
> TopDocs/TopFieldDocs?
Yes, you can use these methods in Searcher, they are sufficient:
TopDocs Searcher.search(Query query, Filter filter, int n)
TopFieldDocs Sea
Stefan
> On Mon, Nov 30, 2009 at 12:22 PM, Stefan Trcek
wrote:
> > On Monday 30 November 2009 14:24:20 Michael McCandless wrote:
> >> I agree, it's silly we label things like TopDocs/TopFieldDocs as
> >> expert -- they are no longer for "low level" API
On Monday 30 November 2009 14:24:20 Michael McCandless wrote:
> I agree, it's silly we label things like TopDocs/TopFieldDocs as
> expert -- they are no longer for "low level" APIs (or, perhaps since
> we've removed the "high level" API (= Hits), what remains should no
> longer be considered low le
On Friday 27 November 2009 14:49:07 Michael McCandless wrote:
> So the "don't care" equivalent here is to use IndexSearcher's normal
> search APIs (ie, we don't use Version to switch this on or off).
Hmm - Searcher/IndexSearchers search methods are "Low
level", "Expert", "Expert + low level" or r
On Friday 27 November 2009 14:49:07 Michael McCandless wrote:
>
> So the "don't care" equivalent here is to use IndexSearcher's normal
> search APIs (ie, we don't use Version to switch this on or off).
Thanks for the hint. For an unknown reason I once fell into
the "search(query, filter, collecto
On Friday 27 November 2009 12:07:07 Michael McCandless wrote:
> Re: What does "out of order" mean?
>
> It refers to the order in which the docIDs are delivered to your
> Collector.
>
> "Normally" they are always delivered in increasing order.
>
> However, some queries (well, currently only certain
On Friday 16 October 2009 08:57:37 Michael Busch wrote:
>
> So please tell us which you prefer as a back compatibility policy for
> Lucene:
I don't do drop in but recompile anyway, so it doesn't matter for me.
It is only important that the documentation is clear about what has to
be done.
> B) b
On Wednesday 12 November 2008 14:58:53 Christian Reuschling wrote:
> In order to offer some simple 1:n matching, currently we create
> several, counted attributes and expand our queries that we search
> inside each attribute, e.g.:
I use one attribute (Field) multiple times.
Stefan
-
On Monday 10 November 2008 14:58:15 Mark Miller wrote:
> > But: it's slow to load a field for the first time. LUCENE-1231
> > (column-stride fields) aims to greatly speed up the load time.
>
> Test it out though. In some recent testing I was doing it was *way*
> faster than I thought it would be b
On Tuesday 11 November 2008 02:18:39 Erik Hatcher wrote:
>
> The integration won't be too painful... the main thing is that Solr
> requires* some configuration files, literally on the filesystem, in
> order to fire up and be happy. And you'll need to craft Solr's
> schema.xml to jive with how you
On Monday 10 November 2008 13:55:31 Michael McCandless wrote:
>
> Finally, you might want to instead look at Solr, which provides facet
> counting out of the box, rather than roll your own...
Doooh - new api, but it's facet counting sounds good.
Any starting points for moving from plain lucene to
On Friday 07 November 2008 18:46:17 Michael McCandless wrote:
>
> Sorting populates the field cache (internal to Lucene) for that
> field, meaning it loads all values for all docs and holds them in
> memory. This makes the first query slow, and, consumes RAM, in
> proportion to how large your ind
On Thursday 06 November 2008 10:18:45 Dora wrote:
> Lucene will then tell me which contacts match my query, but is there
> a way to know which field(s) matched the request ?
> The goal is to display the XML with the matching fields highlighted.
I think org.apache.lucene.search.highlight.Highlight
Hello
When using "new QueryParser(...).parse(...)" I'd like to get the
position where the error was detected (to show it to the user).
See (and run) the code below.
This is not possible via "e.currentToken" (that's null). Nevertheless
this position will be printed within the getMessage() method
25 matches
Mail list logo
