Thanks Jay for the quick reply.
Maybe we can set up a dev env with trunk and use JOIN.
Is JOIN a good use case for this ?
On 11 June 2011 15:28, Jay Luker wrote:
> You are correct that ExternalFileField values can only be used in
> query functions (i.e. scoring, basically). Sorry for firing off
You are correct that ExternalFileField values can only be used in
query functions (i.e. scoring, basically). Sorry for firing off that
answer without reading your use case more carefully.
I'd be inclined towards giving your Option #1 a try, but that's
without knowing much about the scale of your a
Hi Jay
I thought external file field could not be returned as a field but
only used in scoring.
trunk has pseudo field which can take a function value but we cant
move to trunk.
also its a more general question around schema design, what happens if
you have several fields with different update fre
Take a look at ExternalFileField [1]. It's meant for exactly what you
want to do here.
FYI, there is an issue with caching of the external values introduced
in v1.4 but, thankfully, resolved in v3.2 [2]
--jay
[1]
http://lucene.apache.org/solr/api/org/apache/solr/schema/ExternalFileField.html
[2
Hi,
We have a document type which has fields which are pretty static. Say
they change once every 6 month. But the same document has a field
which changes hourly
What are the best approaches to index this document ?
Eg
Hotel ID (static) , Hotel Description (static and costly to get from a
url etc),
