On Wed, Jan 12, 2011 at 8:49 PM, alexei wrote:
[...]
> Unfortunately reorganizing the data is not an option for me.
> Multiple databases exist and a third party is taking care of
> populating them. Once a database reaches a certain size, a switch
> occurs and a new database is created with the sam
release?
Regards,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/Resolve-a-DataImportHandler-datasource-based-on-previous-entity-tp2235573p2241653.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Wed, Jan 12, 2011 at 1:40 AM, alexei wrote:
[...]
> The datasource number is stored in the database.
> The parent entity queries for this number and in theory it
> should becomes available to the child entity - "Article" in my case.
I do not think that it is possible to have the datasource nam
oad-config ?
In my mind this should be following the same mechanism which resolves
variables in queries.
Any other ideas?
Regards,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/Resolve-a-DataImportHandler-datasource-based-on-previous-entity-tp2235573p2236472.html
Sen
On Tue, Jan 11, 2011 at 11:10 PM, alexei wrote:
>
> Hi,
>
> I am in a situation where the data needed for one of the fields in my
> document
> may be sitting in a different datasource each time.
[...]
At what point of time will you be aware of which datasource
the field is coming from? How are yo
Hi,
I am in a situation where the data needed for one of the fields in my
document
may be sitting in a different datasource each time.
I would like to be able to configure something like this:
http://lucene.472066.n3.nabble.com/Resolve-a-DataImportHandler-datasource-based-on-previous-entity
