Hi Mitch,
> New idea:
> Create a method which returns the query-string:
>
> returnString(theVIP)
> {
> if ( theVIP != null || theVIP != "")
> {
> return "a query-string to find the vip"
> }
> else
> {
> return "SELECT 1" // you need to modify this, so that it
> matches your field-definition
> }
> }
>
> The main-idea is to perform a blazing fast query, instead of a complex
> IN-clause-query.
> Does this sounds like a solution???
I was using "in" because it's a multiValued input that results in
multiValued output (not necessarily but it's most probable - it's either
empty or multiple values).
I don't understand how I can make your solution work with multivalued
input/output?
> > The new approach is to query the solr index for that other database that
> > I've already setup. This is only a bit slower than the original query
> > (20min). (I'm using URLDataSource to be 1.4.1 conform.)
> >
> Unfortunately I can not follow you.
> You are querying a solr-index for a database?
Yes, because I've already put one up (second core) and used SolrJ to get
what I want later on, but it would be better to compute the relation
between the two indexes at index time instead of at query time. (If it
would have worked with the db entity the second index wouldn't have been
required, anymore.)
But now that it works well with the url entity I'm fine with maintaining
that second index. It's not that much effort.
I've subclassed URLDataSource to add a check whether the list of input
values is empty and only proceed when this is not the case. If realized
that I have to throw an exception and add the onError attribute to the
entity to make that work.
Thanks!
Chantal
