[
https://issues.apache.org/jira/browse/SOLR-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562215#action_12562215
]
Ryan McKinley commented on SOLR-457:
It is there so that multicore reload/swap/etc
Yonik Seeley wrote:
On Jan 23, 2008 3:02 PM, Ryan McKinley (JIRA) <[EMAIL PROTECTED]> wrote:
Even if we are the only implementation, how do you add functions after a
release? Is it just that the standard compatibility rules would not apply?
I *think* that a client using an older int
[
https://issues.apache.org/jira/browse/SOLR-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561802#action_12561802
]
Ryan McKinley commented on SOLR-436:
Even if we are the only implementation, how do
[
https://issues.apache.org/jira/browse/SOLR-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-436.
Resolution: Fixed
> Make SolrServer an abstract superclass rather then an interf
[
https://issues.apache.org/jira/browse/SOLR-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-436:
--
Assignee: Ryan McKinley
> Make SolrServer an abstract superclass rather then an interf
[
https://issues.apache.org/jira/browse/SOLR-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-436:
---
Attachment: SOLR-436-AbstractSolrj.patch
moves BaseSolrServer to the SolrServer implementaion
> M
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-350:
---
Attachment: solr-350.patch
Looking good. I took your patch and removed all the 'default'
Mike Klaas wrote:
On 14-Jan-08, at 1:48 AM, [EMAIL PROTECTED] wrote:
[junit] Running org.apache.solr.update.AutoCommitTest
[junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 9.735 sec
[junit] Test org.apache.solr.update.AutoCommitTest FAILED
Does anyone else find it odd
[
https://issues.apache.org/jira/browse/SOLR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561067#action_12561067
]
Ryan McKinley commented on SOLR-462:
I totally agree with why you would not want to
try the 'rows' parameter:
http://wiki.apache.org/solr/CommonQueryParameters#head-da5370813ade4b2fc8aa5037b3fcd5562ef0179e
nithyavembu wrote:
Hi All,
I am facing some problem in retrieving records during solr search.
I have a data base which contains more than 1 lakh records.
When i sear
[
https://issues.apache.org/jira/browse/SOLR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-462.
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Ryan McKinley
Wow! this is great. I
[
https://issues.apache.org/jira/browse/SOLR-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560448#action_12560448
]
Ryan McKinley commented on SOLR-459:
I'm glad its working for you. To be clear
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560234#action_12560234
]
Ryan McKinley commented on SOLR-350:
Hi Henri-
We're getting there
[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560228#action_12560228
]
Ryan McKinley commented on SOLR-418:
Thanks for looking at this - and fixing it up
[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-418.
Resolution: Fixed
Assignee: Ryan McKinley
> Editorial Query Boosting Compon
I have seen it, but it always went away with a clean checkout. I was
able to reproduce it, and then can make it stay away by adding
deleteByQuery( "*:*" ) -- see:
http://svn.apache.org/viewvc?rev=613056&view=rev
If you see it pop up, holler.
ryan
Yonik Seeley wrote:
I'm getting an intermi
You will either want to do something with a custom RequestHandler, or
plug into the UpdateRequestProcessor framework
http://wiki.apache.org/solr/UpdateRequestProcessor
On the search/retrieval side, you will probably want to implement a
SearchComponent to fill in the stored fields:
http://wik
Did adding a request handler to /update fix your issue?
I added some docs to:
http://wiki.apache.org/solr/Solrj
And a warning message to the deprecated SolrUpdateServlet:
http://svn.apache.org/viewvc?view=rev&revision=612896
ryan
Keene, David wrote:
Running under tomcat 5.5.23
Sending the
et which calls XmlUpdateRequestHandler.doLegacyUpdate,
which calls XmlUpdateRequestHandler.processUpdate .. processUpdate
does
not check the queryString for a commit, only the POSTed xml. Has this
functionality been turned off in trunk?
-Original Message-
From: Ryan McKinley [mailto:[EMA
lr.update.processor.LogUpdateProcessor finish
INFO: {add=[ABC123-KNEW1_CN-0001]} 0 6
Jan 15, 2008 3:42:12 PM
org.apache.solr.update.processor.LogUpdateProcessor finish
INFO: {add=[QAQA12-QAQA1_CN-0001]} 0 5
-Original Message-
From: Ryan McKinley [mailto:[EMA
[
https://issues.apache.org/jira/browse/SOLR-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559282#action_12559282
]
Ryan McKinley commented on SOLR-457:
Is this something that is only used in
org.apache.solr.update.processor.LogUpdateProcessor finish
INFO: {add=[QAQA12-QAQA1_CN-0001]} 0 7
That is what you get when you call:
client.add( docs )
but what do you see when you call:
client.commit()?
It seems to me that if a user does option 1: client.add(docs) they
oolean
overwrite ) throws SolrServerException, IOException {
UpdateRequest req = new UpdateRequest();
req.add(docs);
req.setOverwrite(overwrite);
return req.process(this);
}
So there is no way to get at the action of that request.
-Original Message-
From: Ryan McKinley
-----
From: Ryan McKinley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 15, 2008 12:54 PM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch to COMMIT with xml
Are you hitting a 1.2 solr index? Using ?commit=true assumes you are
hitting a 1.3 index...
The reason for it is so you can opti
Are you hitting a 1.2 solr index? Using ?commit=true assumes you are
hitting a 1.3 index...
The reason for it is so you can optionally add docs and commit in one call.
ryan
Keene, David wrote:
Hey guys,
I'm not sure why, but the solrj client relies on commit=true on the
querystring for
[
https://issues.apache.org/jira/browse/SOLR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557887#action_12557887
]
Ryan McKinley commented on SOLR-446:
good catch Hoss!
Looking at it again, the &#
[
https://issues.apache.org/jira/browse/SOLR-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-19:
--
Attachment: pom.xml
here is a pom that works, but is not how we should have things...
It stuffs
[
https://issues.apache.org/jira/browse/SOLR-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557375#action_12557375
]
Ryan McKinley commented on SOLR-453:
so what error do you actually see? Does the re
[
https://issues.apache.org/jira/browse/SOLR-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557343#action_12557343
]
Ryan McKinley commented on SOLR-453:
but response.setStatus(int sc, java.lang.Strin
[
https://issues.apache.org/jira/browse/SOLR-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-453:
--
Assignee: Ryan McKinley
> Solr may send invalid HTTP error responses on excepti
[
https://issues.apache.org/jira/browse/SOLR-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-434.
Resolution: Fixed
Assignee: Ryan McKinley
> interfaces should support >2
[
https://issues.apache.org/jira/browse/SOLR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-446.
Resolution: Fixed
Assignee: Ryan McKinley
> TextResponseWriter should be able to work w
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557017#action_12557017
]
Ryan McKinley commented on SOLR-303:
yonik, if you say "go", I&#
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556732#action_12556732
]
Ryan McKinley commented on SOLR-236:
Charles - try applying Doug Steigerwald'
[
https://issues.apache.org/jira/browse/SOLR-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-434:
---
Attachment: SOLR-434-LongDocCount.patch
switches solrj + SolrDocumentList representation from int
check rev 608613
added the file back and am using log.warning() for messages (not System.out)
Chris Hostetter wrote:
: Is raw-schema.jsp in use? It isn't (nor has it been) linked to anything. The
: schema/config links used to point to get-file.jsp
once upon a time it was used by the schema
x27;t think a deprecation warning is necessary (it's not really part
of the "interface" of Solr).
-Mike
On 2-Jan-08, at 9:14 AM, Ryan McKinley wrote:
Hello-
Is raw-schema.jsp in use? It isn't (nor has it been) linked to
anything. The schema/config links used to point to
[
https://issues.apache.org/jira/browse/SOLR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-142.
Resolution: Fixed
Fix Version/s: 1.3
> RawResponseWriter - replace /admin/get-file.
Hello-
Is raw-schema.jsp in use? It isn't (nor has it been) linked to
anything. The schema/config links used to point to get-file.jsp
Should we remove it? Add a deprecation warning?
ryan
[
https://issues.apache.org/jira/browse/SOLR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-142:
--
Assignee: Ryan McKinley
> RawResponseWriter - replace /admin/get-file.
[
https://issues.apache.org/jira/browse/SOLR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-142:
---
Attachment: SOLR-142-RawResponseWriter.patch
Updated so that SOLR-447 AdminHandler automatically
[
https://issues.apache.org/jira/browse/SOLR-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-447.
Resolution: Fixed
> Register standard AdminHandlers automatica
* I wouldn't be in favor of changing the build to rely on Maven2. We
use Maven internally at Krugle, and sometimes it works well, and other
times it's a royal pain in the butt. So having it as an option would
be nice, and handy for me personally, but I'd hate to foist Maven on
everybody els
[
https://issues.apache.org/jira/browse/SOLR-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554928
]
Ryan McKinley commented on SOLR-434:
>
>> I think we can safely change all integers to long withou
Mike Klaas wrote:
On 27-Dec-07, at 5:26 PM, Ryan McKinley wrote:
Seems like that would be the best solution. Me (and, I think, many
others), would be unlikely to used the multiple core functionality of
Solr at all. Avoiding lengthening the log messages in this case
would be nice.
check
[
https://issues.apache.org/jira/browse/SOLR-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-447:
---
Attachment: SOLR-447-AdminHandlers.patch
I realized this last patch does not include the added file
[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-418:
---
Attachment: SOLR-418-QueryBoosting.patch
Thanks Koji -- here is an updated patch
#1 - I change
Seems like that would be the best solution. Me (and, I think, many
others), would be unlikely to used the multiple core functionality of
Solr at all. Avoiding lengthening the log messages in this case would
be nice.
check rev 607151 -- this removes the "[name] " bit for things where th
Hello! Hope you all are having nice holidays. let me lob another idea
out there and see if you think I'm crazy...
How do you all feel about changing the directory layout so it plays
nicely with maven? While we are at it, how do you feel about switching
to maven for the primary build system?
[
https://issues.apache.org/jira/browse/SOLR-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-19:
--
Attachment: solr-test-maven.zip
Here is a proposed directory structure and functional poms for a stubbed
[
https://issues.apache.org/jira/browse/SOLR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-373.
Resolution: Later
I'll close the issue now... feel free to re-open it if you have a patch.
I
[
https://issues.apache.org/jira/browse/SOLR-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-434:
---
Fix Version/s: 1.3
solrj can change everything to long without problem.
I think we can safely change
[
https://issues.apache.org/jira/browse/SOLR-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-180.
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Ryan McKinley
fixed with SOLR-414
[
https://issues.apache.org/jira/browse/SOLR-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-419.
Resolution: Fixed
This looks like it was fixed as part of SOLR-350
> SolrDispatchFilter thr
[
https://issues.apache.org/jira/browse/SOLR-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-351:
---
Component/s: search
Fix Version/s: 1.3
> external value sou
[
https://issues.apache.org/jira/browse/SOLR-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-144.
Resolution: Fixed
Fix Version/s: 1.3
Currenty there we have two cases where we parse xml
[
https://issues.apache.org/jira/browse/SOLR-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-447:
---
Attachment: SOLR-447-AdminHandlers.patch
> Register standard AdminHandlers automatica
Reporter: Ryan McKinley
Assignee: Ryan McKinley
Priority: Minor
Fix For: 1.3
Attachments: SOLR-447-AdminHandlers.patch
As admin functionality evolves, it would be nice to register a single handler
that maintains all functionality rather then keeping each
INFO: [null] /select
I just committed something that changes the default behavior to "[core]"
Perhaps we should omit the [] if it is null?
an early patch had that, but it seems a bit silly to have every log
message check for a valid core name. Right now it does:
log.warning("["+nam
[
https://issues.apache.org/jira/browse/SOLR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-142:
---
Attachment: SOLR-142-RawResponseWriter.patch
resurrecting an old patch from February. This uses the
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-409.
Resolution: Fixed
Assignee: Ryan McKinley
This was committed along with SOLR-350
> Al
[
https://issues.apache.org/jira/browse/SOLR-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-437.
Resolution: Fixed
> Remove xpp jars and XppUpdateRequestHand
[
https://issues.apache.org/jira/browse/SOLR-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-437:
--
Assignee: Ryan McKinley
> Remove xpp jars and XppUpdateRequestHand
[
https://issues.apache.org/jira/browse/SOLR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-446:
---
Attachment: SOLR-446-WriteSolrDocument.patch
> TextResponseWriter should be able to work w
[
https://issues.apache.org/jira/browse/SOLR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554525
]
Ryan McKinley commented on SOLR-446:
code extracted from SOLR-303 and added a small interface to reuse some code
Issue Type: Improvement
Affects Versions: 1.3
Reporter: Ryan McKinley
Fix For: 1.3
ResponseWriters should be able to write SolrDocuments the same way they write
Documents. This will be useful for SOLR-303 or other RequestHandlres that
modify a SolrDocument and
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554524
]
Ryan McKinley commented on SOLR-303:
{quote}
\\
For #3, are there SolrJ parts (or future parts) that we wouldn&#
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554513
]
Ryan McKinley commented on SOLR-303:
I just took a quick look... a few observations:
We should extract out a few
Thanks for getting this set up Chris!
I've been messed around with it, and think I have the hang of it. I
converted everything from the current "site" and it raised a few issues:
1. We need to figure out how to deal with dates on the old news?
Ideally we could transpose old "news" into the n
[
https://issues.apache.org/jira/browse/SOLR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554452
]
Ryan McKinley commented on SOLR-445:
yup... as is, it keeps anything it had before it fails.
Check http
Thanks Chris!
ryantxu
Enjoy your holiday and I hope you feel better soon.
Chris Hostetter wrote:
See this thread for background...
http://www.nabble.com/Confluence-wiki-vs-MoinMoin-to14207960.html
The new Solr Confluence wiki is ready for experimenting ... i played
with it just enough to c
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554053
]
Ryan McKinley commented on SOLR-350:
just committed SOLR-350-Naming.patch
>
> Ryan, if possible, I'd
[
https://issues.apache.org/jira/browse/SOLR-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-441.
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Ryan McKinley
> example app comes
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-350:
---
Attachment: SOLR-350-Naming.patch
Here is a patch that cleans up some naming and implements the SWAP
[
https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-443:
---
Attachment: solr-443.patch
Andrew, does this patch work for you?
rather then specify the contentType
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553983
]
Ryan McKinley commented on SOLR-350:
> RequestHandlers do not today know the path that requested them;
a
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553885
]
Ryan McKinley commented on SOLR-350:
> If we were to use the 'alias' to map behaviors,
how would
[
https://issues.apache.org/jira/browse/SOLR-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-442.
Resolution: Fixed
Assignee: Ryan McKinley
commited. The test creates a file on the fly
[
https://issues.apache.org/jira/browse/SOLR-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-442:
---
Attachment: SOLR-442-UseDataDir.patch
change indexDir to dataDir
> FileFloatSource should read f
[
https://issues.apache.org/jira/browse/SOLR-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-428.
Resolution: Invalid
SOLR-350 is changing to force the core name to be in the url
> Restrict va
Components: search
Affects Versions: 1.3
Reporter: Ryan McKinley
Priority: Minor
Fix For: 1.3
The FileFloatSource currently loads its file from the indexDir:
parser.getReq().getCore().getIndexDir()
This is a problem for an empty index since you get a
arted)
> Manage Multiple SolrCores
> -
>
> Key: SOLR-350
> URL: https://issues.apache.org/jira/browse/SOLR-350
> Project: Solr
> Issue Type: Improvement
>Affects Versions: 1.3
>Reporter:
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553809
]
Ryan McKinley commented on SOLR-350:
> (be it, filtered queries, query parsers, etc) would open to easy ways
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553754
]
Ryan McKinley commented on SOLR-350:
I have not looked at the recent patches yet... but I'm still wonderi
Thats a good idea. I'll make the same change in the example config.
Thanks
ryan
Apache Wiki wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Solr Wiki" for change
notification.
The following page has been changed by HossMan:
http://wiki.apache.org/solr/QueryEl
Henrib wrote:
Indeed, I reworded (plagiarized) your original proposal; sorry it took me a
full thread loop to grasp it & realize that...
About "comfort", it feels like having one name and multiple aliases per core
would be "easier" to work with than using a path-based identification; since
the
[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-418:
---
Attachment: SOLR-418-QueryBoosting.patch
Updated to accept a runtime query param "enableElev
[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-418:
---
Attachment: SOLR-418-QueryBoosting.patch
Here is an updated patch that allows you to put the
[
https://issues.apache.org/jira/browse/SOLR-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553373
]
Ryan McKinley commented on SOLR-438:
the problem with using File.pathSeparator is that you would need a different
[
https://issues.apache.org/jira/browse/SOLR-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552926
]
Ryan McKinley commented on SOLR-438:
or maybe:
{code:xml}
{code}
In general, the existence of xxx-delimiter would
Yonik Seeley wrote:
On Dec 18, 2007 9:50 AM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
perhaps we should increase the default maxConnectionsPerHost. 10? We
should also add some comment about setting it?
Yes, we should definitely change the default (probably higher... 32 or
64?). The
[
https://issues.apache.org/jira/browse/SOLR-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552865
]
Ryan McKinley commented on SOLR-438:
duplicate attribute names are bad: (no kidding)
http://www.w3.org/TR/1999/REC
[
https://issues.apache.org/jira/browse/SOLR-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552855
]
Ryan McKinley commented on SOLR-438:
I'm not sure either is a good idea, but i'll throw it out ther
climbingrose wrote:
There seems to be resource contention problem with Solrj under load. To
reproduce the problem: set up a sample webapp with solrj connect to a HTTP
Solr instance and hammer the webapp with Apache ab (say 10 concurrent
connection with 100 requests). You'll notice that the webapp
[
https://issues.apache.org/jira/browse/SOLR-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-439.
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Ryan McKinley
committed in rev 604951
Remove xpp jars and XppUpdateRequestHandler
---
Key: SOLR-437
URL: https://issues.apache.org/jira/browse/SOLR-437
Project: Solr
Issue Type: Task
Affects Versions: 1.3
Reporter: Ryan
Components: clients - java
Affects Versions: 1.3
Reporter: Ryan McKinley
Fix For: 1.3
To allow more flexability in the future, SolrServer should be an abstract super
class
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a
Chris Hostetter wrote:
: Javadocs aren't appropriate for documenting configuration and RequestHandler
: parameters/usage. These are used by many non-java folks and should have
: nothing to do with the java class structure/methods/etc
i agree that the generated javadocs are not very freindly for
Chris Hostetter wrote:
: To get that going, it looks like a Project PMC needs to file a ticket with
: infrastructure.
I can do this (or ask Doug to do it if they really want it to be the
chair) but just to clarify
: o Also specify the key name for the Space. The key name cannot be chang
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-350:
---
Attachment: SOLR-350-Naming.patch
patch to get rid of the @corename syntax and force things into
701 - 800 of 1806 matches
Mail list logo
