[
https://issues.apache.org/jira/browse/SOLR-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-3430:
-----------------------------
Attachment: SOLR-3430.patch
I added a check to the # of queries being issued to the datasource and found an
additional bug. This is likely the bug users are reporting on the mailing list.
I will commit now to Trunk & 3.6.1 .
> DIH: More-realistic testing & subsequent bug fix
> ------------------------------------------------
>
> Key: SOLR-3430
> URL: https://issues.apache.org/jira/browse/SOLR-3430
> Project: Solr
> Issue Type: Bug
> Components: contrib - DataImportHandler
> Affects Versions: 3.6, 4.0
> Reporter: James Dyer
> Assignee: James Dyer
> Priority: Minor
> Fix For: 4.0, 3.6.1
>
> Attachments: SOLR-3430.patch, SOLR-3430.patch, SOLR-3430.patch,
> SOLR-3430.patch, derby-10.8.2.2.jar, derby-10.8.2.2.jar.sha1,
> derby-LICENSE-ASL.txt, derby-NOTICE.txt
>
>
> A couple of people have mentioned on the users' list that 3.6 changes break
> CachedSqlEntityProcessor. Part of the problem is the current DIH tests are
> not realistic: they mostly test 1 class at a time and not the full
> end-to-end interactions between components.
> This is a test of (Cached) SqlEntityProcessor using an in-memory Derby
> database. This hopefully is a first step in creating a series of new,
> more-rigorous DIH tests, which is needed in order to make changes without
> worry.
> This also revealed a bug in SortedMapBackedCache, which is fixed also. I'm
> not sure this is the same bug causing problems for the 2 users but once
> committed I will post a reply on the users' list to see if they can try it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
