[
https://issues.apache.org/jira/browse/LUCENENET-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-424:
---
Attachment: TestIsolatedStorageDirectory.cs
Test cases for IsolatedStorageDirectory.
(Doesn't
[
https://issues.apache.org/jira/browse/LUCENENET-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047089#comment-13047089
]
Digy commented on LUCENENET-423:
Maybe I am missing something,
but I run your code both
For that many unique values I would recommend to take a look at References
to adding faceted to Lucene.Net section in that wiki page.
Using BitSets(as in contrib) is good for large number of search results(say
millions) with small # of facets(say 1000-4000).
Using Collector approach is good when
[
https://issues.apache.org/jira/browse/SOLR-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047047#comment-13047047
]
Dawid Weiss commented on SOLR-1804:
---
I am not considering changes to my code to be a
[
https://issues.apache.org/jira/browse/SOLR-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Gambier resolved SOLR-2529.
--
Resolution: Fixed
Fix Version/s: 4.0
I've made some test on unreleased version 4.0 and
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/8743/
2 tests failed.
REGRESSION: org.apache.lucene.index.TestIndexReaderReopen.testThreadSafety
Error Message:
Error occurred in thread Thread-122:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/8748/
No tests ran.
Build Log (for compile errors):
[...truncated 4186 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional
The class from cotrub directory org.apache.lucene.index.IndexSplitter creates a
non correct index
-
Key: LUCENE-3188
URL:
[
https://issues.apache.org/jira/browse/LUCENE-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Dimitrov Vasilev updated LUCENE-3188:
--
Attachment: IndexSplitter.java
TestIndexSplitter.java
The
TestIndexWriter.testThreadInterruptDeadlock failed (can't reproduce)
Key: LUCENE-3189
URL: https://issues.apache.org/jira/browse/LUCENE-3189
Project: Lucene - Java
Issue
[
https://issues.apache.org/jira/browse/LUCENE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-152:
Attachment: LUCENE-152_optimization.patch
very minor optimization to avoid a char[] allocation per
Build: https://builds.apache.org/job/Lucene-Solr-Maven-3.x/148/
No tests ran.
Build Log (for compile errors):
[...truncated 8340 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands,
[
https://issues.apache.org/jira/browse/LUCENE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-152:
---
Attachment: LUCENE-152_alt.patch
why create strings either?
[PATCH] KStem for Lucene
[
https://issues.apache.org/jira/browse/SOLR-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047160#comment-13047160
]
Simon Willnauer commented on SOLR-1431:
---
I think this patch looks good, mark I think
[
https://issues.apache.org/jira/browse/SOLR-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-1431:
-
Assignee: Mark Miller (was: Noble Paul)
CommComponent abstracted
[
https://issues.apache.org/jira/browse/SOLR-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1431:
--
Fix Version/s: 4.0
CommComponent abstracted
Key: SOLR-1431
Build:
https://builds.apache.org/job/Lucene-Solr-tests-only-docvalues-branch/1260/
2 tests failed.
REGRESSION: org.apache.lucene.index.TestIndexReaderReopen.testThreadSafety
Error Message:
Error occurred in thread Thread-175:
[
https://issues.apache.org/jira/browse/LUCENE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-152:
Attachment: LUCENE-152_optimization.patch
bq. why create strings either?
Good point. I assume
[
https://issues.apache.org/jira/browse/LUCENE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047171#comment-13047171
]
Yonik Seeley commented on LUCENE-152:
-
bq. i think its the same as the patch i
[
https://issues.apache.org/jira/browse/LUCENE-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-3108.
-
Resolution: Fixed
Reintegrated, Tested, Committed to trunk in revision 1134311
thanks
[
https://issues.apache.org/jira/browse/SOLR-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047177#comment-13047177
]
Mark Miller commented on SOLR-1431:
---
I've got to look a little closer here - there was a
[
https://issues.apache.org/jira/browse/LUCENENET-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047179#comment-13047179
]
Digy commented on LUCENENET-423:
You are right, I used a different date string.
.Net
[
https://issues.apache.org/jira/browse/SOLR-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047185#comment-13047185
]
Mark Miller commented on SOLR-1431:
---
So my bad - looks like this patch is for 3.x - need
[
https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047208#comment-13047208
]
Simon Willnauer commented on LUCENE-2878:
-
it doesn't seem that this issue is
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/145/
No tests ran.
Build Log (for compile errors):
[...truncated 7512 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands,
[
https://issues.apache.org/jira/browse/SOLR-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated SOLR-2582:
-
Priority: Minor (was: Major)
Fix Version/s: 4.0
Assignee: Koji Sekiguchi
[
https://issues.apache.org/jira/browse/SOLR-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated SOLR-2582:
-
Attachment: SOLR-2582.patch
Use uniqueKey for error log in UIMAUpdateRequestProcessor
[
https://issues.apache.org/jira/browse/LUCENE-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker updated LUCENE-2793:
--
Attachment: LUCENE-2793.patch
I had messed up the patch using eclipse. This should be ok.
[
https://issues.apache.org/jira/browse/LUCENE-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047234#comment-13047234
]
Simon Willnauer commented on LUCENE-2793:
-
Varun, your patch doesn't apply
[
https://issues.apache.org/jira/browse/LUCENE-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047245#comment-13047245
]
Steven Rowe commented on LUCENE-3188:
-
This is a better Wikipedia article on (source
On Fri, Jun 10, 2011 at 12:04 PM, Jason Rutherglen
jason.rutherg...@gmail.com wrote:
Maybe we should bring back the 'merge results' part of multi searcher
without the query rewrite.
and how exactly? If this was easy, we wouldn't have to do
https://issues.apache.org/jira/browse/LUCENE-2837
I
As I previously tried to explain, I have custom query for some pre-cached
terms, which I load into RAM in efficient compressed form. I need this for
faster searching and also for much faster faceting. So what I do is process
incoming query and replace certain sub-queries with my own
On Fri, Jun 10, 2011 at 12:18 PM, Jason Rutherglen
jason.rutherg...@gmail.com wrote:
I think we only need to resurrect the merge score/field-docs code, in
it's own class. Eg, each sub-node is expected to create it's own
score/field-docs, then the merge code is centralized.
Maybe we should
Simon can you also email java-user@ and solr-user@? Seems good to
over-communicate when trunk index format changes...
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jun 10, 2011 at 10:01 AM, Simon Willnauer
simon.willna...@googlemail.com wrote:
Hey folks,
I just committed
[
https://issues.apache.org/jira/browse/LUCENE-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Dimitrov Vasilev updated LUCENE-3188:
--
Attachment: LUCENE-3188.patch
The file LUCENE-3188.patch contains the needed
[
https://issues.apache.org/jira/browse/SOLR-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047275#comment-13047275
]
Jason Rutherglen commented on SOLR-1431:
I just downloaded
Have you tried to use Lucene.Net as is, before working on optimizing your
code? There are a lot of speed improvements in it since 1.9.
There is also a Faceted Search project in contrib.
(https://cwiki.apache.org/confluence/display/LUCENENET/Simple+Faceted+Search
)
DIGY
-Original
[
https://issues.apache.org/jira/browse/LUCENE-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047279#comment-13047279
]
Ivan Dimitrov Vasilev commented on LUCENE-3188:
---
Hi Steve,
I attached the
Ok sounds good. Grouping is an interesting distrib case.
On Fri, Jun 10, 2011 at 9:27 AM, Michael McCandless
luc...@mikemccandless.com wrote:
I'm actually working on something like this, basically a utility
method to merge N TopDocs into 1. I want to do this for grouping as
well to make it
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047291#comment-13047291
]
Uwe Schindler commented on LUCENE-1768:
---
Hi Vinicius,
if you want the code be
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047315#comment-13047315
]
Uwe Schindler commented on LUCENE-1768:
---
One small thing I have seen after applying
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047315#comment-13047315
]
Uwe Schindler edited comment on LUCENE-1768 at 6/10/11 5:48 PM:
Out of curiosity, how is DF handled with the new automaton [regex] queries?
On Fri, Jun 10, 2011 at 10:48 AM, Andrzej Bialecki a...@getopt.org wrote:
On 6/10/11 6:27 PM, Michael McCandless wrote:
I'm actually working on something like this, basically a utility
method to merge N TopDocs into
On Fri, Jun 10, 2011 at 6:22 PM, Michael McCandless
luc...@mikemccandless.com wrote:
Simon can you also email java-user@ and solr-user@? Seems good to
over-communicate when trunk index format changes...
good point, done!
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jun 10,
On 6/10/11 7:51 PM, Jason Rutherglen wrote:
Out of curiosity, how is DF handled with the new automaton [regex] queries?
Automaton is eventually resolved into a list of terms, and the IDF for
each term is obtained in the usual way.
--
Best regards,
Andrzej Bialecki
___. ___ ___ ___ _ _
Hi Jason,
Standard MTQ queries have no scoring at all (using ConstantScoreRewrite by
default). Exception is FuzzyQuery which has two modes: One using standard
BQ TermQuery scoring multiplied with factor calculated from levensthein
distance and another one with all TermQueries made constant score
[
https://issues.apache.org/jira/browse/SOLR-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2564:
---
Priority: Blocker (was: Major)
Marking this issue as a blocker for Solr 4.0 per McCandless comment in
[
https://issues.apache.org/jira/browse/LUCENE-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047354#comment-13047354
]
Steven Rowe commented on LUCENE-3188:
-
{quote}
I attached the patch to this issue as
No I will try it though. Thanks.
Bob
On Jun 10, 2011, at 12:37 PM, Digy wrote:
Have you tried to use Lucene.Net as is, before working on optimizing your
code? There are a lot of speed improvements in it since 1.9.
There is also a Faceted Search project in contrib.
TestStressIndexing2 testMultiConfig failure
---
Key: LUCENE-3190
URL: https://issues.apache.org/jira/browse/LUCENE-3190
Project: Lucene - Java
Issue Type: Bug
Reporter: selckin
trunk:
Add a parameter in UIMAUpdateRequestProcessor to avoid duplicated values on
insert
--
Key: SOLR-2584
URL: https://issues.apache.org/jira/browse/SOLR-2584
Project: Solr
Hi, guys,
FYI: Here is the link to how to build and start Apache Solr admin app from
source with Maven just in case you might be interested:
http://thetechietutorials.blogspot.com/2011/06/how-to-build-and-start-apache-solr.html
Have fun.
YH
[
https://issues.apache.org/jira/browse/SOLR-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-2535:
---
Attachment: SOLR-2535_fix_admin_file_handler_for_directory_listings.patch
The attached patch fixes
Add TopDocs.merge to merge multiple TopDocs
---
Key: LUCENE-3191
URL: https://issues.apache.org/jira/browse/LUCENE-3191
Project: Lucene - Java
Issue Type: Improvement
Reporter: Michael
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3191:
---
Attachment: LUCENE-3191.patch
Patch.
The basic idea is simple (use PQ to find top
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-3191:
--
Assignee: Michael McCandless
Add TopDocs.merge to merge multiple TopDocs
On Fri, Jun 10, 2011 at 1:48 PM, Andrzej Bialecki a...@getopt.org wrote:
On 6/10/11 6:27 PM, Michael McCandless wrote:
I'm actually working on something like this, basically a utility
method to merge N TopDocs into 1. I want to do this for grouping as
well to make it easy to do grouping
[
https://issues.apache.org/jira/browse/LUCENE-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047408#comment-13047408
]
Simon Willnauer commented on LUCENE-3190:
-
I will dig!
TestStressIndexing2
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047416#comment-13047416
]
Uwe Schindler commented on LUCENE-3191:
---
bq. The basic idea is simple (use PQ to
[
https://issues.apache.org/jira/browse/SOLR-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047420#comment-13047420
]
David Smiley commented on SOLR-2535:
The relayout of import statements in
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047440#comment-13047440
]
Michael McCandless commented on LUCENE-3191:
Uwe, you are right! Now why
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047472#comment-13047472
]
Michael McCandless commented on LUCENE-3191:
So... I started down this path
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047477#comment-13047477
]
Uwe Schindler commented on LUCENE-3191:
---
This still confuses me:
bq. There might
[
https://issues.apache.org/jira/browse/SOLR-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047478#comment-13047478
]
Michael McCandless commented on SOLR-2564:
--
Hmm, I think this only needs to be a
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047479#comment-13047479
]
Uwe Schindler commented on LUCENE-3191:
---
By the way, in current trunk the value()
Context-Sensitive Spelling Suggestions Collations
---
Key: SOLR-2585
URL: https://issues.apache.org/jira/browse/SOLR-2585
Project: Solr
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/SOLR-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-2585:
-
Attachment: SOLR-2585.patch
Context-Sensitive Spelling Suggestions Collations
We have still a problem with queries that rewrite depending on index
contents - which was the reason for MTQ's deMorgan bug. If two
MultiTermQueries rewrite to different queries on two shards, the scores are
also not comparable, even with normalized idf. This does not affect
WildCardCo (because
On Fri, Jun 10, 2011 at 6:06 PM, Uwe Schindler u...@thetaphi.de wrote:
We have still a problem with queries that rewrite depending on index
contents - which was the reason for MTQ's deMorgan bug. If two
MultiTermQueries rewrite to different queries on two shards, the scores are
also not
Really? because I see your description of the situation as mixing two totally
different things:
They are connected because they follow each other.
1. a situation where a distributed case returns scores different than a single
node case. Who cares? This should be up to the user to make the
On Fri, Jun 10, 2011 at 6:49 PM, Uwe Schindler u...@thetaphi.de wrote:
Really? because I see your description of the situation as mixing two totally
different things:
They are connected because they follow each other.
1. a situation where a distributed case returns scores different than a
About the merging; when I look at Mikes code:
Except the global IDF and the bug in MTQ, the merging code is identical to
what MultiSearcher did before. I would in trunk even recommend to
undelete FieldDocSortedHitQueue and you have everything you need to
merge two TopDocs instances.
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047748#comment-13047748
]
Uwe Schindler commented on LUCENE-3191:
---
We had some discussions about cleaning
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3191:
---
Attachment: LUCENE-3191.patch
New patch:
* Changes .value from Comparator (which
Build: https://builds.apache.org/job/Lucene-3.x/401/
No tests ran.
Build Log (for compile errors):
[...truncated 9153 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
On Fri, Jun 10, 2011 at 7:08 PM, Uwe Schindler u...@thetaphi.de wrote:
And I still tend to undelete FieldDocSortedHitQueue as it merged TopDocs and
LUCENE-3191 will get a very small patch. :-)
just please don't resurrect any Collators here in trunk!
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3191:
---
Attachment: LUCENE-3191.patch
New patch, adds default impl for FC.compareValues to
[
https://issues.apache.org/jira/browse/LUCENE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047781#comment-13047781
]
Uwe Schindler commented on LUCENE-3191:
---
Looks fine, I am happy now :-)
The
[
https://issues.apache.org/jira/browse/SOLR-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047793#comment-13047793
]
Koji Sekiguchi commented on SOLR-2584:
--
Or we can implement the function in the new
On Fri, Jun 10, 2011 at 8:45 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: We could compile under 1.6 and have a jenkins (ant) target to check
: binary 1.5 compatibility -- bytecode versions and std. API calls. This
: way we could use 1.6, @Override annotations, etc. and still ensure
: I agree with you completely (a rare occasion, i know!). I think it
I don't think it's that rare -- i suspect we agree 80% of the time, but
don't notice due to silent concenses.
: This is why hudson is complicated.
right .. no complaint from me, just explaining why we have a nightly
target
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/8775/
All tests passed
Build Log (for compile errors):
[...truncated 15394 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional
On Fri, Jun 10, 2011 at 9:31 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
Buf for bug fixes we really need to deal with this in a better way. We
need to track *every* bug fix made on a branch, even if they were
backported to an earlier branch.
I think we have?
bugfixes are the only
Build: https://builds.apache.org/job/Lucene-trunk/1588/
No tests ran.
Build Log (for compile errors):
[...truncated 8001 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/8772/
4 tests failed.
REGRESSION: org.apache.lucene.index.TestIndexReader.testFilesOpenClose
Error Message:
[
https://issues.apache.org/jira/browse/LUCENE-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3188:
Attachment: LUCENE-3188.patch
Patch against branch_3x.
I converted Ivan's test class into a unit
[
https://issues.apache.org/jira/browse/LUCENE-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3188:
Fix Version/s: (was: 3.2)
(was: 3.0)
4.0
[
https://issues.apache.org/jira/browse/SOLR-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley closed SOLR-1232.
--
Resolution: Fixed
This was fixed long ago with the /spell request handler.
Add spellchecker example
example work logs directories needed?
---
Key: SOLR-2586
URL: https://issues.apache.org/jira/browse/SOLR-2586
Project: Solr
Issue Type: Improvement
Components: Build
Reporter: David
89 matches
Mail list logo