Build: https://hudson.apache.org/hudson/job/Solr-3.x/184/
All tests passed
Build Log (for compile errors):
[...truncated 18941 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-ma
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2078/
1 tests failed.
REGRESSION: org.apache.solr.TestDistributedSearch.testDistribSearch
Error Message:
Some threads threw uncaught exceptions!
Stack Trace:
junit.framework.AssertionFailedError: Some threads threw uncaugh
Hello,
I am using CachedSqlEntityProcessor for one of my entities and it working
fine when I am loading the cache as keys are requested, however it doesn't
work when I try to pre load the cache. My configuration for "loading the
cache as keys are requested" is:
When I change it to the following
[
https://issues.apache.org/jira/browse/SOLR-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965913#action_12965913
]
Shawn Heisey commented on SOLR-1143:
I tried this patch, then we put SOLR-1537 into prod
[
https://issues.apache.org/jira/browse/SOLR-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965891#action_12965891
]
Gary Yngve commented on SOLR-1143:
--
This issue has been superceded by
https://issues.apach
I agree with Robert that minimizing analysis <-> indexer interface is
the way to go.
For me, one of Lucene's problems is that it wants to do too much stuff
out of the box, and is tightly coupled, so you can't drop much of the
things you never need.
Having minimal interface for the indexer allows u
On Wed, Dec 1, 2010 at 3:44 PM, Grant Ingersoll wrote:
>> Well i have trouble with a few of your examples: "want to use
>> Tee/Sink" doesn't work for me... its a description of an XY problem to
>> me... i've never needed to use it, and its rarely discussed on the
>> user list...
>
> Shrugs. In m
[
https://issues.apache.org/jira/browse/SOLR-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965841#action_12965841
]
Peter Karich commented on SOLR-1709:
Hi Peter,
sorry for getting so late back.
I'm rel
[
https://issues.apache.org/jira/browse/LUCENE-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2788:
Attachment: LUCENE-2788.patch
here's a very quick patch (all tests pass):
* Changed CharFilter to
On Dec 1, 2010, at 2:40 PM, Robert Muir wrote:
> On Wed, Dec 1, 2010 at 2:25 PM, Grant Ingersoll wrote:
>>
>> Nah, I just meant analysis would often benefit from having knowledge of the
>> document as a whole instead of just the individual field.
>>
>
> and analysis would suffer from this to
Make CharFilter reusable
Key: LUCENE-2788
URL: https://issues.apache.org/jira/browse/LUCENE-2788
Project: Lucene - Java
Issue Type: Improvement
Components: Analysis
Reporter: Robert Muir
To remove your address from the list, send a message to:
On Dec 1, 2010, at 2:40 PM, asmcad wrote:
> how can i leave this group? i couldn't find the site.
>
> thanks
Wade Girard
wade.gir...@gmail.com
On Wed, Dec 1, 2010 at 2:25 PM, Grant Ingersoll wrote:
>
> Nah, I just meant analysis would often benefit from having knowledge of the
> document as a whole instead of just the individual field.
>
and analysis would suffer from this too, because right now these
things are independent and we have
how can i leave this group? i couldn't find the site.
thanks
On Dec 1, 2010, at 8:07 AM, Robert Muir wrote:
> On Wed, Dec 1, 2010 at 8:01 AM, Grant Ingersoll wrote:
>
>> While we are at it, how about we make the Analysis process document aware
>> instead of Field aware? The PerFieldAnalyzerWrapper, while doing exactly
>> what it says it does, is just
[
https://issues.apache.org/jira/browse/LUCENE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965752#action_12965752
]
Simon Willnauer commented on LUCENE-2787:
-
after all i think we should really do i
So, going forward...
When committing an issue that needs a changes entry, where are we
supposed to put it?
EG if it's a bug fix that we'll backport all the way to 2.9.x... where
does it go?
If it's a new feature/API that's going to 3.x and trunk... only in
3.x's CHANGES?
Mike
On Wed, Dec 1, 20
[
https://issues.apache.org/jira/browse/LUCENENET-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965741#action_12965741
]
Hans commented on LUCENENET-384:
You'll have to get the sources from SVN and compile you
[
https://issues.apache.org/jira/browse/LUCENE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965740#action_12965740
]
Michael McCandless commented on LUCENE-2787:
+1, this is a no brainer. I had
[
https://issues.apache.org/jira/browse/LUCENE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera resolved LUCENE-2779.
Resolution: Fixed
Committed revision 1041019 (3x).
Committed revision 1041039 (trunk).
Thanks all
[
https://issues.apache.org/jira/browse/LUCENE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965705#action_12965705
]
Robert Muir commented on LUCENE-2787:
-
Uwe: I don't interpret it that way!
I don't th
While I'm not against going back towards a checkout backwards that we can
modify, I wonder if all the tests there should be there and how much do we
actually duplicate.
Lucene 3x should include all of 3.0 tests + new ones that test new
functionality, or assert bug fixes etc. There shouldn't be a t
[
https://issues.apache.org/jira/browse/LUCENE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965700#action_12965700
]
Robert Muir commented on LUCENE-2787:
-
Also simon, i just wanted to say, you need to b
[
https://issues.apache.org/jira/browse/LUCENE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965701#action_12965701
]
Uwe Schindler commented on LUCENE-2787:
---
bq. The option exists specifically for apps
[
https://issues.apache.org/jira/browse/LUCENE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965697#action_12965697
]
Robert Muir commented on LUCENE-2787:
-
Simon, of course you can, but why not set it? O
[
https://issues.apache.org/jira/browse/LUCENE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965695#action_12965695
]
Simon Willnauer commented on LUCENE-2787:
-
robert, you can also control this throu
Hi all,
when merging changes done in 2.9.4/3.0.3 with current 3.x and trunk I found
out that 3.x changes differ immense between the trunk changes.txt and the
3.x changes.txt. Some entries are missing in the 3.x branch, but are
available in trunk's 3.x part or other entries using new trunk class na
[
https://issues.apache.org/jira/browse/LUCENE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2787:
Attachment: LUCENE-2787.patch
all core tests pass with this directory.
> disable atime for Direct
disable atime for DirectIOLinuxDirectory
Key: LUCENE-2787
URL: https://issues.apache.org/jira/browse/LUCENE-2787
Project: Lucene - Java
Issue Type: Improvement
Components: contrib/*
syntax error in shell script "abo"
--
Key: SOLR-2260
URL: https://issues.apache.org/jira/browse/SOLR-2260
Project: Solr
Issue Type: Sub-task
Affects Versions: 1.4.1, 1.4
Reporter: Thomas Koch
On Wed, Dec 1, 2010 at 8:01 AM, Grant Ingersoll wrote:
> While we are at it, how about we make the Analysis process document aware
> instead of Field aware? The PerFieldAnalyzerWrapper, while doing exactly
> what it says it does, is just silly. If you had an analysis process that was
> aware
On Nov 29, 2010, at 5:34 AM, Robert Muir wrote:
> On Mon, Nov 29, 2010 at 2:50 AM, Earwin Burrfoot wrote:
>> And for indexes:
>> * Index compatibility is guaranteed across two adjacent major
>> releases. eg 2.x -> 3.x, 3.x -> 4.x.
>> That includes both binary compat - codecs, and semantic compa
We have a Board Report due this month. I will setup the placeholder in SVN.
We have two things we must address beyond the usual:
1. The Trademark stuff. I will take the lead on this.
2. Per the conversation on Lucene.NET's status, we expect a full report from
the .NET community in regards to th
[
https://issues.apache.org/jira/browse/SOLR-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965675#action_12965675
]
Robert Muir commented on SOLR-2259:
---
I committed the patch for part 1 to trunk in revision
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2055/
1 tests failed.
REGRESSION: org.apache.solr.TestDistributedSearch.testDistribSearch
Error Message:
Some threads threw uncaught exceptions!
Stack Trace:
junit.framework.AssertionFailedError: Some threads threw uncaugh
[
https://issues.apache.org/jira/browse/LUCENE-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-2786.
-
Resolution: Not A Problem
lowercasefilter is there for non-arabic text, for consistency with oth
[
https://issues.apache.org/jira/browse/LUCENE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male updated LUCENE-2599:
---
Attachment: LUCENE-2599.patch
Attaching a patch that includes the creation of a new spatial module.
Is it possible to remove the QueryNorm??
so all the bf boost became an add of the solr score??
omitNorm is about fieldNorm or queryNorm??
thanx
--
Gastone Penzo
[
https://issues.apache.org/jira/browse/LUCENE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male updated LUCENE-2599:
---
Attachment: LUCENE-2599.patch
Attached patch for deprecating the contrib. Each class is deprecated,
[
https://issues.apache.org/jira/browse/LUCENE-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1737.
Resolution: Fixed
Fix Version/s: 3.1
> Always use bulk-copy when merging st
[
https://issues.apache.org/jira/browse/LUCENE-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2785.
Resolution: Fixed
> TopFieldCollector throws AIOOBE if numHits is 0
>
[
https://issues.apache.org/jira/browse/LUCENE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965649#action_12965649
]
Chris Male commented on LUCENE-2599:
On it.
> Deprecate Spatial Contrib
> ---
[
https://issues.apache.org/jira/browse/LUCENE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965648#action_12965648
]
Simon Willnauer commented on LUCENE-2599:
-
chris, wanna come up with a patch again
[
https://issues.apache.org/jira/browse/LUCENE-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965646#action_12965646
]
Chris Male commented on LUCENE-2139:
See LUCENE-2599 (which I'd opened up awhile back
[
https://issues.apache.org/jira/browse/LUCENE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male updated LUCENE-2599:
---
Description:
The spatial contrib is blighted by bugs. The latest series, found by Grant and
discus
[
https://issues.apache.org/jira/browse/LUCENE-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male closed LUCENE-1732.
--
Resolution: Won't Fix
Assignee: Chris Male
Closing along with LUCENE-2139
> Multi-threaded Spat
[
https://issues.apache.org/jira/browse/LUCENE-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male closed LUCENE-2151.
--
Resolution: Won't Fix
Assignee: Chris Male (was: Simon Willnauer)
Closing along with LUCENE-213
[
https://issues.apache.org/jira/browse/LUCENE-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male closed LUCENE-2149.
--
Resolution: Won't Fix
Assignee: Chris Male (was: Simon Willnauer)
Closing along with LUCENE-213
[
https://issues.apache.org/jira/browse/LUCENE-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male closed LUCENE-2148.
--
Resolution: Won't Fix
Assignee: Chris Male (was: Simon Willnauer)
Closing along with LUCENE-213
[
https://issues.apache.org/jira/browse/LUCENE-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male closed LUCENE-2152.
--
Resolution: Won't Fix
Assignee: Chris Male
Closing along with LUCENE-2139
> Abstract Spatial di
[
https://issues.apache.org/jira/browse/LUCENE-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male closed LUCENE-2174.
--
Resolution: Won't Fix
Assignee: Chris Male (was: Simon Willnauer)
Closing along with LUCENE-213
[
https://issues.apache.org/jira/browse/LUCENE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male closed LUCENE-2173.
--
Resolution: Won't Fix
Assignee: Chris Male (was: Simon Willnauer)
Closing along with LUCENE-213
[
https://issues.apache.org/jira/browse/LUCENE-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male closed LUCENE-2175.
--
Resolution: Won't Fix
Assignee: Chris Male
Closing along with LUCENE-2139.
> Deprecate remainin
[
https://issues.apache.org/jira/browse/LUCENE-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male closed LUCENE-2139.
--
Resolution: Won't Fix
Assignee: Chris Male (was: Simon Willnauer)
Closing as we will look into
[
https://issues.apache.org/jira/browse/LUCENE-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965635#action_12965635
]
Chris Male commented on LUCENE-2139:
I have to echo Simon's comments here. Furthermor
[
https://issues.apache.org/jira/browse/LUCENE-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965631#action_12965631
]
Simon Willnauer commented on LUCENE-2139:
-
bq. Pity to remove code before replacin
[
https://issues.apache.org/jira/browse/LUCENE-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965621#action_12965621
]
Nicolas Helleringer commented on LUCENE-2139:
-
bq. Yep - but they are normally
Build: https://hudson.apache.org/hudson/job/Solr-trunk/1329/
All tests passed
Build Log (for compile errors):
[...truncated 18570 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e
[
https://issues.apache.org/jira/browse/SOLR-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965603#action_12965603
]
Shimon Shrem commented on SOLR-1913:
I worked this out.
I mistakenly used on old schema.
59 matches
Mail list logo