[
https://issues.apache.org/jira/browse/SOLR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-280:
---
Attachment: SOLR-280-SolrDocument2.patch
We could go further and store boosted values as:
class Booste
slightly more efficient SolrDocument implementation
---
Key: SOLR-280
URL: https://issues.apache.org/jira/browse/SOLR-280
Project: Solr
Issue Type: Improvement
Reporter: Ryan McKinl
[
https://issues.apache.org/jira/browse/SOLR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-269.
Resolution: Fixed
> UpdateRequestProcessorFactory - process requests before submitting them
> ---
[
https://issues.apache.org/jira/browse/SOLR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-133.
Resolution: Fixed
this is the default implementation since r552198
> change XmlUpdateRequestHandler
Yonik Seeley wrote:
On 6/29/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
How do you all feel about moving:
XmlUpdateRequestHandler -> XppUpdateRequestHandler
StaxUpdateRequestHandler -> XmlUpdateRequestHandler
then deprecating XppUpdateRequestHandler?
+1
I think we could remove the XppUp
See http://lucene.zones.apache.org:8080/hudson/job/Solr-Nightly/128/changes
Changes:
[ryan] SOLR-278 - modify LukeRequest/Response to handle show=schema
[yonik] remove test properties from ant: SOLR-279
--
[...truncated 875 lines...]
AUclient/ruby