Apache Jenkins Server | 1 Aug 2011 02:12
Picon

[JENKINS] Lucene-3.x - Build # 456 - Failure

Build: https://builds.apache.org/job/Lucene-3.x/456/

1 tests failed.
REGRESSION:  org.apache.lucene.index.TestPayloads.testThreadSafety

Error Message:
expected:<[�]˗> but was:<[]˗>

Stack Trace:
	at org.apache.lucene.index.TestPayloads.testThreadSafety(TestPayloads.java:518)
	at org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(LuceneTestCase.java:1335)
	at org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(LuceneTestCase.java:1240)

Build Log (for compile errors):
[...truncated 14563 lines...]
Steven A Rowe | 1 Aug 2011 02:50
Picon
Favicon

RE: [JENKINS] Lucene-3.x - Build # 456 - Failure

I can reproduce this error about 75% of the time, with both 1.6 and 1.5 Oracle JVMs on Windows 7:

ant test-core -Dtestcase=TestPayloads -Dtestmethod=testThreadSafety
-Dtests.seed=-3021922680363445715:6414710724825348772 -Dtests.multiplier=3 -Dtests.nightly=true

Steve

-----Original Message-----
From: Apache Jenkins Server [mailto:jenkins <at> builds.apache.org] 
Sent: Sunday, July 31, 2011 8:13 PM
To: dev <at> lucene.apache.org
Subject: [JENKINS] Lucene-3.x - Build # 456 - Failure

Build: https://builds.apache.org/job/Lucene-3.x/456/


1 tests failed.
REGRESSION:  org.apache.lucene.index.TestPayloads.testThreadSafety

Error Message:
expected:<[ ]˗> but was:<[]˗>

Stack Trace:
	at org.apache.lucene.index.TestPayloads.testThreadSafety(TestPayloads.java:518)
	at org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(LuceneTestCase.java:1335)
	at org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(LuceneTestCase.java:1240)




Build Log (for compile errors):
(Continue reading)

