[
https://issues.apache.org/jira/browse/LUCENE-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414576#comment-13414576
]
Chris Male commented on LUCENE-4173:
{quote}
Having said all this, and even suggested
[
https://issues.apache.org/jira/browse/LUCENE-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414573#comment-13414573
]
David Smiley commented on LUCENE-4173:
--
bq. Is the idea to push the decision about
[
https://issues.apache.org/jira/browse/LUCENE-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414566#comment-13414566
]
Robert Muir commented on LUCENE-4221:
-
This patch disables all the offsets checks for
[
https://issues.apache.org/jira/browse/LUCENE-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4221:
Attachment: LUCENE-4221.patch
> CheckIndex is overeager for term vector offsets bounds checks
Robert Muir created LUCENE-4221:
---
Summary: CheckIndex is overeager for term vector offsets bounds
checks
Key: LUCENE-4221
URL: https://issues.apache.org/jira/browse/LUCENE-4221
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414562#comment-13414562
]
Jack Krupansky commented on SOLR-3619:
--
Now I am confused. The summary seems deceptive
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414555#comment-13414555
]
Jan Høydahl commented on SOLR-3619:
---
Sure it would be nice to be GSAish. Everything with
[
https://issues.apache.org/jira/browse/SOLR-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3621:
--
Attachment: SOLR--3621.patch
> Fix concurrency race around newIndexWriter
> ---
[
https://issues.apache.org/jira/browse/SOLR-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414548#comment-13414548
]
Mark Miller commented on SOLR-3621:
---
A first patch.
> Fix concurrency ra
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414544#comment-13414544
]
Mark Miller commented on SOLR-3619:
---
Since I think there is at least general agreement on
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414534#comment-13414534
]
Mark Miller commented on SOLR-3619:
---
bq. So in calling it example (or template or skeleto
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414531#comment-13414531
]
Jan Høydahl commented on SOLR-3619:
---
bq. we are renaming it from example because we are r
Mark Miller created SOLR-3621:
-
Summary: Fix concurrency race around newIndexWriter
Key: SOLR-3621
URL: https://issues.apache.org/jira/browse/SOLR-3621
Project: Solr
Issue Type: Bug
Co
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java7-64/296/
1 tests failed.
REGRESSION: org.apache.solr.spelling.suggest.SuggesterFSTTest.testSuggestions
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
at
__
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java8-64/16/
1 tests failed.
REGRESSION:
org.apache.solr.handler.component.SpellCheckComponentTest.testPerDictionary
Error Message:
mismatch: '0'!='2' @ spellcheck/suggestions/bar/startOffset
Stack Trace:
java.lang.RuntimeE
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/483/
1 tests failed.
REGRESSION:
org.apache.lucene.search.grouping.DistinctValuesCollectorTest.testRandom
Error Message:
testRandom(org.apache.lucene.search.grouping.DistinctValuesCollectorTest):
Insane FieldCache us
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/1261/
1 tests failed.
REGRESSION:
org.apache.solr.handler.dataimport.TestSqlEntityProcessor2.testCompositePk_FullImport
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception durin
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x-java7/127/
No tests ran.
Build Log:
[...truncated 17829 lines...]
[...truncated 17829 lines...]
[...truncated 17829 lines...]
[...truncated 8520 lines...]
check-forbidden-apis:
validate:
[echo] Building solr...
compile-tool
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2899/
1 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.handler.TestReplicationHandler
Error Message:
ERROR: SolrIndexSearcher opens=74 closes=73
Stack Trace:
java.lang.AssertionError: ERROR: SolrIndexSearc
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java8-64/12/
1 tests failed.
REGRESSION:
org.apache.solr.handler.component.SpellCheckComponentTest.testPerDictionary
Error Message:
mismatch: '0'!='2' @ spellcheck/suggestions/bar/startOffset
Stack Trace:
java.lang.RuntimeExce
Formatted exception messages for non-scalar values is highly desirable, if
not essential. Not just that a map/list does not match, but how it doesn't
match - missing keys, extra keys, which key values differ (which can be a
recursive process).
-- Jack Krupansky
-Original Message-
Fro
Uwe Schindler created LUCENE-4220:
-
Summary: Replace benchmarks crazy HTML parser by a nekohtml
10-liner
Key: LUCENE-4220
URL: https://issues.apache.org/jira/browse/LUCENE-4220
Project: Lucene - Java
I like that, nice builder pattern *duck* ! (running away)
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of
> Dawid Weiss
> Sent: Saturday,
We use (and like) fest asserts. The syntax is nice but what's even
nicer are formatted exception messages for arrays, maps, etc. so you
get the idea what the mismatch was.
http://code.google.com/p/fest/
see fluid assertions; or here a new 2.x line of development:
https://github.com/alexruiz/fest-
On Sat, Jul 14, 2012 at 6:51 AM, Uwe Schindler wrote:>
> That's definitely the case, also (partly in Java 7 for
> HashSet/HashMaps/ConcurrentHashMap > 512 entries). They have now a better
> has algorithm enabled by default. I already fixed some Solr tests doing
> Map.toString() and compare against
Some typo in last example (toString() missing):
> If you want to compare by String and you only have a HashMap/HashSet, the
> trick is:
>
> assertEquals("map differs", "{items}", new
TreeMap(someMapToTest).toString());
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thet
Hi,
> "... tests doing Map.toString() and compare against a hardcoded String
(which
> is of course wrong for HashMaps or HashSets because order is undefined)."
>
> Map.toString sounds like a great operation to forbid in Solr/Lucene,
especially
> in tests. Although Map.toString is still helpful
"... tests doing Map.toString() and compare against a hardcoded String
(which is of course wrong for HashMaps or HashSets because order is
undefined)."
Map.toString sounds like a great operation to forbid in Solr/Lucene,
especially in tests. Although Map.toString is still helpful for
debug/lo
[
https://issues.apache.org/jira/browse/LUCENE-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4217:
--
Summary: Load clover.jar from ivy-cachepath and store license key in SVN
(was: Load clover.ja
[
https://issues.apache.org/jira/browse/LUCENE-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414363#comment-13414363
]
Uwe Schindler commented on LUCENE-4217:
---
Clover reports of Lucene and Solr look coo
> Or it could just be that something in Java8 causes orderings of some
container (like a Map) to be different.
That's definitely the case, also (partly in Java 7 for
HashSet/HashMaps/ConcurrentHashMap > 512 entries). They have now a better
has algorithm enabled by default. I already fixed some Sol
On Sat, Jul 14, 2012 at 6:37 AM, Uwe Schindler wrote:
> Thanks for taking care. Interestingly this test was mostly failing in Java 8
> EA builds. Strange, maybe there is something different with Java 8!
Yeah, there still could be something else wrong with the test or
elevate component itself - I
[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414326#comment-13414326
]
Yonik Seeley commented on SOLR-3619:
bq. I think calling it an example is a real turn o
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414324#comment-13414324
]
Yonik Seeley commented on SOLR-139:
---
The create-if-not-exist patch was committed to both t
I'm sorry the info has been dribbling in slowly; it's all now summarized in
CONNECTORS-491. Now that I've confirmed that this even occurs for them without
the ";" (unlike what I was originally told) it is clear it is a config related
issue. I have urged them to look to this list for further he
[
https://issues.apache.org/jira/browse/LUCENE-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-4217.
---
Resolution: Fixed
Committed trunk r1361480, 4.x r1361481.
Also committed nightly changes in
36 matches
Mail list logo
