[
https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257899#comment-13257899
]
Karl Wright edited comment on CONNECTORS-347 at 4/19/12 11:23 PM:
------------------------------------------------------------------
Just saw it again; clearly it is "real".
My working hypothesis is that the counts returned by count(x) in the SQL
statements are in fact not synchronized with the transactions, so maybe the
count can "run behind". The context in which this happens is an initial crawl
of six documents, with a hopcount filter. If the filter is not working the
count would be 7; with a working filter, it's 6. But how can we then get 4?
was (Author: kwri...@metacarta.com):
Just saw it again; clearly it is "real".
> MySQL HopCount test sometimes fails
> -----------------------------------
>
> Key: CONNECTORS-347
> URL: https://issues.apache.org/jira/browse/CONNECTORS-347
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
> Affects Versions: ManifoldCF 0.5
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF next
>
>
> The HopcountMySQLIT test sometimes fails complaining that it is expecting to
> see 6 documents but only sees 4.
> {code}
> [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong
> number of documents processed - expected 6, saw 4
> [junit] at
> org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152)
> {code}
> This does not happen on every run.
--
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
