[
https://issues.apache.org/jira/browse/LUCENE-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1771:
--------------------------------
Attachment: LUCENE-1771.patch
Here it is basically.
Core tests pass, but oddly TestCompoundWordTokenFilter took a real long time in
contrib.
[junit] Testsuite:
org.apache.lucene.analysis.compound.TestCompoundWordTokenFilter
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 195.028 sec
Benchmark also was pretty slow. I'm guessing because of autocommit. Similar
symptoms.
Perhaps my OS is messed up - would be odd though - fresh install from a week
ago. Never noticed things being so slow before though. TestQualityRun is taking
forever. So the benchmark thing could very well be an isolated issue.
> Using explain may double ram reqs for fieldcaches when using
> ValueSourceQuery/CustomScoreQuery or for ConstantScoreQuerys that use a
> caching Filter.
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-1771
> URL: https://issues.apache.org/jira/browse/LUCENE-1771
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 2.9
>
> Attachments: LUCENE-1771.patch, LUCENE-1771.patch, LUCENE-1771.patch,
> LUCENE-1771.patch, LUCENE-1771.patch
>
>
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
