Upgrading to 3.6 broke cachedsqlentityprocessor

[Brent Mills <bm...@uship.com>]

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">

Re: Upgrading to 3.6 broke cachedsqlentityprocessor

[Mikhail Khludnev <mk...@griddynamics.com>]

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 <bm...@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>
 <mk...@griddynamics.com>