: Tuesday, October 25, 2016 12:31 PM
To: solr-user
Subject: Re: CachedSqlEntityProcessor with delta-import
Why not use delete by id rather than query? It'll be more efficient
Probably not a big deal though.
On Tue, Oct 25, 2016 at 1:47 AM, Aniket Khare wrote:
> Hi Sowmya,
>
> I
7;${dataimporter.last_index_time}'"
>>
>>
>>
>>
>>
>>
>> -Original Message-
>> From: Dyer, James [mailto:james.d...@ingramcontent.com]
>> Sent: Friday, October 21, 2016 4:23 PM
>> To: solr-user@lucene.apache.org
>>
> '${dataimporter.last_index_time}'"
>
>
>
>
>
>
> -Original Message-
> From: Dyer, James [mailto:james.d...@ingramcontent.com]
> Sent: Friday, October 21, 2016 4:23 PM
> To: solr-user@lucene.apache.org
> Subject: RE: CachedSqlEntityProcessor wi
FROM content
WHERE active = 1 AND lastUpdate >
'${dataimporter.last_index_time}'"
-Original Message-
From: Dyer, James [mailto:james.d...@ingramcontent.com]
Sent: Friday, October 21, 2016 4:23 PM
To: solr-u
Sowmya,
My memory is that the cache feature does not work with Delta Imports. In fact,
I believe that nearly all DIH features except straight JDBC imports do not work
with Delta Imports. My advice is to not use the Delta Import feature at all as
the same result can (often more-efficiently) be
I'm noticing some very odd behavior using dataimport from the Admin UI.
Whenever I limit the number of rows to 75 or below, the aliases field never
gets populated. As soon as I increase the limit to 76 or more, the aliases
field gets populated!
What am I not understanding here?
On Tue, Jul 30,
FYI my sub-entity looks like the following
On 11/15/11 10:42 AM, Mark wrote:
I am trying to use the CachedSqlEntityProcessor with Solr 1.4.2
however I am not seeing any performance gains. I've read some other
posts that reference cacheKey and cacheLookup however I don't see any
reference to
