Build: http://hudson.zones.apache.org/hudson/job/Solr-trunk/1289/
All tests passed
Build Log (for compile errors):
[...truncated 16296 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional comman
Build:
http://hudson.zones.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/416/
6 tests failed.
REGRESSION:
org.apache.solr.TestGroupingSearch.testGroupingGroupSortingScore_basic
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
a
Sure, it all would work and would be better than "naive" index UID.
Mapping more UIDs to one permits this compromise "Number of unique terms in
term dict against CPU during update to resolve collisions".
I like Paul's idea with more fields, it reduces number of UIDs in term
dictionary, but
Build:
http://hudson.zones.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/418/
6 tests failed.
REGRESSION:
org.apache.solr.TestGroupingSearch.testGroupingGroupSortingScore_basic
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
a
[
https://issues.apache.org/jira/browse/SOLR-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923808#action_12923808
]
Simon Willnauer commented on SOLR-2160:
---
FYI - I can reliably reproduce with running S
[
https://issues.apache.org/jira/browse/SOLR-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923813#action_12923813
]
Simon Willnauer commented on SOLR-2160:
---
Could we put @Ignore on the SolrInfoMBeanTest
Build:
http://hudson.zones.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/419/
1 tests failed.
REGRESSION: org.apache.solr.TestDistributedSearch.testDistribSearch
Error Message:
Some threads threw uncaught exceptions!
Stack Trace:
junit.framework.AssertionFailedError: Some threads threw un
[
https://issues.apache.org/jira/browse/LUCENE-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923817#action_12923817
]
Veena Channagouda commented on LUCENE-2347:
---
These were the steps I followed to
[
https://issues.apache.org/jira/browse/SOLR-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923813#action_12923813
]
Simon Willnauer edited comment on SOLR-2160 at 10/22/10 6:54 AM:
-
On Fri, 2010-10-22 at 11:23 +0200, eks dev wrote:
> Both of these solutions are just better way to do it wrong :) The real
> solution
> is definitely somewhere around ParallelReader usage.
The problem with parallel is with updates of documents. The IndexWriter
takes terms and queries for deleti
On Oct 21, 2010, at 3:44 PM, eks dev wrote:
> Hi All,
> I am trying to figure out a way to implement following use case with
> lucene/solr.
>
>
> In order to support simple incremental updates (master) I need to index and
> store UID Field on 300Mio collection. (My UID is a 32 byte sequen
Build:
http://hudson.zones.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/425/
6 tests failed.
REGRESSION:
org.apache.solr.TestGroupingSearch.testGroupingGroupSortingScore_basic
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
a
I do not think aeletes are really a problem, there are probably many ways to
fix
that. The problem is to create and keep in sync two(or more) indexes with
parallel docIDs.
For example: use DeleteByQuery and feed it with Filter with set bits on docID
positions?
- Original Message ---
[
https://issues.apache.org/jira/browse/LUCENE-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved LUCENE-2718.
--
Resolution: Fixed
Fix Version/s: 4.0
> separate java code from .jj file
> -
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923866#action_12923866
]
Michael McCandless commented on LUCENE-2618:
OK thanks Shai... I'll commit sho
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2618.
Resolution: Fixed
> Intermittent failure in 3.x's backwards TestThreadedOptimize
>
Thanks Grant,
this sound good.
https://issues.apache.org/jira/browse/LUCENE-1812
and
https://issues.apache.org/jira/browse/LUCENE-2632
I didn't notice them before due to high_volume high_quality traffic here in
lucene world, one cannot keep up :)
Will have to look into it in detail.
With
[
https://issues.apache.org/jira/browse/LUCENE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923867#action_12923867
]
Robert Muir commented on LUCENE-1823:
-
Looking at the patch, its a bit difficult to re
[
https://issues.apache.org/jira/browse/SOLR-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923882#action_12923882
]
Robert Muir commented on SOLR-2160:
---
Thanks for the reproducable case, Simon.
Unfortunate
[
https://issues.apache.org/jira/browse/LUCENE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-996:
Attachment: LUCENE-996.patch
I didn't realize there was already a patch for this!
Anyway, I just im
Provide more DirectoryFactory implementations for the various different
Directories
---
Key: SOLR-2187
URL: https://issues.apache.org/jira/browse/SOLR-2187
Project: Solr
Build:
http://hudson.zones.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/431/
1 tests failed.
REGRESSION:
org.apache.lucene.index.TestBackwardsCompatibility.testUnsupportedOldIndexes
Error Message:
Format version is not supported in file '_0.fdx': 1 (needs to be between 2 and
2). This ve
StandardTokenizerFactory should accept a maxTokenLength parameter
-
Key: SOLR-2188
URL: https://issues.apache.org/jira/browse/SOLR-2188
Project: Solr
Issue Type: Improvement
WTF
Did somebody mixup something in TestBackwards or its zip files? That’s
impossible. Only if the SSDs on lucene.zones are now broken *g*
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Apache Huds
[
https://issues.apache.org/jira/browse/SOLR-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923904#action_12923904
]
Steven Rowe commented on SOLR-2188:
---
ClassicTokenizerFactory should also accept a maxToken
I found the reason for the problem:
try {
writer = new IndexWriter(dir, newIndexWriterConfig(
TEST_VERSION_CURRENT, new MockAnalyzer())
.setMergeScheduler(new SerialMergeScheduler()) // no threads!
);
// TODO: Make IndexWriter fail on open!
On Fri, 22 Oct 2010, Imre András wrote:
Ok, thanks. After resolving this I got the following error:
jcc.cpp(294) : error C2039: 'fromJString' : is not a member of 'JCCEnv'
As I see this method is present in JCCEnv.h, but an #ifdef PYTHON
directive prevents to make it available for the tier co
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reopened LUCENE-2618:
---
This commit sometimes fails TestBackwards because IndexWriter.close() now also
throws IndexForm
[
https://issues.apache.org/jira/browse/SOLR-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-2187:
--
Attachment: SOLR-2187.patch
Provide MMap and SimpleFS DirectoryFactory impls. Didn't include th
[
https://issues.apache.org/jira/browse/SOLR-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923914#action_12923914
]
Robert Muir commented on SOLR-2187:
---
For the MMap one, I think it would be good to at leas
[
https://issues.apache.org/jira/browse/SOLR-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923916#action_12923916
]
Grant Ingersoll commented on SOLR-2073:
---
When I saw the title of this, I was under the
[
https://issues.apache.org/jira/browse/SOLR-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923920#action_12923920
]
Grant Ingersoll commented on SOLR-2075:
---
Chris/William, can you bring this up to date
[
https://issues.apache.org/jira/browse/SOLR-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923925#action_12923925
]
David Smiley commented on SOLR-2155:
Lance, did you look at my patch or just skim the is
[
https://issues.apache.org/jira/browse/SOLR-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923926#action_12923926
]
Chris A. Mattmann commented on SOLR-2075:
-
Note: there was no patch before I stepped
FYI: I started seeing this error when Miller committed SolrCloud to trunk
and included the slf4j log4j bridge jar -- the root cause was that i had
a very old version of log4j in my classpath (as part of a custom ant
install)
: Date: Sat, 16 Oct 2010 05:44:03 -0400
: From: Michael McCandless
[
https://issues.apache.org/jira/browse/SOLR-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923927#action_12923927
]
Chris A. Mattmann commented on SOLR-2073:
-
Great, well if you guys don't find it use
[
https://issues.apache.org/jira/browse/SOLR-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923931#action_12923931
]
Hoss Man commented on SOLR-2178:
bq. I also think we should make /browse the landing page fo
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923946#action_12923946
]
Michael McCandless commented on LUCENE-2618:
Hmm indeed you can repro with
[
https://issues.apache.org/jira/browse/LUCENE-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923949#action_12923949
]
Yonik Seeley commented on LUCENE-2576:
--
{noformat}
[junit] NOTE: reproduce with:
[
https://issues.apache.org/jira/browse/SOLR-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923954#action_12923954
]
Grant Ingersoll commented on SOLR-2187:
---
bq. enable the unmapHack if its supported (MM
[
https://issues.apache.org/jira/browse/SOLR-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923956#action_12923956
]
Robert Muir commented on SOLR-2187:
---
{quote}
What do you think should be the behavior if s
[
https://issues.apache.org/jira/browse/SOLR-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-2187:
--
Attachment: SOLR-2187.patch
Incorporates Muir's feedback.
> Provide more DirectoryFactory imple
[
https://issues.apache.org/jira/browse/SOLR-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923965#action_12923965
]
Robert Muir commented on SOLR-2187:
---
+1, looks like a good idea for 64-bit windows users o
[
https://issues.apache.org/jira/browse/SOLR-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923967#action_12923967
]
Grant Ingersoll commented on SOLR-2187:
---
OK, I will commit and, gasp, merge to 3.x!
>
Build:
http://hudson.zones.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/436/
All tests passed
Build Log (for compile errors):
[...truncated 7468 lines...]
[javac] ^
[javac]
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-tests-only-trunk/checkout/solr/src/java/org
It would be nice if compilation warnings were turned off, so that compilation
*errors* would be shown instead of warnings here (compilation output is
otherwise useless) ...
> -Original Message-
> From: Apache Hudson Server [mailto:hud...@hudson.apache.org]
> Sent: Friday, October 22, 201
We want to get rid of the warnings... So we display them that everybody sees
them on each compilation is solr!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Steven A Rowe [mailto:sar...@syr.edu]
> Sen
On Fri, Oct 22, 2010 at 3:02 PM, Steven A Rowe wrote:
> It would be nice if compilation warnings were turned off, so that compilation
> *errors* would be shown instead of warnings here (compilation output is
> otherwise useless) ...
>
Personally I don't think the warnings are useless, they poin
[
https://issues.apache.org/jira/browse/SOLR-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmet Arslan updated SOLR-1604:
---
Attachment: ComplexPhrase.zip
There is a need for un-ordered proximity search.
http://search-lucene.c
I agree that compilation warnings are not useless. In general, anyway.
But for the case of an email alerting the dev list to a broken compile, the
email should point out what's breaking the compile. The warnings are useless
in this context (i.e., telling us what broke the build).
On 10/22/201
Build:
http://hudson.zones.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/437/
All tests passed
Build Log (for compile errors):
[...truncated 7464 lines...]
[javac] ^
[javac]
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-tests-only-trunk/checkout/solr/src/java/org
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2618:
---
Attachment: LUCENE-2618.patch
> Intermittent failure in 3.x's backwards TestThreaded
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923987#action_12923987
]
Michael McCandless commented on LUCENE-2618:
OK so I think we should fix this
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923989#action_12923989
]
Shai Erera commented on LUCENE-2618:
Does this mean I'll need to catch that exception
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923995#action_12923995
]
Michael McCandless commented on LUCENE-2618:
bq. Does this mean I'll need to c
[
https://issues.apache.org/jira/browse/LUCENE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923998#action_12923998
]
Yonik Seeley commented on LUCENE-996:
-
OK, here's the full patch.
Rather than try to ma
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924002#action_12924002
]
Shai Erera commented on LUCENE-2618:
I see. It's just that you describe this exception
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924008#action_12924008
]
Michael McCandless commented on LUCENE-2618:
I think there's a separate issue
[
https://issues.apache.org/jira/browse/LUCENE-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924006#action_12924006
]
Michael McCandless commented on LUCENE-2618:
bq. If my app knowingly opened a
[
https://issues.apache.org/jira/browse/LUCENE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved LUCENE-996.
-
Resolution: Fixed
Committed.
> Parsing mixed inclusive/exclusive range queries
> --
[
https://issues.apache.org/jira/browse/SOLR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-355.
---
Resolution: Fixed
Fix Version/s: 4.0
Resolved as part of LUCENE-996
> Parsing mixed inclusive/e
QP can't represent a literal * in range
---
Key: SOLR-2189
URL: https://issues.apache.org/jira/browse/SOLR-2189
Project: Solr
Issue Type: Bug
Components: search
Reporter: Yonik Seeley
[
https://issues.apache.org/jira/browse/LUCENE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley reassigned LUCENE-995:
---
Assignee: Yonik Seeley (was: Luis Alves)
> Add open ended range query syntax to QueryParser
[
https://issues.apache.org/jira/browse/LUCENE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924041#action_12924041
]
Yonik Seeley commented on LUCENE-995:
-
FYI, this last patch has the same issue as Solr
Re-add SorterTemplate and use it to provide fast ArraySorting and replace
BytesRefHash sorting
--
Key: LUCENE-2719
URL: https://issues.apache.org/jira/browse/LUCENE-2719
[
https://issues.apache.org/jira/browse/LUCENE-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2719:
--
Attachment: LUCENE-2719.patch
Attached you find the patch. Robert offered to do benchmarks wit
[
https://issues.apache.org/jira/browse/LUCENE-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924051#action_12924051
]
Uwe Schindler commented on LUCENE-2719:
---
Using this class we can look for more usele
[
https://issues.apache.org/jira/browse/LUCENE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-995:
Attachment: LUCENE-995.patch
Here's a draft patch (no tests yet, so I don't know if it works).
But
[
https://issues.apache.org/jira/browse/LUCENE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-995:
Attachment: LUCENE-995.patch
OK, here's the final patch - adds a few tests and changes
TermRangeQu
[
https://issues.apache.org/jira/browse/LUCENE-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924068#action_12924068
]
Yonik Seeley commented on LUCENE-2719:
--
bq. This also applies to Solr (Yonik?).
Yep
[
https://issues.apache.org/jira/browse/LUCENE-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2719:
--
Attachment: LUCENE-2719.patch
The quickSort in DocFieldProcessorPerThread also converted to
A
Build: http://hudson.zones.apache.org/hudson/job/Lucene-3.x/158/
All tests passed
Build Log (for compile errors):
[...truncated 21249 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional command
[
https://issues.apache.org/jira/browse/SOLR-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924098#action_12924098
]
Lance Norskog commented on SOLR-2155:
-
I've reread the patch a few times and I understan
[
https://issues.apache.org/jira/browse/SOLR-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924098#action_12924098
]
Lance Norskog edited comment on SOLR-2155 at 10/22/10 8:32 PM:
---
Build: http://hudson.zones.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/435/
1 tests failed.
REGRESSION: org.apache.lucene.search.TestThreadSafe.testLazyLoadThreadSafety
Error Message:
unable to create new native thread
Stack Trace:
java.lang.OutOfMemoryError: unable to create new native th
Build: http://hudson.zones.apache.org/hudson/job/Solr-3.x/144/
All tests passed
Build Log (for compile errors):
[...truncated 16556 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands,
76 matches
Mail list logo
