Hi all,
I'm new to the pylucene-dev list, so please forgive me if I'm stepping out
of line in the voting process.
We're using sucesfully JCC 2.15 to generate a wrapper for our Java API. JCC
2.16 from SVN HEAD produces the following error (output log attached) when
using the new --use_full_names
On May 12, 2013, at 21:04, Barry Wark ba...@physion.us wrote:
Hi all,
I'm new to the pylucene-dev list, so please forgive me if I'm stepping out of
line in the voting process.
We're using sucesfully JCC 2.15 to generate a wrapper for our Java API. JCC
2.16 from SVN HEAD produces the
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Windows/2780/
Java: 64bit/jdk1.6.0_45 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
5 tests failed.
FAILED:
org.apache.solr.client.solrj.embedded.TestEmbeddedSolrServer.testGetCoreContainer
Error Message:
Stack Trace:
[
https://issues.apache.org/jira/browse/LUCENE-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655478#comment-13655478
]
John Wang commented on LUCENE-4992:
---
makes senses, agreed.
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/5615/
Java: 64bit/jdk1.7.0_21 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
REGRESSION: org.apache.solr.request.TestRemoteStreaming.testQtUpdateFails
Error Message:
IOException occured when talking to server at:
[
https://issues.apache.org/jira/browse/LUCENE-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655522#comment-13655522
]
Robert Muir commented on LUCENE-4583:
-
{quote}
Are you also against just fixing the
[
https://issues.apache.org/jira/browse/LUCENE-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655525#comment-13655525
]
Jack Krupansky commented on LUCENE-4583:
bq. abusing docvalues as stored fields
[
https://issues.apache.org/jira/browse/LUCENE-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655526#comment-13655526
]
Michael McCandless commented on LUCENE-4583:
{quote}
I'm worried about a few
[
https://issues.apache.org/jira/browse/LUCENE-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655529#comment-13655529
]
Michael McCandless commented on LUCENE-4583:
bq. I have to admit that I still
[
https://issues.apache.org/jira/browse/LUCENE-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-4975:
---
Attachment: LUCENE-4975.patch
New patch changes how handlers work:
* Beasting found a seed which
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/5619/
Java: 64bit/jdk1.7.0_21 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
REGRESSION:
org.apache.lucene.search.grouping.AllGroupHeadsCollectorTest.testBasic
Error Message:
[
https://issues.apache.org/jira/browse/LUCENE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655545#comment-13655545
]
l0co commented on LUCENE-3422:
--
I have the similar problems in 3.1.0, likewise here and
Hi
Over at LUCENE-4975 (Replicator) I use InfoStream.getDefault() for logging
messages. That uses the static InfoStream, which means it affects all
replicator instances in the same JVM.
I remember that one of the reasons to not using Logger is because of its
static nature, i.e. once you turn on
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/462/
Java: 64bit/jdk1.7.0 -XX:-UseCompressedOops -XX:+UseG1GC
All tests passed
Build Log:
[...truncated 9178 lines...]
[junit4:junit4] ERROR: JVM J0 ended with an exception, command line:
[
https://issues.apache.org/jira/browse/SOLR-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-3038:
---
Attachment: SOLR-3038-abstract-writer.patch
The extremely simple fix for this is to simply change one
Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/324/
2 tests failed.
REGRESSION: org.apache.solr.cloud.ShardSplitTest.testDistribSearch
Error Message:
Wrong doc count on shard1_1 expected:142 but was:141
Stack Trace:
java.lang.AssertionError: Wrong doc count on shard1_1 expected:142
OnI think that in general the code that initializes ignoreAfterMaxFailures
should take tests.iters into account?
I.e. what's the point of running a test with maxfailures=5 or failfast=true
without iters?
I looked at the code. The thing is one of these options (failfast?) is
I think a legacy
Dawid Weiss created LUCENE-4997:
---
Summary: TestReproduceMessage fails when tests.failfast is set to
true.
Key: LUCENE-4997
URL: https://issues.apache.org/jira/browse/LUCENE-4997
Project: Lucene - Core
Thanks Dawid. It's not critical to change this setting and i don't want to
override it by default when running tests, only if I use tests.iters.
While we could make LTC default maxFailures to 1 if tests.iters are 1, I
don't think that it's worth it. I'll just type -Dtests.failfast=true.
Anyway,
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/2813/
Java: 64bit/jdk1.7.0_21 -XX:-UseCompressedOops -XX:+UseSerialGC
5 tests failed.
FAILED:
org.apache.solr.client.solrj.embedded.TestEmbeddedSolrServer.testGetCoreContainer
Error Message:
Stack Trace:
While we could make LTC default maxFailures to 1 if tests.iters are 1, I
don't think that it's worth it. I'll just type -Dtests.failfast=true.
The default isn't without a reason -- when you run with tests.iters
with a fixed (method) seed and have multiple failures (but different
from the
Thanks Dawid!
Shai
On Sun, May 12, 2013 at 10:03 PM, Dawid Weiss
dawid.we...@cs.put.poznan.plwrote:
While we could make LTC default maxFailures to 1 if tests.iters are 1, I
don't think that it's worth it. I'll just type -Dtests.failfast=true.
The default isn't without a reason -- when
[
https://issues.apache.org/jira/browse/SOLR-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-3038:
---
Attachment: SOLR-3038-abstract-writer.patch
Earlier patch was incomplete - forgot an svn add.
I do not think the real problem gets solved by fixing it here, this is just one
particular instance of the problem and it will pop up somewhere else. If you
have a lot of threads, or you have very high thread churn, gc()/oom is going to
hurt with or without this patch, just slightly later. It
[
https://issues.apache.org/jira/browse/LUCENE-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-4997:
Summary: Internal test framework's tests are sensitive to previous test
failures and
[
https://issues.apache.org/jira/browse/LUCENE-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655621#comment-13655621
]
Commit Tag Bot commented on LUCENE-4997:
[trunk commit] dweiss
[
https://issues.apache.org/jira/browse/LUCENE-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655623#comment-13655623
]
Commit Tag Bot commented on LUCENE-4997:
[branch_4x commit] dweiss
[
https://issues.apache.org/jira/browse/LUCENE-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss resolved LUCENE-4997.
-
Resolution: Fixed
Internal test framework's tests are sensitive to previous test failures
[
https://issues.apache.org/jira/browse/LUCENE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655626#comment-13655626
]
Michael McCandless commented on LUCENE-3422:
An ongoing merge won't remove
[
https://issues.apache.org/jira/browse/LUCENE-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-4901:
Attachment: LUCENE-4901.patch
I've removed the vendor-check assumption entirely and call
[
https://issues.apache.org/jira/browse/LUCENE-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-4901:
Summary: TestIndexWriterOnJRECrash should work on any JRE vendor via
Runtime.halt() (was: Unit
[
https://issues.apache.org/jira/browse/LUCENE-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-4901:
Fix Version/s: (was: 4.2)
4.4
5.0
Unit test
[
https://issues.apache.org/jira/browse/LUCENE-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-4901:
Affects Version/s: (was: 4.2)
Unit test TestIndexWriterOnJRECrash does not support IBM
Shawn Heisey created SOLR-4811:
--
Summary: cleanup - commonsHttpSolrServer - httpSolrServer
Key: SOLR-4811
URL: https://issues.apache.org/jira/browse/SOLR-4811
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/SOLR-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-4811:
---
Attachment: SOLR-4811.patch
Attached patch.
cleanup - commonsHttpSolrServer -
[
https://issues.apache.org/jira/browse/LUCENE-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-4975:
---
Attachment: LUCENE-4975.patch
Patch adds instance InfoStream members instead of relying on the
[
https://issues.apache.org/jira/browse/LUCENE-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sivan Yogev updated LUCENE-4258:
Attachment: LUCENE-4258.branch.4.patch
1. Removed some assertions which were based on assumptions
[
https://issues.apache.org/jira/browse/SOLR-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655641#comment-13655641
]
Commit Tag Bot commented on SOLR-4785:
--
[trunk commit] janhoy
[
https://issues.apache.org/jira/browse/SOLR-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655646#comment-13655646
]
Commit Tag Bot commented on SOLR-4785:
--
[branch_4x commit] janhoy
[
https://issues.apache.org/jira/browse/SOLR-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl resolved SOLR-4785.
---
Resolution: Fixed
New MaxScoreQParserPlugin
-
Key:
[
https://issues.apache.org/jira/browse/LUCENE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655651#comment-13655651
]
l0co commented on LUCENE-3422:
--
Sure, this can happen because of other reasons (might be a
[
https://issues.apache.org/jira/browse/LUCENE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655651#comment-13655651
]
l0co edited comment on LUCENE-3422 at 5/12/13 10:09 PM:
Sure,
[
https://issues.apache.org/jira/browse/SOLR-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655657#comment-13655657
]
Jan Høydahl commented on SOLR-4785:
---
Also added the new parser to the list in
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/848/
1 tests failed.
FAILED:
org.apache.solr.search.QueryEqualityTest.org.apache.solr.search.QueryEqualityTest
Error Message:
testParserCoverage was run w/o any other method explicitly testing qparser:
maxscore
Stack Trace:
[
https://issues.apache.org/jira/browse/LUCENE-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Berryman updated LUCENE-4922:
--
Attachment: HilbertConverter.zip
This is a Java example of converting from a set of x,y
[
https://issues.apache.org/jira/browse/LUCENE-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655668#comment-13655668
]
John Berryman commented on LUCENE-4922:
---
I just attached code called
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/5625/
Java: 64bit/jdk1.7.0_21 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.search.QueryEqualityTest
Error Message:
testParserCoverage was run w/o any other method explicitly
[
https://issues.apache.org/jira/browse/SOLR-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-3038:
---
Attachment: SOLR-3038-abstract-writer.patch
Updated patch to fix some test failures. I am seeing
[
https://issues.apache.org/jira/browse/SOLR-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer updated SOLR-3763:
--
Attachment: SOLR-3763-Make-solr-use-lucene-filters-directly.patch
Version that has a basic (but
Hi,
I discovered that the doc redirect still redirects to 4_1_0 javadocs.
I changed .htaccess so it now points to 4_3_0
https://svn.apache.org/repos/asf/lucene/cms/trunk/content/.htaccess
The Release TODO should mention updating this link -
http://wiki.apache.org/lucene-java/ReleaseTodo
--
Build: https://builds.apache.org/job/Lucene-Solr-Tests-4.x-Java6/1606/
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.search.QueryEqualityTest
Error Message:
testParserCoverage was run w/o any other method explicitly testing qparser:
maxscore
Stack Trace:
[
https://issues.apache.org/jira/browse/SOLR-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer updated SOLR-3763:
--
Fix Version/s: 5.0
Make solr use lucene filters directly
-
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/5564/
Java: 32bit/jdk1.6.0_45 -client -XX:+UseParallelGC
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.search.QueryEqualityTest
Error Message:
testParserCoverage was run w/o any other method explicitly testing
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/5626/
Java: 64bit/jdk1.8.0-ea-b86 -XX:-UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.search.QueryEqualityTest
Error Message:
testParserCoverage was run w/o any other method
[
https://issues.apache.org/jira/browse/SOLR-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reopened SOLR-4785:
---
This one seems to be causing a test fail.
New MaxScoreQParserPlugin
[
https://issues.apache.org/jira/browse/SOLR-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655696#comment-13655696
]
Commit Tag Bot commented on SOLR-4234:
--
[trunk commit] markrmiller
[
https://issues.apache.org/jira/browse/SOLR-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655697#comment-13655697
]
Commit Tag Bot commented on SOLR-4234:
--
[branch_4x commit] markrmiller
[
https://issues.apache.org/jira/browse/SOLR-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-4796:
-
Assignee: Mark Miller
zkcli.sh should honor JAVA_HOME
---
[
https://issues.apache.org/jira/browse/SOLR-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4796:
--
Fix Version/s: 5.0
zkcli.sh should honor JAVA_HOME
---
[
https://issues.apache.org/jira/browse/SOLR-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655702#comment-13655702
]
Mark Miller commented on SOLR-4796:
---
I've tested this - seems to work as expected with or
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/5565/
Java: 32bit/jdk1.7.0_21 -client -XX:+UseParallelGC
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.search.QueryEqualityTest
Error Message:
testParserCoverage was run w/o any other method explicitly testing
[
https://issues.apache.org/jira/browse/SOLR-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer updated SOLR-4785:
--
Attachment: SOLR-4785-Add-tests-for-maxscore-to-QueryEqualityTest.patch
This bit me while I was
[
https://issues.apache.org/jira/browse/SOLR-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer updated SOLR-3763:
--
Attachment: SOLR-3763-Make-solr-use-lucene-filters-directly.patch
Trunk moves really quickly these
[
https://issues.apache.org/jira/browse/SOLR-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655723#comment-13655723
]
Nguyen Manh Tien commented on SOLR-4690:
Could you post your response?
[
https://issues.apache.org/jira/browse/SOLR-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655723#comment-13655723
]
Nguyen Manh Tien edited comment on SOLR-4690 at 5/13/13 2:48 AM:
[
https://issues.apache.org/jira/browse/LUCENE-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer updated LUCENE-1560:
Labels: dead (was: )
maxDocBytesToAnalyze should be required arg up front
[
https://issues.apache.org/jira/browse/LUCENE-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer updated LUCENE-1743:
Labels: dead (was: )
MMapDirectory should only mmap large files, small files should be
Nguyen Manh Tien created SOLR-4812:
--
Summary: Edismax highlighting query doesn't work.
Key: SOLR-4812
URL: https://issues.apache.org/jira/browse/SOLR-4812
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nguyen Manh Tien updated SOLR-4812:
---
Attachment: SOLR-4812.patch
Here is a patch
Edismax highlighting query
[
https://issues.apache.org/jira/browse/SOLR-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nguyen Manh Tien updated SOLR-4812:
---
Description:
edismax highlighting query hl.q={!edismax qf=title v=Software}
function
[
https://issues.apache.org/jira/browse/LUCENE-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655732#comment-13655732
]
Commit Tag Bot commented on LUCENE-2713:
[trunk commit] gbowyer
[
https://issues.apache.org/jira/browse/LUCENE-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer resolved LUCENE-2713.
-
Resolution: Fixed
Fix Version/s: (was: 4.4)
5.0
I beat on this
[
https://issues.apache.org/jira/browse/SOLR-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated SOLR-4812:
---
Description:
When hl.q is an edismax query, Highligting will ignore the query specified in
[
https://issues.apache.org/jira/browse/SOLR-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated SOLR-4812:
---
Affects Version/s: 4.2
4.3
Edismax highlighting query doesn't
[
https://issues.apache.org/jira/browse/LUCENE-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer closed LUCENE-1890.
---
Resolution: Cannot Reproduce
Assignee: Greg Bowyer
I am going to be bold and make the
Shingo Sasaki created SOLR-4813:
---
Summary: Unavoidable IllegalArgumentException occurs when
SynonymFilterFactory's setting has tokenizer's parameter.
Key: SOLR-4813
URL:
[
https://issues.apache.org/jira/browse/LUCENE-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655743#comment-13655743
]
Greg Bowyer commented on LUCENE-2540:
-
Outside of batch adding fields it looks like
[
https://issues.apache.org/jira/browse/SOLR-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655749#comment-13655749
]
Jack Krupansky commented on SOLR-4813:
--
The problem is not that you have a
[
https://issues.apache.org/jira/browse/SOLR-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-3038:
---
Attachment: SOLR-3038-abstract-writer.patch
I took a closer look at the tests and fiddled things
[
https://issues.apache.org/jira/browse/SOLR-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655772#comment-13655772
]
Shingo Sasaki commented on SOLR-4813:
-
Hi, Jack. Thank you for your comment.
Do you
80 matches
Mail list logo
