[
https://issues.apache.org/jira/browse/SOLR-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613523#action_12613523
]
Lars Kotthoff commented on SOLR-612:
After having had a closer look at the code, I don't
If the current handlers remain as is (no change in config), What is
the best way to enable handlers (especially new ones) to read
arbitrary xml configuration?. The only possible solution is to use
XPath which I see as very cumbersome.
On Tue, Jul 15, 2008 at 9:11 AM, Ryan McKinley <[EMAIL PROTECT
I'm raising my objection to -1 for the updated syntax. Let's make
that a
post 1.3 (2.0, is my suggestion) feature.
Users tend to stick to a released version for very long. A lot of
users (we too) still use Solr 1.2. That means we are going to see this
syntax for atleast another year after
On Tue, Jul 15, 2008 at 12:12 AM, Erik Hatcher
<[EMAIL PROTECTED]> wrote:
>
> On Jul 14, 2008, at 12:25 PM, Noble Paul നോബിള് नोब्ळ् wrote:
>>
>> We can choose one clean syntax and stick to it .
>
> -1 to that at least in a backwards compatible support kinda way.
backward compatiblity is very
[
https://issues.apache.org/jira/browse/SOLR-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-626.
---
Resolution: Fixed
I've committed an additional fix so that scores are returned if requested in
the fie
[
https://issues.apache.org/jira/browse/SOLR-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613501#action_12613501
]
Norberto Meijome commented on SOLR-632:
---
i think is best if someone with write access t
Upgrade bundled Jetty with latest from vendor
-
Key: SOLR-632
URL: https://issues.apache.org/jira/browse/SOLR-632
Project: Solr
Issue Type: Improvement
Affects Versions: 1.3
Reporte
Thanks so much for your help, we are currently using an older version of lucene
but managed to port your fix over and it worked magnificently. We appreciate it
very much.
Sincerely,
Ramneet
--
Ramneet Tung - Developer
Ela
Provide a flexible interface for http requests that will work with
allow_url_fopen off
--
Key: SOLR-631
URL: https://issues.apache.org/jira/browse/SOLR-631
Project: S
[
https://issues.apache.org/jira/browse/SOLR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated SOLR-572:
--
Comment: was deleted
> Spell Checker as a Search Component
> ---
Spellchecker should not be case-sensitive and should be stopwords-aware
---
Key: SOLR-630
URL: https://issues.apache.org/jira/browse/SOLR-630
Project: Solr
Issue Type: Bug
On Jul 14, 2008, at 12:25 PM, Noble Paul നോബിള്
नोब्ळ् wrote:
We can choose one clean syntax and stick to it .
-1 to that at least in a backwards compatible support kinda way.
My preference is to have
value-1
value-2
because this is the most common way I have seen configuration file
[
https://issues.apache.org/jira/browse/SOLR-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613370#action_12613370
]
patrick o'leary commented on SOLR-565:
--
Been tied up with work recently
The objective of
We can choose one clean syntax and stick to it . My preference is to have
value-1
value-2
because this is the most common way I have seen configuration files
instead of.
value-1
value-2
I guess we must be able to stick to one snytax irrespective of the
underlying framework we use because c
Personally I'm -0 on this one. Adding another syntax will possibly
confuse users and us doing mailing list support when presented with
bits of the config files. More than one way to do something doesn't
seem worthwhile here.
While in general I appreciate cleaning up any kind of XML conf
+1 for committing it.
Spring may be a pretty big undertaking for which we are not ready at
this point in time. This patch should be incorporated in 1.3 so that
at least the new features can take advantage of the simpler style. I'd
even go as far as to suggest giving a uniform look to the entire
so
[
https://issues.apache.org/jira/browse/SOLR-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613310#action_12613310
]
Erik Hatcher commented on SOLR-627:
---
I've manually published the gems whenever seems reason
[
https://issues.apache.org/jira/browse/SOLR-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Smet updated SOLR-629:
Attachment: dismax_fuzzy_query_field.v0.1.diff
> Fuzzy search with DisMax request handler
> -
Fuzzy search with DisMax request handler
Key: SOLR-629
URL: https://issues.apache.org/jira/browse/SOLR-629
Project: Solr
Issue Type: Improvement
Affects Versions: 1.3
Reporter: Guillau
init-forrest-entities:
[mkdir] Created dir: /tmp/apache-solr-nightly/build
[mkdir] Created dir: /tmp/apache-solr-nightly/build/web
compile-common:
[mkdir] Created dir: /tmp/apache-solr-nightly/build/common
[javac] Compiling 35 source files to /tmp/apache-solr-nightly/build/common
20 matches
Mail list logo
