RE: caceh implemetation?

Mikhail Khludnev [via Lucene] [mailto:ml-node+s472066n421911...@n3.nabble.com] Sent: Friday, July 24, 2015 4:00 PM To: Carl Buxbaum Subject: Re: caceh implemetation? On Fri, Jul 24, 2015 at 1:06 AM, Shawn Heisey <[hidden email]> wrote: > On 7/23/2015 10:55 AM, cbuxbaum wrote: > > Say we

RE: cache implemetation?

aceh implemetation? On 7/23/2015 10:55 AM, cbuxbaum wrote: > Say we have 100 party records. Then the child SQL will be run 100 > times (once for each party record). Isn't there a way to just run the child > SQL on all of the party records at once with a join, using a GROUP BY

Re: caceh implemetation?

That's OK, I have determined that caching is not relevant to our use case. However, I have a question about the full import queries that we are using: Here is the SQL from the top level entity: query="SELECT DISTINCT 'LEAP_PARTY' AS DOCUMENT_TYPE, VPARTY.OWNER AS PARTY_OW

caceh implemetation?

Hi, We are trying to improve the performance of our data import. We tried using the CachedSqlEntityProcessor implementation, but that is apparently broken. I am looking at the workaround described below: https://issues.apache.org/jira/browse/SOLR-3857