[
https://issues.apache.org/jira/browse/SOLR-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872898#action_12872898
]
Chris Harris commented on SOLR-937:
---
I haven't taken the time to reproduce this particular
I see that Robert committed a fix for that, gonna try the package target
now.
On Fri, May 28, 2010 at 3:00 PM, Shai Erera ser...@gmail.com wrote:
Tracing this back, I see that Robert removed everything related to 'demo'
from /build.xml to contrib/demo/build.xml, except for this part. Thing is,
sorry about this, i caused it by moving demo to a contrib module.
as a contrib module all this special logic is no longer necessary, it
uses the logic in contrib-build to build its artifacts, javadocs, etc.
but somehow i missed this stuff.
additionally javacc target should work, for some reason
it works for me now. Thanks !
Shai
On Fri, May 28, 2010 at 3:15 PM, Robert Muir rcm...@gmail.com wrote:
sorry about this, i caused it by moving demo to a contrib module.
as a contrib module all this special logic is no longer necessary, it
uses the logic in contrib-build to build its
[
https://issues.apache.org/jira/browse/LUCENE-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872945#action_12872945
]
Shai Erera commented on LUCENE-2481:
If there are not comments/objections, I'd like to
Hmm... so I think the questions really are how many merges are
allowed to run concurrently? (SMS is 1 and CMS is N), and do I spawn
my own threads for merging or do I steal the app's threads (SMS
steals app threads and CMS spawns new ones).
Of course if you steal app threads you can only make use
We just need an Executor-based MS, then we can throw all other out of
the window, as threading concerns are now resolved by a proper choice
of Executor supplied to constructor.
Also an application has much more control over threading in
multiple-index situations, as single Executor can be reused
[
https://issues.apache.org/jira/browse/LUCENE-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873004#action_12873004
]
Michael McCandless commented on LUCENE-2481:
This looks nice Shai!
So now you
[
https://issues.apache.org/jira/browse/LUCENE-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873030#action_12873030
]
Yonik Seeley commented on LUCENE-2458:
--
{quote}
True, but I thought there was
[
https://issues.apache.org/jira/browse/LUCENE-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873034#action_12873034
]
Yonik Seeley commented on LUCENE-2458:
--
bq. In this case, too, you could override the
[
https://issues.apache.org/jira/browse/LUCENE-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873035#action_12873035
]
Robert Muir commented on LUCENE-2458:
-
ok i revised the idea here:
in 3.1 we supply a
The word executor helped me nail down my thoughts (thanks Earwin). I
think we should decouple MS into MergeExecutor and MergeScheduler.
ME would control how merges are done: serial, parallel, queue-based
(control the level of parallelism) etc.
MS would schedule the merges (perhaps a different
When loading FieldCache terms index, make terms data optional
-
Key: LUCENE-2483
URL: https://issues.apache.org/jira/browse/LUCENE-2483
Project: Lucene - Java
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2468.
Fix Version/s: 3.1
4.0
Resolution: Fixed
reopen on NRT
I remember thinking several months back, when some Jira fix caught my eye,
Man, that's a heinous bug, we should really put out a 1.4.1 bug fix
release for that once it's committed. Then i evidently got distracted,
and there was a lot going on with the trunk merge, and then the 3x branch
[
https://issues.apache.org/jira/browse/SOLR-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-1915.
Fix Version/s: 4.0
Resolution: Fixed
Committed revision 949318.
people can try this out on the
[
https://issues.apache.org/jira/browse/SOLR-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873190#action_12873190
]
Yonik Seeley commented on SOLR-1915:
On a quick try, I think I like the old behavior as
Schema Browser does not scale with large indexes
Key: SOLR-1931
URL: https://issues.apache.org/jira/browse/SOLR-1931
Project: Solr
Issue Type: Improvement
Components: web gui
On Fri, May 28, 2010 at 6:23 PM, Chris Hostetter
hossman_luc...@fucit.orgwrote:
I remember thinking several months back, when some Jira fix caught my eye,
Man, that's a heinous bug, we should really put out a 1.4.1 bug fix release
for that once it's committed. Then i evidently got
[
https://issues.apache.org/jira/browse/SOLR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873197#action_12873197
]
Yonik Seeley commented on SOLR-1931:
This is correctly marked as Improvement, but I
[
https://issues.apache.org/jira/browse/SOLR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873200#action_12873200
]
Lance Norskog commented on SOLR-1931:
-
The UI should change to a drill-down UI that
[
https://issues.apache.org/jira/browse/SOLR-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reopened SOLR-1915:
bq Having firefox not show the linebreaks unless you press CTRL-U (or
cut-n-paste it) also has it's
add relevancy function queries
--
Key: SOLR-1932
URL: https://issues.apache.org/jira/browse/SOLR-1932
Project: Solr
Issue Type: New Feature
Reporter: Yonik Seeley
Priority: Minor
: I would suggest that if there is 1.4.1, that it use lucene 2.9.2 jars also.
: some bugfixes there too.
+1 ... good call ... i think it may have actually been the a bug fix in
the 2.9.2 release that i was initially thinking of.
-Hoss
[
https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873205#action_12873205
]
Lance Norskog commented on SOLR-1163:
-
A deployment suggestion: since the
Should I explicitly say I meant java.util.concurrent.Executor? :)
serial, parallel, queue-based, ride-the-caller-thread - all these
decisions could be made by existing framework, and there's no need to
invent something.
So what we /do/ need is an entity that decides on which merges are
needed at
[
https://issues.apache.org/jira/browse/SOLR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873224#action_12873224
]
Hoss Man commented on SOLR-1931:
Anything with numTerms !=0 is likely to be slow, and the
[
https://issues.apache.org/jira/browse/SOLR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873225#action_12873225
]
Lance Norskog commented on SOLR-1931:
-
bq. ...that's really weird. i havn't looked at
See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/1202/changes
Changes:
[mikemccand] LUCENE-2468: strengthen javadocs
[mikemccand] LUCENE-2468: make CachingWrapperFilter treatment of new deletes
customizable
[mikemccand] remove unnecessary final modifiers
[rmuir] fix contrib/demo's
: Subject: Build failed in Hudson: Lucene-trunk #1202
I don't fully understand it, but there still seems to be a failure related
to the demo -- the path is convoluted, benchmark evidently depends on
demo, but demo can't be built? ...
BUILD FAILED
: ...hmmm it seems to only happen when clover is enabled ... i bet it
: doesn't like that the demo contrib doens't have any tests. I'm trying to
: reproduce now (needed to re-install clover and re-remember how to use it)
I can't seem to reproduce this error locally even though i'm also using
Yes I got it that you were referring to the Java Executor :).
I disagree about time limiting MS. It may not be useful in many cases,
true. But I have a scenario in which machines are used to perform all
sorts of tasks and the are windows in which I'm allowed to do 'heavy
operations'.
It's true I
32 matches
Mail list logo
