lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mikhail Khludnev <mkhlud...@griddynamics.com>
Subject Re: Upgrading to 3.6 broke cachedsqlentityprocessor
Date Tue, 01 May 2012 16:52:21 GMT
I know about one regression at least. Fix is already committed. see
https://issues.apache.org/jira/browse/SOLR-3360

On Tue, May 1, 2012 at 12:53 AM, Brent Mills <bmills@uship.com> wrote:

> I've read some things in jira on the new functionality that was put into
> caching in the DIH but I wouldn't think it should break the old behavior.
>  It doesn't look as though any errors are being thrown, it's just ignoring
> the caching part and opening a ton of connections.  Also I cannot find any
> documentation on the new functionality that was added so I'm not sure what
> syntax is valid and what's not.  Here is my entity that worked in 3.1 but
> no longer works in 3.6:
>
> <entity name="Emails" query="SELECT * FROM Account.SolrUserSearchEmails
> WHERE '${dataimporter.request.clean}' != 'false' OR DateUpdated >=
> dateadd(ss, -30, '${dataimporter.last_index_time}')"
> processor="CachedSqlEntityProcessor" where="UserID=Users.UserID">
>



-- 
Sincerely yours
Mikhail Khludnev
Tech Lead
Grid Dynamics

<http://www.griddynamics.com>
 <mkhludnev@griddynamics.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message