Hi Lance,
> You cannot give it a wildcard to go find dynamic fields;
ah, ok. But it would be nice to use wildcards.
You correctly guessed that I meant the wildcard querying. The
dynamicField definition is not the problem ... So one can define
and
then the query via myfield_t would work.
The term
Hello community and a nice satureday,
from several discussions about Solr and Nutch, I got some questions for a
virtual web-search-engine.
The requirements:
I. I need a scalable solution for a growing index that becomes larger than
one machine can handle. If I add more hardware, I want to linear
I'm putting together an entity. A simplified version of the database schema is
below. There is a 1-[0,1] relationship between Person and Address with
address_id being the nullable foreign key. If it makes any difference, I'm
using SQL Server 2005 on the backend.
Person [id (pk), name, addres
MLT needs term vectors. You may either store the term vectors while
indexing, or store the text so that the MLT handler can pull it and
analyze it. (Highlighting has the same problem.)
I don't know if you still need the stored text with term vectors in
the index, but storing neither will definitel
This is a slow way to do this; databases are capable of doing this
join and feeding the results very efficiently.
The 'skipDoc' feature allows you to break out of the processing chain
after the first query. It is used in the wikipedia example.
http://wiki.apache.org/solr/DataImportHandler
On Sat
I want to use fast highlighter in solr1.4 and find a issue in
https://issues.apache.org/jira/browse/SOLR-1268
File Name Date Attached ↑
Attached By Size
SOLR-1268.patch 2010-02-05 10:32 PM
Koji Sekiguc
On Fri, Jun 11, 2010 at 11:13 PM, Chris Hostetter
wrote:
>
> : Is there a way to dynamically point which dataConfig file to use to
> import
> : using DIH without using the defaults hardcoded in solrconfig.xml?
>
> what do you mean by "dynamically" ? ... it's a query param, so you can
> specify th
this looks like a common problem. I guess DIH should handle this more
gracefully. Instead of firing a query and failing it should not fire a query
if any of the values are missing . This can b made configurable if needed
On Sun, Jun 13, 2010 at 9:14 AM, Lance Norskog wrote:
> This is a slow way
