[
https://issues.apache.org/jira/browse/SOLR-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543516
]
Henri Biestro commented on SOLR-414:
org.apache.solr.util.plugin.DeprecatedPluginUtils seems to be missing from
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sabyasachi Dalal updated SOLR-303:
--
Attachment: fedsearch.patch
I have updated the patch to remove the code pertaining to SOLR-281,
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543553
]
Sabyasachi Dalal commented on SOLR-303:
---
I mean i removed the files pertaining to 281. If you follow the
[
https://issues.apache.org/jira/browse/SOLR-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-414:
---
Attachment: SOLR-414-Initialization.patch
sorry - I uploaded the wrong one
Coherent plugin
Definitely a simpler more practical route - it avoids all previously
inelegant lately unorthodox pitfalls :-)
The only thing that this leaves behind is solr-399; I guess it's ok, we can
revive this after 1.3.
I've got a 414 + 350 + 409 working but I don't know where to upload it.
Should we
Henrib wrote:
Definitely a simpler more practical route - it avoids all previously
inelegant lately unorthodox pitfalls :-)
The only thing that this leaves behind is solr-399; I guess it's ok, we can
revive this after 1.3.
Yes, this leaves behind the 399 post core initialization callback.
[
https://issues.apache.org/jira/browse/SOLR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-413.
---
Resolution: Fixed
committed
Cap offset + limit to maxDoc()
--
Yes, I'm ok with it, please do.
ryantxu wrote:
...
If you feel ok with 414, I will commit it.
...
--
View this message in context:
http://www.nabble.com/Initializing---break-init%28%29-API-compatibility--tf4808463.html#a13839870
Sent from the Solr - Dev mailing list archive at
Hey guys, i'm *WAY* behind on my email, ironicly due to going mostly off
the grid while at a apachecon -- but the first thing i'm trying to do is
get caught up with what's going on here.
if i can sum up my understanding (and please correct me if i'm wrong, this
is based purely on email and
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543693
]
Hoss Man commented on SOLR-409:
---
as i mentioned on the mailing list a while back, it's not clear to me how
multicore
[
https://issues.apache.org/jira/browse/SOLR-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-327:
--
Component/s: replication
shell scripts failed to run on Solaris 8 (and probably other non recent UNIX)
Hey
Is there a reason that QueryParsing.SortSpec has private constructors?
It's preventing me from having a custom sort parser for the
ResponseBuilder
without a patch for solr.
Thanks
P
--
Patrick O'Leary
You see, wire telegraph is a kind of a very, very long cat. You pull his tail in New
On Nov 19, 2007 9:01 PM, patrick o'leary [EMAIL PROTECTED] wrote:
Is there a reason that QueryParsing.SortSpec has private constructors?
It's preventing me from having a custom sort parser for the ResponseBuilder
without a patch for solr.
Hmmm, no reason I see.
Unless there are objections,
: Hmmm, no reason I see.
: Unless there are objections, I'll make them public.
-0 ... i'd much rather see us deprecate it and make it go away entirely.
it's an archaic throwback to the days when every option was going to
be encoded into the q param instead of having sort rows and start
(ie:
...Did i get that all right?
wow! you are good!
The one key point you did not mention is that the ThreadLocal approach
is proposed as a stop-gap measure until we have an API breaking release.
In the 2.0 release, the init() method signature will change and the
ThreadLocal hack will go
On Nov 19, 2007 10:26 PM, Chris Hostetter [EMAIL PROTECTED] wrote:
Last time i looked at most usages, the getOffset() and getCount() were
totally ignored
Not any more... see QueryComponent.process():
results.docList = searcher.getDocList(
builder.getQuery(),
I don't see an issue with retaining it, as long as it's got public
constructors.
The difference between
responseBuilder.setSort(customSort); // if you deprecate SortSpec.
and
responseBuilder.setSortSpec (new QueryParser.SortSpec(customSort, -1));
isn't going to kill anyone.
P
Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543774
]
Yonik Seeley commented on SOLR-303:
---
I'm really just starting to dig into this again, but here are a couple of
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543787
]
Ryan McKinley commented on SOLR-409:
Yes #1, not #2
{code:xml}
multicore enabled=true adminpath=/admin/multicore
19 matches
Mail list logo
