You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2010/07/18 23:55:49 UTC
[jira] Created: (LUCENE-2549) TimeLimitingCollector's
TimeExceededException contains useless relative docid
TimeLimitingCollector's TimeExceededException contains useless relative docid
-----------------------------------------------------------------------------
Key: LUCENE-2549
URL: https://issues.apache.org/jira/browse/LUCENE-2549
Project: Lucene - Java
Issue Type: Bug
Affects Versions: 3.0.2, 3.0.1, 3.0, 2.9.3, 2.9.2, 2.9.1, 2.9, 3.1, 4.0
Reporter: Uwe Schindler
Assignee: Uwe Schindler
We found another bug with the RandomIndexWriter: When TimeLimitingCollector breaks collection after timeout, it records the last/next collected docid. It does this without rebasing, so the docid is useless. TestTimeLimitingCollector checks the docid, but correctly rebases it (as only this makes sense). Because the RandomIndexWriter uses different merge settings, the index is now sometimes not optimized and so the test fails (which is correct, as the docid is useless for non-optimized index).
Attached is a patch that fixes this. Please tell me if I should backport to 2.9 and 3.0!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Updated: (LUCENE-2549) TimeLimitingCollector's
TimeExceededException contains useless relative docid
Posted by "Uwe Schindler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler updated LUCENE-2549:
----------------------------------
Fix Version/s: 3.1
4.0
Affects Version/s: (was: 4.0)
(was: 3.1)
> TimeLimitingCollector's TimeExceededException contains useless relative docid
> -----------------------------------------------------------------------------
>
> Key: LUCENE-2549
> URL: https://issues.apache.org/jira/browse/LUCENE-2549
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.9, 2.9.1, 2.9.2, 2.9.3, 3.0, 3.0.1, 3.0.2
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-2549.patch
>
>
> We found another bug with the RandomIndexWriter: When TimeLimitingCollector breaks collection after timeout, it records the last/next collected docid. It does this without rebasing, so the docid is useless. TestTimeLimitingCollector checks the docid, but correctly rebases it (as only this makes sense). Because the RandomIndexWriter uses different merge settings, the index is now sometimes not optimized and so the test fails (which is correct, as the docid is useless for non-optimized index).
> Attached is a patch that fixes this. Please tell me if I should backport to 2.9 and 3.0!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Reopened: (LUCENE-2549) TimeLimitingCollector's
TimeExceededException contains useless relative docid
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir reopened LUCENE-2549:
---------------------------------
reopening for possible 2.9.4/3.0.3 backport.
> TimeLimitingCollector's TimeExceededException contains useless relative docid
> -----------------------------------------------------------------------------
>
> Key: LUCENE-2549
> URL: https://issues.apache.org/jira/browse/LUCENE-2549
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.9, 2.9.1, 2.9.2, 2.9.3, 3.0, 3.0.1, 3.0.2
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 2.9.4, 3.0.3, 3.1, 4.0
>
> Attachments: LUCENE-2549.patch
>
>
> We found another bug with the RandomIndexWriter: When TimeLimitingCollector breaks collection after timeout, it records the last/next collected docid. It does this without rebasing, so the docid is useless. TestTimeLimitingCollector checks the docid, but correctly rebases it (as only this makes sense). Because the RandomIndexWriter uses different merge settings, the index is now sometimes not optimized and so the test fails (which is correct, as the docid is useless for non-optimized index).
> Attached is a patch that fixes this. Please tell me if I should backport to 2.9 and 3.0!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Updated: (LUCENE-2549) TimeLimitingCollector's
TimeExceededException contains useless relative docid
Posted by "Uwe Schindler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler updated LUCENE-2549:
----------------------------------
Attachment: LUCENE-2549.patch
> TimeLimitingCollector's TimeExceededException contains useless relative docid
> -----------------------------------------------------------------------------
>
> Key: LUCENE-2549
> URL: https://issues.apache.org/jira/browse/LUCENE-2549
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.9, 2.9.1, 2.9.2, 2.9.3, 3.0, 3.0.1, 3.0.2, 3.1, 4.0
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Attachments: LUCENE-2549.patch
>
>
> We found another bug with the RandomIndexWriter: When TimeLimitingCollector breaks collection after timeout, it records the last/next collected docid. It does this without rebasing, so the docid is useless. TestTimeLimitingCollector checks the docid, but correctly rebases it (as only this makes sense). Because the RandomIndexWriter uses different merge settings, the index is now sometimes not optimized and so the test fails (which is correct, as the docid is useless for non-optimized index).
> Attached is a patch that fixes this. Please tell me if I should backport to 2.9 and 3.0!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Resolved: (LUCENE-2549) TimeLimitingCollector's
TimeExceededException contains useless relative docid
Posted by "Uwe Schindler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler resolved LUCENE-2549.
-----------------------------------
Resolution: Fixed
Committed 3.0 branch revision: 1028920
Committed 2.9 branch revision: 1028922
> TimeLimitingCollector's TimeExceededException contains useless relative docid
> -----------------------------------------------------------------------------
>
> Key: LUCENE-2549
> URL: https://issues.apache.org/jira/browse/LUCENE-2549
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.9, 2.9.1, 2.9.2, 2.9.3, 3.0, 3.0.1, 3.0.2
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 2.9.4, 3.0.3, 3.1, 4.0
>
> Attachments: LUCENE-2549.patch
>
>
> We found another bug with the RandomIndexWriter: When TimeLimitingCollector breaks collection after timeout, it records the last/next collected docid. It does this without rebasing, so the docid is useless. TestTimeLimitingCollector checks the docid, but correctly rebases it (as only this makes sense). Because the RandomIndexWriter uses different merge settings, the index is now sometimes not optimized and so the test fails (which is correct, as the docid is useless for non-optimized index).
> Attached is a patch that fixes this. Please tell me if I should backport to 2.9 and 3.0!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Resolved: (LUCENE-2549) TimeLimitingCollector's
TimeExceededException contains useless relative docid
Posted by "Uwe Schindler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler resolved LUCENE-2549.
-----------------------------------
Resolution: Fixed
Committed trunk revision: 965299
Committed 3.x revision: 965300
Please reopen if we should backport to 2.9 or 3.0!
> TimeLimitingCollector's TimeExceededException contains useless relative docid
> -----------------------------------------------------------------------------
>
> Key: LUCENE-2549
> URL: https://issues.apache.org/jira/browse/LUCENE-2549
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.9, 2.9.1, 2.9.2, 2.9.3, 3.0, 3.0.1, 3.0.2
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-2549.patch
>
>
> We found another bug with the RandomIndexWriter: When TimeLimitingCollector breaks collection after timeout, it records the last/next collected docid. It does this without rebasing, so the docid is useless. TestTimeLimitingCollector checks the docid, but correctly rebases it (as only this makes sense). Because the RandomIndexWriter uses different merge settings, the index is now sometimes not optimized and so the test fails (which is correct, as the docid is useless for non-optimized index).
> Attached is a patch that fixes this. Please tell me if I should backport to 2.9 and 3.0!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Updated: (LUCENE-2549) TimeLimitingCollector's
TimeExceededException contains useless relative docid
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-2549:
--------------------------------
Fix Version/s: 3.0.3
2.9.4
> TimeLimitingCollector's TimeExceededException contains useless relative docid
> -----------------------------------------------------------------------------
>
> Key: LUCENE-2549
> URL: https://issues.apache.org/jira/browse/LUCENE-2549
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.9, 2.9.1, 2.9.2, 2.9.3, 3.0, 3.0.1, 3.0.2
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 2.9.4, 3.0.3, 3.1, 4.0
>
> Attachments: LUCENE-2549.patch
>
>
> We found another bug with the RandomIndexWriter: When TimeLimitingCollector breaks collection after timeout, it records the last/next collected docid. It does this without rebasing, so the docid is useless. TestTimeLimitingCollector checks the docid, but correctly rebases it (as only this makes sense). Because the RandomIndexWriter uses different merge settings, the index is now sometimes not optimized and so the test fails (which is correct, as the docid is useless for non-optimized index).
> Attached is a patch that fixes this. Please tell me if I should backport to 2.9 and 3.0!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org