Robert Muir (JIRA | 1 Aug 2011 02:59
Picon
Favicon

[jira] [Resolved] (LUCENE-3351) DirectSpellChecker throws NPE if field doesn't exist


     [
https://issues.apache.org/jira/browse/LUCENE-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir resolved LUCENE-3351.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0
         Assignee: Robert Muir

> DirectSpellChecker throws NPE if field doesn't exist
> ----------------------------------------------------
>
>                 Key: LUCENE-3351
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3351
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: modules/spellchecker
>    Affects Versions: 4.0
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>             Fix For: 4.0
>
>         Attachments: LUCENE-3351.patch
>
>
> DirectSpellchecker doesn't check that the resulting Terms is null,
> it should return an empty list here.

(Continue reading)

Chris Hostetter | 1 Aug 2011 04:24

Re: svn commit: r1152673 - /lucene/dev/branches/branch_3x/lucene/src/test/org/apache/lucene/index/Tes tPayloads.java


: fix test to not create invalid unicode

I'm confused ... when/why does randomFixedByteLengthUnicodeString not 
return valid unicode?

: -      // this test needs the random data to be valid unicode
: -      String s = _TestUtil.randomFixedByteLengthUnicodeString(random, data.length);

-Hoss
Robert Muir | 1 Aug 2011 04:33
Picon
Gravatar

Re: svn commit: r1152673 - /lucene/dev/branches/branch_3x/lucene/src/test/org/apache/lucene/index/Tes tPayloads.java

On Sun, Jul 31, 2011 at 10:24 PM, Chris Hostetter
<hossman_lucene <at> fucit.org> wrote:
>
> : fix test to not create invalid unicode
>
> I'm confused ... when/why does randomFixedByteLengthUnicodeString not
> return valid unicode?
>

I'm confused too, but all of the issues are with replacement chars for
invalid unicode:

Since the intent of this test is to test thread safety, not to test
unicode enc/dec back and forth, I switched it to ascii until the test
grows up (e.g. trunk, which now uses full unicode range correctly,
maybe I backported this wrong before)

--

-- 
lucidimagination.com
Bill Bell (JIRA | 1 Aug 2011 04:55
Picon
Favicon

[jira] [Commented] (SOLR-2337) Solr needs hits= added to the log when using grouping


    [
https://issues.apache.org/jira/browse/SOLR-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073426#comment-13073426
] 

Bill Bell commented on SOLR-2337:
---------------------------------

MArtin,

Are you logging it in your latest patch?

If so, we can close this. We use the info in the log to try to find queries where users get 0 results, and we are
using grouping exclusively.

> Solr needs hits= added to the log when using grouping 
> ------------------------------------------------------
>
>                 Key: SOLR-2337
>                 URL: https://issues.apache.org/jira/browse/SOLR-2337
>             Project: Solr
>          Issue Type: Bug
>          Components: SearchComponents - other
>    Affects Versions: 4.0
>            Reporter: Bill Bell
>             Fix For: 4.0
>
>         Attachments: SOLR.2337.patch
>
>
(Continue reading)

Bill Bell (JIRA | 1 Aug 2011 04:57
Picon
Favicon

[jira] [Closed] (SOLR-2154) Spatial support for MultiValued fields


     [
https://issues.apache.org/jira/browse/SOLR-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Bell closed SOLR-2154.
---------------------------

    Resolution: Duplicate

This is duplicated

> Spatial support for MultiValued fields
> --------------------------------------
>
>                 Key: SOLR-2154
>                 URL: https://issues.apache.org/jira/browse/SOLR-2154
>             Project: Solr
>          Issue Type: New Feature
>          Components: Build
>    Affects Versions: 4.0
>            Reporter: Bill Bell
>             Fix For: 4.0
>
>
> Is this an issue - it appears to work ?
> This appears to work on LatLon Spatial fields. It appears to find the right lat long... Is this supposed to work?
> I read that this does not work on solr.PointType, but it appears to work on LatLonType.
>  <fieldType name="location" class="solr.PointType" dimension="2" subFieldSuffix="_d"/>
> <field name="store" type="location" indexed="true" stored="true" multiValued="true"/>
> Trying a few queries and I can get either of the 2 points.
(Continue reading)

Bill Bell (JIRA | 1 Aug 2011 05:01
Picon
Favicon

[jira] [Created] (SOLR-2686) Extend FieldCache architecture to multiple Values

Extend FieldCache architecture to multiple Values
-------------------------------------------------

                 Key: SOLR-2686
                 URL: https://issues.apache.org/jira/browse/SOLR-2686
             Project: Solr
          Issue Type: Bug
            Reporter: Bill Bell

I would consider this a bug. It appears lots of people are working around this limitation, 
why don't we just change the underlying data structures to natively support multiValued fields in the
FieldCache architecture?

Then functions() will work properly, and we can do things like easily geodist() on a multiValued field.

Thoughts?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Apache Jenkins Server | 1 Aug 2011 06:24
Picon

[JENKINS] Lucene-Solr-tests-only-3.x - Build # 9905 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/9905/

1 tests failed.
REGRESSION:  org.apache.solr.client.solrj.embedded.MultiCoreExampleJettyTest.testMultiCore

Error Message:
Can not find: /example/core1/update  Can not find: /example/core1/update  request: http://localhost:43192/example/core1/update?commit=true&waitFlush=true&waitSearcher=true&wt=javabin&version=2

Stack Trace:
org.apache.solr.common.SolrException: Can not find: /example/core1/update

Can not find: /example/core1/update

request: http://localhost:43192/example/core1/update?commit=true&waitFlush=true&waitSearcher=true&wt=javabin&version=2
	at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:430)
	at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:244)
	at org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:105)
	at org.apache.solr.client.solrj.MultiCoreExampleTestBase.testMultiCore(MultiCoreExampleTestBase.java:79)
	at org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(LuceneTestCase.java:1335)
	at org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(LuceneTestCase.java:1240)

Build Log (for compile errors):
[...truncated 14146 lines...]
Alexey Serba (JIRA | 1 Aug 2011 06:59
Picon
Favicon

[jira] [Commented] (SOLR-2382) DIH Cache Improvements


    [
https://issues.apache.org/jira/browse/SOLR-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073437#comment-13073437
] 

Alexey Serba commented on SOLR-2382:
------------------------------------

James, I tested your patch (SOLR-2382-solrwriter-verbose-fix.patch) and verified that verbose output
is working ok now. Noble, could you please review and commit this patch?

> DIH Cache Improvements
> ----------------------
>
>                 Key: SOLR-2382
>                 URL: https://issues.apache.org/jira/browse/SOLR-2382
>             Project: Solr
>          Issue Type: New Feature
>          Components: contrib - DataImportHandler
>            Reporter: James Dyer
>            Priority: Minor
>         Attachments: SOLR-2382-dihwriter.patch, SOLR-2382-entities.patch, SOLR-2382-entities.patch,
SOLR-2382-entities.patch, SOLR-2382-properties.patch, SOLR-2382-properties.patch,
SOLR-2382-solrwriter-verbose-fix.patch, SOLR-2382-solrwriter.patch,
SOLR-2382-solrwriter.patch, SOLR-2382-solrwriter.patch, SOLR-2382.patch, SOLR-2382.patch,
SOLR-2382.patch, SOLR-2382.patch, SOLR-2382.patch, SOLR-2382.patch, SOLR-2382.patch, SOLR-2382.patch
>
>
> Functionality:
>  1. Provide a pluggable caching framework for DIH so that users can choose a cache implementation that best
(Continue reading)


Gmane