Solr replication by Solr (for windows also)
---
Key: SOLR-561
URL: https://issues.apache.org/jira/browse/SOLR-561
Project: Solr
Issue Type: New Feature
Components: replication
Affects
[
https://issues.apache.org/jira/browse/SOLR-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated SOLR-537:
Attachment: SOLR-537.patch
a new patch includes test cases.
Use hl.maxAlternateFieldLength
Namedlistcodec throws NPE for null names
Key: SOLR-562
URL: https://issues.apache.org/jira/browse/SOLR-562
Project: Solr
Issue Type: Bug
Affects Versions: 1.3
Reporter: Noble Paul
[
https://issues.apache.org/jira/browse/SOLR-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-562:
Attachment: SOLR-562.patch
Fixed the NPE and made all methods public
Namedlistcodec throws NPE for null
[
https://issues.apache.org/jira/browse/SOLR-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-562.
---
Resolution: Fixed
Fix Version/s: 1.3
committed.
Namedlistcodec throws NPE for null names
A little late to the email party but...
[ ] Keep solr logging as is. (JUL)
[ X ] Convert solr logging to SLF4J
And SOLR-560 looks good too.
- will
: In an effort to put this thread to rest with some sense of closure, perhaps we
yeah, right ... like that will ever happen :)
: [XX ] Keep solr logging as is. (JUL)
: [ ] Convert solr logging to SLF4J
-Hoss
: Yes, but why ship any libraries w/ Solr then? We should write HTTPClient for
: ourselves, as well as all the other dependencies. Class loader hell is at the
: very heart of Java and is just something we all deal with unless we go to OSGi
: (I'm told, anyway, but I don't know enough about it) or
Actually, Solr depends on Lucene :-)
SLF4J doesn't have a LogMessage to propagate to the container since it's a
simple thin facade to the logging kit you want to use. In the case of JUL
which you're a fan of and what we all think should be the default
implementation if you don't take steps to
On 3-May-08, at 9:27 PM, Noble Paul നോബിള്
नोब्ळ् wrote:
There is another class of patches like this RichDocumentRequestHandler
(SOLR-284) which brings in dependencies on other libraries, which can
safely live as a contrib project.
Do we need to raise a jira issue to track this (contrib
On Sat, May 3, 2008 at 11:30 AM, Noble Paul നോബിള് नोब्ळ्
[EMAIL PROTECTED] wrote:
A case in point is DataImportHandler (SOLR-469). As per our discussion
with Grant Ingersoll, it makes a lot of sense to make this a contrib
project rather than adding it to the core codebase.
I haven't had a
: Actually, Solr depends on Lucene :-)
Okay ... I must admit ... this is funnier then Ryan's i prefer kittens
comment.
yes, i suppose we have a core dependency on Lucene which could in theory
result in an incompatibility. That ship has sailed.
: SLF4J doesn't have a LogMessage to propagate
12 matches
Mail list logo
