3. SQL standard "=" matching when possible to reduce the candidate data set.
>>> 4. Dismax match based on a rule set Joining SQL Server candidate dataset
>>> against Solr indexing set using a join operator.
>>> 5. Cache possible matches in SQL Server for a given r
r indexing set using a join operator.
>> 5. Cache possible matches in SQL Server for a given record in order for a
>> human to disposition them.
>>
>> From what I read, Carrot is great for Solr clustering, but once you get into
>> RDBMS, you're out of luck.
>
> From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
> Sent: Thursday, December 31, 2015 12:44 AM
> To: solr-user
> Subject: Re: Teiid with Solr - using any other engine except the
> SolrDefaultQueryEngine
>
> Are you trying to do federated search? What about carrot? Not the o
hem.
From what I read, Carrot is great for Solr clustering, but once you get into
RDBMS, you're out of luck.
-Original Message-
From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
Sent: Thursday, December 31, 2015 12:44 AM
To: solr-user
Subject: Re: Teiid with Solr - using a
Are you trying to do federated search? What about carrot? Not the one that
ships with Solr, the parent project.
Regards,
Alex
On 31 Dec 2015 12:21 am, "Mark Horninger"
wrote:
> I have gotten Teiid and Solr wired up, but it seems like the only way to
> query is with the default Solr Query Engi
I have gotten Teiid and Solr wired up, but it seems like the only way to query
is with the default Solr Query Engine, and nothing else. In asking Dr. Google,
this is a data black hole. The more I look at it, the more I think I'm going
to end up having to write a custom translator. Is there an
