I have system in which documents and Query comes frequently .I am
creating index writer in memory every time for each query I request . I
want to know Is it good to separate Index Writing and loading and Query
request ? Whether It is good to save index writer on hard disk .Whether it
is time co
I'm new to Lucene and search technology. I've read just enough to be
confused and dangerous, so please bear with me.
My documents have sets of integer ranges, like 1-3,
12-20,13290-16509,
The total enumeration of ranges across all documents will be tens of
thousands. Most documents will
Probably the simplest thing is to define a field for each of the
contexts you are interested in, but you might want to consider using a
tagged-token approach.
I spent a while figuring out how to index tagged tree-structured data
and came up with Lux (http://luxdb.org) - basically it accepts XM
You can only use the PayloadAttribute at the moment. In general the way to go
is to add another TokenFilter at the end of your indexing chain, that converts
all those attributes to a single Payload (serializing them). On the search
side, there are multiple possibilities to access the payloads (a
Hi,
I want to create a Lucene analyzer for RDF nodes. RDF nodes can have
multiple types (uri, bnode, plain literal, plain literal with language,
typed literal with datatype). While analyzing the term, I want to create a
RDFNodeTypeAttribute, LanguageAttribute and DatatypeAttribute to store
respect
Hi,
I have used the data import handler feature of importing 500 RTF's into Solr
and have been able to search the query string also. I have made use of fq
param as a filter query parameter to limit my search space to only the document
ids that I am interested in. However I am bogged with two q
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I remember that there was a general Searcher interface, with the standard
IndexSearcher as
subclass, plus some subclass that enabled RMI-based remote access to an index.
In the case you used Searcher in your codebase, the code was independent from
ac
The the majority of queries will be look-ups of functions/types by fully
qualified name. For example, the query [Data.Map.insert] will find the
definition and all uses of the `insert` function defined in the `Data.Map`
module. The corpus is all Haskell open source code on hackage.haskell.org.
Bein