[
https://issues.apache.org/jira/browse/LUCENE-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027570#comment-13027570
]
Simon Willnauer commented on LUCENE-3057:
-
bq. Hi Simon, I think you meant to set
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer reassigned LUCENE-3041:
---
Assignee: Simon Willnauer
> Support Query Visting / Walking
> --
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027575#comment-13027575
]
Simon Willnauer commented on LUCENE-3041:
-
bq.New patch that implements what I sa
[
https://issues.apache.org/jira/browse/LUCENE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3056:
Component/s: Search
Lucene Fields: [New, Patch Available] (was: [New])
A
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3041:
Lucene Fields: [New, Patch Available] (was: [New])
Affects Version/s: 4.0
[
https://issues.apache.org/jira/browse/LUCENE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027578#comment-13027578
]
Simon Willnauer commented on LUCENE-3056:
-
Hey chris,
here are some comments:
*
[
https://issues.apache.org/jira/browse/SOLR-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shinichiro Abe updated SOLR-2480:
-
Attachment: SOLR-2480-idea1.patch
> Text extraction of password protected files
>
[
https://issues.apache.org/jira/browse/SOLR-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027579#comment-13027579
]
Shinichiro Abe commented on SOLR-2480:
--
{quote}
But I think you want Solr to skip the
Revise ThreadAffinityDocumentsWriterThreadPool queue handling
-
Key: LUCENE-3060
URL: https://issues.apache.org/jira/browse/LUCENE-3060
Project: Lucene - Java
Issue Type: Improvemen
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027583#comment-13027583
]
Simon Willnauer commented on LUCENE-3023:
-
bq. In ThreadAffinityDocumentsWriterTh
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027587#comment-13027587
]
Uwe Schindler commented on LUCENE-3023:
---
The first full Jenkins Build also succeede
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027589#comment-13027589
]
Chris Male commented on LUCENE-3041:
bq. Are you going to add the IS changes here too
[
https://issues.apache.org/jira/browse/LUCENE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027592#comment-13027592
]
Chris Male commented on LUCENE-3056:
bq. This change somewhat depends on LUCENE-3041
[
https://issues.apache.org/jira/browse/LUCENE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male updated LUCENE-3056:
---
Attachment: LUCENE-3056.patch
Patch implementing Simon's suggestions
- RewriteState -> RewriteConte
Hi
I wanted to impl my own MergeScheduler (a variation of SerialMergeScheduler,
which does minor additional work), and found out I cannot really, for lack
of visible API on IndexWriter, such as getNextMerge() and merge(OneMerge) --
both exist, but are package-private.
It got me thinking -- how ca
[
https://issues.apache.org/jira/browse/SOLR-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Drozdov updated SOLR-2472:
-
Affects Version/s: 4.0
> StatsComponent should support hierarchical facets
> -
[
https://issues.apache.org/jira/browse/SOLR-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027608#comment-13027608
]
Uwe Schindler commented on SOLR-2392:
-
When reviewing the current builds I can again al
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/7642/
1 tests failed.
REGRESSION: org.apache.lucene.collation.TestCollationKeyAnalyzer.testThreadSafe
Error Message:
Java heap space
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf
I think we should open up these APIs?
And, we should make a test case that lives outside of oal.index, to
assert that in fact all needed APIs are not package private?
Mike
http://blog.mikemccandless.com
On Mon, May 2, 2011 at 5:09 AM, Shai Erera wrote:
> Hi
>
> I wanted to impl my own MergeSch
DIH - an uppercase problem in query parameters
--
Key: SOLR-2483
URL: https://issues.apache.org/jira/browse/SOLR-2483
Project: Solr
Issue Type: Bug
Components: clients - java, contrib - D
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027612#comment-13027612
]
Earwin Burrfoot commented on LUCENE-3041:
-
The static cache is now not threadsafe
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027612#comment-13027612
]
Earwin Burrfoot edited comment on LUCENE-3041 at 5/2/11 10:30 AM:
-
Open IndexWriter API to allow custom MergeScheduler implementation
--
Key: LUCENE-3061
URL: https://issues.apache.org/jira/browse/LUCENE-3061
Project: Lucene - Java
Issue Type:
I slurped this hprof down and opened it w/ YourKit...
Something weird is going on, because there is a single massive (151
MB) string, stack local to one of the threads, filled with character
U+00B2.
The test itself looks innocuous; I don't think it creates any massive
stack local strings.
I'm ba
On Mon, May 2, 2011 at 6:43 AM, Michael McCandless
wrote:
> I slurped this hprof down and opened it w/ YourKit...
>
> Something weird is going on, because there is a single massive (151
> MB) string, stack local to one of the threads, filled with character
> U+00B2.
>
> The test itself looks innoc
[
https://issues.apache.org/jira/browse/LUCENE-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-3061:
---
Attachment: LUCENE-3061.patch
Open up necessary API + add TestCustomMergeScheduler under
src/test/o
[
https://issues.apache.org/jira/browse/LUCENE-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027621#comment-13027621
]
Uwe Schindler commented on LUCENE-3061:
---
All of those the public API tests are dire
[
https://issues.apache.org/jira/browse/LUCENE-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-3061:
---
Attachment: LUCENE-3061.patch
Thanks Uwe ! Following your comment, I noticed there is a
TestMergeSc
[
https://issues.apache.org/jira/browse/LUCENE-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027626#comment-13027626
]
Earwin Burrfoot commented on LUCENE-3061:
-
Mark these as @experimental?
> Open I
[
https://issues.apache.org/jira/browse/LUCENE-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027627#comment-13027627
]
Shai Erera commented on LUCENE-3061:
I don't think they are experimental though -- th
On Mon, May 2, 2011 at 6:43 AM, Michael McCandless
wrote:
> I slurped this hprof down and opened it w/ YourKit...
>
> Something weird is going on, because there is a single massive (151
> MB) string, stack local to one of the threads, filled with character
> U+00B2.
>
> The test itself looks innoc
[
https://issues.apache.org/jira/browse/SOLR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027629#comment-13027629
]
Matthias Pigulla commented on SOLR-42:
--
I don't think it's a duplicate and the issue is
[
https://issues.apache.org/jira/browse/SOLR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027629#comment-13027629
]
Matthias Pigulla edited comment on SOLR-42 at 5/2/11 12:02 PM:
---
First, this kind of question is better suited for the Lucene User's list,
this list is intended for people actively developing the lucene code
itself.
That said, your problem most likely is that you are indexing your
fields "UN_TOKENIZED", which means that the information isn't
split into words. T
[
https://issues.apache.org/jira/browse/LUCENE-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027631#comment-13027631
]
Michael McCandless commented on LUCENE-3061:
I think they should be @experime
[
https://issues.apache.org/jira/browse/LUCENE-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027633#comment-13027633
]
Shai Erera commented on LUCENE-3061:
I didn't notice MS is experimental. It's weird (
Hi
Today, LogMP allows you to set different thresholds for segments sizes,
thereby allowing you to control the largest segment that will be
considered for merge + the largest segment your index will hold (=~
threshold * mergeFactor).
So, if you want to end up w/ say 20GB segments, you can set
max
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027639#comment-13027639
]
Uwe Schindler commented on LUCENE-3054:
---
I investigated what happens here:
The pro
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3054:
--
Priority: Critical (was: Major)
Summary: SorterTemplate.quickSort stack overflows on brok
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027640#comment-13027640
]
Robert Muir commented on LUCENE-3054:
-
{quote}
I propose to change SorterTemplate to
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3054:
--
Attachment: LUCENE-3054-stackoverflow.patch
Patch that shows the issue.
> SorterTemplate.quic
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027643#comment-13027643
]
Uwe Schindler commented on LUCENE-3054:
---
As quicksort gets insanely slow when these
TestBytesRefHash#testCompact is broken
--
Key: LUCENE-3062
URL: https://issues.apache.org/jira/browse/LUCENE-3062
Project: Lucene - Java
Issue Type: Bug
Affects Versions: 4.0
Reporter: Simo
[
https://issues.apache.org/jira/browse/LUCENE-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3062:
Attachment: LUCENE-3062.patch
here is a patch
> TestBytesRefHash#testCompact is broken
>
Have you checked BalancedSegmentMergePolicy? It has some more knobs :)
On Mon, May 2, 2011 at 17:03, Shai Erera wrote:
> Hi
>
> Today, LogMP allows you to set different thresholds for segments sizes,
> thereby allowing you to control the largest segment that will be
> considered for merge + the l
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reassigned LUCENE-3054:
-
Assignee: Uwe Schindler
> SorterTemplate.quickSort stack overflows on broken comparators
I did look at it, but I didn't find that it answers this particular need
(ending with a segment no bigger than X). Perhaps by tweaking several
parameters (e.g. maxLarge/SmallNumSegments + maxMergeSizeMB) I can achieve
something, but it's not very clear what is the right combination.
Which is relat
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027662#comment-13027662
]
Uwe Schindler commented on LUCENE-3054:
---
Due to the realtime merge (LUCENE-3023), s
[
https://issues.apache.org/jira/browse/LUCENE-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera resolved LUCENE-3061.
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [New])
Committed revision 10
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3023:
--
Attachment: LUCENE-3023-quicksort-reincarnation.patch
Here the patch. Will commit soon.
> Lan
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reopened LUCENE-3023:
---
I reopen this one, as the merge added a reincarnation of quicksort in
DocFieldProcessor (which
Dunno, I'm quite happy with numLargeSegments (you critically
misspelled it). It neatly avoids uber-merges, keeps the number of
segments at bay, and does not require to recalculate thresholds when
my expected index size changes.
The problem is - each person needs his own set of knobs (or thinks he
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-3023.
---
Resolution: Fixed
Removed quicksort in revision 1098592
> Land DWPT on trunk
>
>
> The problem is - each person needs his own set of knobs (or thinks he
> needs them) for MergePolicy, and I can't call any of these sets
> superior to others :/
>
I agree. I wonder tough if the knobs we give on LogMP are intuitive enough.
It neatly avoids uber-merges
>
I didn't see that I can
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3054:
--
Attachment: LUCENE-3054.patch
Here the patch that combines Robert's optimization for PhraseQue
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3054:
--
Fix Version/s: 4.0
3.2
3.1.1
Set fix versions (also back
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3054:
--
Attachment: LUCENE-3054.patch
Sorry, the safety net is only needed at 40 (from my tests), befo
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3054:
--
Attachment: LUCENE-3054.patch
Better test that fails faster in case of quickSort bug
> Sorter
Is there any reason not to replace the old mirror with the newly created
one?
- Michael
--
Hi,
On Tue, Apr 26, 2011 at 7:51 PM, Michael Herndon
wrote:
> Would it be possible to get the git mirror to reflect that or at least
> create a
[
https://issues.apache.org/jira/browse/LUCENE-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-3062.
-
Resolution: Fixed
> TestBytesRefHash#testCompact is broken
> ---
Actually the new TieredMergePolicy (only on trunk currently but I plan
to backport for 3.2) lets you set the max merged segment size
(maxMergedSegmentMB).
It's only an "estimate", but if it's set, it tries to pick a merge
reaching around that target size.
Mike
http://blog.mikemccandless.com
On
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3054:
--
Attachment: LUCENE-3054.patch
Final patch.
After some discussion with robert: The use of Quic
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027702#comment-13027702
]
Uwe Schindler commented on LUCENE-3054:
---
Committed trunk revision: 1098633
Now mer
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-3054.
---
Resolution: Fixed
Merged 3.x revision: 1098639
Merged 3.1 revision: 1098641
> SorterTemplat
[
https://issues.apache.org/jira/browse/LUCENE-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3063:
Attachment: LUCENE-3063.patch
> factor CharTokenizer/CharacterUtils into analyzers module
> --
factor CharTokenizer/CharacterUtils into analyzers module
-
Key: LUCENE-3063
URL: https://issues.apache.org/jira/browse/LUCENE-3063
Project: Lucene - Java
Issue Type: Task
R
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reopened LUCENE-3054:
Reopening so we can discuss things further...:
QuickSort is dangerous! Yet, it's def
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027730#comment-13027730
]
Michael McCandless commented on LUCENE-3054:
Also, I think PQ.PostingsAndFreq
I don't think so
> Date: Mon, 2 May 2011 11:18:12 -0400
> From: mhern...@wickedsoftware.net
> To: lucene-net-...@lucene.apache.org
> Subject: [Lucene.Net] fw: resolving github mirror issues
>
> Is there any reason not to replace the old mirror with the newly created
> one?
>
> - Michael
>
Thanks Mike. I'll take a look at TieredMP. Does it depend on trunk in any
way, or do you think it can easily be ported to 3x?
Shai
On Mon, May 2, 2011 at 6:34 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> Actually the new TieredMergePolicy (only on trunk currently but I plan
> to
I think it should be an easy port...
Mike
http://blog.mikemccandless.com
On Mon, May 2, 2011 at 2:16 PM, Shai Erera wrote:
> Thanks Mike. I'll take a look at TieredMP. Does it depend on trunk in any
> way, or do you think it can easily be ported to 3x?
> Shai
>
> On Mon, May 2, 2011 at 6:34 PM,
[
https://issues.apache.org/jira/browse/LUCENE-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027755#comment-13027755
]
Paul Elschot commented on LUCENE-2945:
--
Does the latest patch solve the original pro
Hi Shai and Mike,
Testing the TieredMP on our large indexes has been on my todo list since I read
Mikes blog post
http://blog.mikemccandless.com/2011/02/visualizing-lucenes-segment-merges.html.
If you port it to the 3.x branch Shai, I'll be more than happy to test it with
our very large (300GB+
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027772#comment-13027772
]
Dawid Weiss commented on LUCENE-3054:
-
I'm sure many of you know this, but there is a
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027774#comment-13027774
]
Uwe Schindler commented on LUCENE-3054:
---
Dawid:
There are two problems we have seen
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/7659/
1 tests failed.
REGRESSION: org.apache.solr.client.solrj.TestLBHttpSolrServer.testSimple
Error Message:
expected:<3> but was:<2>
Stack Trace:
junit.framework.AssertionFailedError: expected:<3> but was:<2>
at
o
[
https://issues.apache.org/jira/browse/LUCENE-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-3059.
Resolution: Fixed
> PulsingTermState.clone leaks memory
>
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027780#comment-13027780
]
Dawid Weiss commented on LUCENE-3054:
-
Thanks Uwe, I didn't know about it. Still, the
Thanks for fixing++
Tom
-Original Message-
From: Uwe Schindler [mailto:u...@thetaphi.de]
Sent: Sunday, May 01, 2011 6:05 AM
To: dev@lucene.apache.org; simon.willna...@gmail.com;
java-u...@lucene.apache.org
Subject: RE: Link to nightly build test reports on main Lucene site needs
updati
[
https://issues.apache.org/jira/browse/SOLR-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-2467.
Resolution: Fixed
Fix Version/s: 4.0
3.2
Thanks for reporting this Alex
Committe
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027808#comment-13027808
]
Michael McCandless commented on LUCENE-3054:
So, there are two known improvem
[
https://issues.apache.org/jira/browse/LUCENE-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-3029.
Resolution: Fixed
> MultiPhraseQuery assigns different scores to identical docs wh
[
https://issues.apache.org/jira/browse/SOLR-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-2484:
Attachment: SOLR-2484-SynonymFilterFactory.patch
patch with a simple test
> Make SynonymFilterFacto
Make SynonymFilterFactory more extendable
-
Key: SOLR-2484
URL: https://issues.apache.org/jira/browse/SOLR-2484
Project: Solr
Issue Type: Improvement
Reporter: Ryan McKinley
Pri
[
https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Matheis (steffkes) updated SOLR-2399:
Description:
*The idea was to create a new, fresh (and hopefully clean) Solr
[
https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027846#comment-13027846
]
Stefan Matheis (steffkes) commented on SOLR-2399:
-
Just because i had a qui
[
https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027850#comment-13027850
]
Otis Gospodnetic commented on SOLR-2399:
Thanks for doing all this, Stefan!
I look
Remove BaseResponseWriter, GenericBinaryResponseWriter, and
GenericTextResponseWriter
-
Key: SOLR-2485
URL: https://issues.apache.org/jira/browse/SOLR-2485
Project: S
>> The problem is - each person needs his own set of knobs (or thinks he
>> needs them) for MergePolicy, and I can't call any of these sets
>> superior to others :/
>
> I agree. I wonder tough if the knobs we give on LogMP are intuitive enough.
>
>> It neatly avoids uber-merges
>
> I didn't see tha
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/7666/
All tests passed
Build Log (for compile errors):
[...truncated 7968 lines...]
[javac] required:
org.apache.solr.common.util.NamedList
[javac] NamedList whitetok = fieldNames.get("whitetok");
[javac]
On Apr 27, 2011, at 11:45 PM, Greg Stein wrote:
> On Wed, Apr 27, 2011 at 09:25:14AM -0400, Yonik Seeley wrote:
>> ...
>> But as I said... it seems only fair to meet half way and use the solr
>> namespace
>> for some modules and the lucene namespace for others.
>
> Please explain this part to m
[
https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027878#comment-13027878
]
Ryan McKinley commented on SOLR-2399:
-
Stefan -- this stuff is looking great! Would yo
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/7667/
All tests passed
Build Log (for compile errors):
[...truncated 7958 lines...]
[javac] required:
org.apache.solr.common.util.NamedList
[javac] NamedList whitetok = fieldNames.get("whitetok");
[javac]
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027892#comment-13027892
]
Uwe Schindler commented on LUCENE-3054:
---
{quote}
Maybe we leave our QS as is (excep
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/7668/
All tests passed
Build Log (for compile errors):
[...truncated 7958 lines...]
[javac] required:
org.apache.solr.common.util.NamedList
[javac] NamedList whitetok = fieldNames.get("whitetok");
[javac]
[
https://issues.apache.org/jira/browse/SOLR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027915#comment-13027915
]
Hoss Man commented on SOLR-2191:
Is anyone else interested in entertaining the notion that
[
https://issues.apache.org/jira/browse/LUCENE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3054:
--
Attachment: LUCENE-3054-dynamic.patch
Here a patch which implements what introsort does: if th
[
https://issues.apache.org/jira/browse/SOLR-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027920#comment-13027920
]
Steven Rowe commented on SOLR-2484:
---
Ryan,
[Jenkins|https://builds.apache.org/hudson/job
>
>
> In short, I believe people should still contribute where they see they can
> add the most value and according to their time schedules. Additionally,
> others who have more time or the ability to refactor for reusability should
> be free to do so as well.
>
I agree that people should be able
: It'd be nice if Jira could auto-magically treat Next as whatever
: release really is "next". EG, say we all agree 3.2 is our next
: release, then ideally Jira would treat all Next issues as if they were
: marked with 3.2.
FWIW: you can rename jira versions w/o losing information about what
is
1 - 100 of 121 matches
Mail list logo
