lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Khludnev (JIRA)" <>
Subject [jira] [Commented] (SOLR-3430) DIH: More-realistic testing & subsequent bug fix
Date Fri, 04 May 2012 06:14:50 GMT


Mikhail Khludnev commented on SOLR-3430:


I agree that DB is better than Mock. I'd like to confirm that this approach covers query repetitions
issues too. In SOLR-3360 we had a bug when the same query runs many times. Blind automated
tests with in-memory DB won't cover such bugs - it will just run same sql 10 times w/o any
problems. Will we have a kind of utility wrapper prevents same query run again and again?

> DIH: More-realistic testing & subsequent bug fix
> ------------------------------------------------
>                 Key: SOLR-3430
>                 URL:
>             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, derby-, derby-,
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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message