Henri, SOLR-646 has been a bit of a controversy. I personally feel the
arbitrary include is a bit of a readability issue. I do not think it
matters that spring allows it because a lot of our users don't know
spring .
The problem with arbitrary include is that it can lead to inserting
one part of
[
https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630423#action_12630423
]
Yonik Seeley commented on SOLR-764:
---
bq. How is the refinement different?
The lists are m
[
https://issues.apache.org/jira/browse/SOLR-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-767.
---
Resolution: Fixed
committed.
> logged "hits" should be num matching docs, not num returned
> -
[
https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630397#action_12630397
]
Wojtek Piaseczny commented on SOLR-764:
---
I measured how long the sort takes in my case:
Thanks, it has been closed now.
-Mike
On 11-Sep-08, at 11:06 AM, Grant Ingersoll wrote:
Note, SOLR-766 is still open.
On Sep 11, 2008, at 1:23 PM, Grant Ingersoll wrote:
http://people.apache.org/~gsingers/solr/1.3.0/
Give it a try.
-Grant
[
https://issues.apache.org/jira/browse/SOLR-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas resolved SOLR-766.
-
Resolution: Fixed
> Remove python client from 1.3 distribution
> --
What about moving SolrCore & a few other key classes to Lucene then?
That would make the distinction between library versus product clearer.
--
View this message in context:
http://www.nabble.com/Configuration-features%2C-Solr2-Spring---Solr1.x-future-tp19435196p19444718.html
Sent from the Solr
Erik Hatcher wrote:
>
>
> actually, configuration _should_ be code :)
>
> there is currently too much code to parse and manage various schemes
> of loading a configuration, making things less easily dynamic and fun.
>
> Erik
>
>
Are you saying Guice versus Spring ? Like no XML con
> ... keep developing more of our own way of doing configuration when large
> parts of it overlap so
> heavily with more standard ways (Spring, etc).
>
I agree that striving to avoid technical/implementation standards overlap is
a *good* thing. Although besides Ioc/DI, I wonder what the etc c
[
https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630320#action_12630320
]
Lars Kotthoff commented on SOLR-764:
How is the refinement different? It seems to me that
On Sep 11, 2008, at 3:02 PM, Noble Paul നോബിള്
नोब्ळ् wrote:
I guess the amount of code written for configuration is
just too much.
actually, configuration _should_ be code :)
there is currently too much code to parse and manage various schemes
of loading a configuration, making things
I am quite eager to see how spring can make our life better/easier. (I
confess that I am spring illiterate)
I am not too much concerned about the current configuration (but for
SOLR-614 ). I guess the amount of code written for configuration is
just too much.
On Fri, Sep 12, 2008 at 12:13 AM, Yo
[
https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630309#action_12630309
]
Yonik Seeley commented on SOLR-764:
---
I separated out topFacets from listFacets because I as
[
https://issues.apache.org/jira/browse/SOLR-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630308#action_12630308
]
Grant Ingersoll commented on SOLR-767:
--
OK.
> logged "hits" should be num matching docs
On Thu, Sep 11, 2008 at 2:30 PM, Henrib <[EMAIL PROTECTED]> wrote:
> I appreciate your answer; a hint that your personal interest is nowhere close
> to the configuration/integration/deployment feature set.
> Do you think there is value in it ?
Sure... it's not high on *my* personal list to keep de
I appreciate your answer; a hint that your personal interest is nowhere close
to the configuration/integration/deployment feature set.
Do you think there is value in it ?
--
View this message in context:
http://www.nabble.com/Configuration-features%2C-Solr2-Spring---Solr1.x-future-tp19435196p19
[
https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630291#action_12630291
]
Lars Kotthoff commented on SOLR-764:
My gut feeling is that it's probably not worth the e
On Thu, Sep 11, 2008 at 2:24 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> There never was a Solr release that shipped with the python client, so
> it wasn't really removed.
Oh, you actually removed the file from subversion too... I had missed that.
-Yonik
There never was a Solr release that shipped with the python client, so
it wasn't really removed.
-Yonik
On Thu, Sep 11, 2008 at 1:36 PM, <[EMAIL PROTECTED]> wrote:
> Author: klaas
> Date: Thu Sep 11 10:36:54 2008
> New Revision: 694375
>
> URL: http://svn.apache.org/viewvc?rev=694375&view=rev
>
[
https://issues.apache.org/jira/browse/SOLR-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630289#action_12630289
]
Yonik Seeley commented on SOLR-767:
---
bq. An alternative would be to add a "matches" or "tot
[
https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630285#action_12630285
]
Wojtek Piaseczny commented on SOLR-764:
---
Do you think it's worth keeping lexicographica
Note, SOLR-766 is still open.
On Sep 11, 2008, at 1:23 PM, Grant Ingersoll wrote:
http://people.apache.org/~gsingers/solr/1.3.0/
Give it a try.
-Grant
[
https://issues.apache.org/jira/browse/SOLR-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630276#action_12630276
]
Shalin Shekhar Mangar commented on SOLR-768:
This is an enhancement marked for 1.
[
https://issues.apache.org/jira/browse/SOLR-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630274#action_12630274
]
Shalin Shekhar Mangar commented on SOLR-742:
The current DataImportHandler code d
[
https://issues.apache.org/jira/browse/SOLR-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630263#action_12630263
]
Grant Ingersoll commented on SOLR-766:
--
+1
> Remove python client from 1.3 distribution
[
https://issues.apache.org/jira/browse/SOLR-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-770.
--
Resolution: Fixed
> Change StAX implementation in Solr
> --
>
>
http://people.apache.org/~gsingers/solr/1.3.0/
Give it a try.
-Grant
[
https://issues.apache.org/jira/browse/SOLR-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630252#action_12630252
]
Wojtek Piaseczny commented on SOLR-768:
---
Thanks Noble. How do we get this committed?
>
On Thu, Sep 11, 2008 at 9:48 AM, Henrib <[EMAIL PROTECTED]> wrote:
> The second one is about "solr.xml" and properties; there does not seem to be
> a ready-made equivalent in Spring XML configuration.
This is the closest thing I think (but I'm no spring expert):
http://static.springframework.org/s
I'm finished my audit of the jars we include. There were missing
elements for junit, stax (now removed), and stax-utils.
In the future we should take care of updating LICENSE/NOTICE
immediately when a new jar is added.
-Yonik
[
https://issues.apache.org/jira/browse/SOLR-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-767:
--
Attachment: SOLR-767.patch
Trivial one line patch (also attached)
-rsp.getToLog().add("hits", rb.get
[
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630231#action_12630231
]
Mark Miller commented on SOLR-756:
--
Ah, your right, I've gotten a bit lost floating between
[
https://issues.apache.org/jira/browse/SOLR-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630228#action_12630228
]
Grant Ingersoll commented on SOLR-770:
--
Committed revision 694305.
Also fixed the Maven
[
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630223#action_12630223
]
David Smiley commented on SOLR-756:
---
When anyone says "dismax", there is ambiguity because
[
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630220#action_12630220
]
Mark Miller commented on SOLR-756:
--
I am not suggesting that you maintain your own, but perh
[
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630217#action_12630217
]
David Smiley commented on SOLR-756:
---
The DisjunctionMaxQueryParser in Solr does more than l
[
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630208#action_12630208
]
Mark Miller commented on SOLR-756:
--
I think the whole point of dismax is to support a very l
Dear committers,
I understand why Solr2 will use Spring at least to ease the configuration
burden wrt plugins & various factories.
There is another set of useful configuration features orthogonal to those,
the ones that make integrating/deploying/using Solr in easier ways; these
could be injected
Change StAX implementation in Solr
--
Key: SOLR-770
URL: https://issues.apache.org/jira/browse/SOLR-770
Project: Solr
Issue Type: Bug
Affects Versions: 1.3
Reporter: Grant Ingersoll
[
https://issues.apache.org/jira/browse/SOLR-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated SOLR-763:
Attachment: SOLR-763.patch
New patch with option now named enablePositions
> Support for LUC
[
https://issues.apache.org/jira/browse/SOLR-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated SOLR-763:
Summary: Support for LUCENE-1380 :: ShingleFilter.enablePositions (was:
Support for LUCENE-1
[
https://issues.apache.org/jira/browse/SOLR-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated SOLR-763:
Attachment: (was: SOLR-763.patch)
> Support for LUCENE-1380 :: ShingleFilter.coterminalPo
Upayavira wrote:
>> > As far as solr.py goes i think it's best to leave it out of 1.3 ... i
>> > think there are some patches for it in Jira, i confess that as
>> > someone who
>> > knows nothing about python i haven't paid any attention to them. it
>> > would
>> > be good to revist those at some
On Wed, 2008-09-10 at 11:40 -0700, Mike Klaas wrote:
> On 9-Sep-08, at 6:49 PM, Chris Hostetter wrote:
>
> >
> > : I was thinking that we may want to move the python client out of
> > the distro as
> > : well. It is untested with 1.3 and unmaintained.
> >
> > +1
> >
> > that seems like the best
[
https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630136#action_12630136
]
Lars Kotthoff commented on SOLR-764:
As far as I could see, "listFacets" wasn't used anyw
[
https://issues.apache.org/jira/browse/SOLR-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630134#action_12630134
]
Lars Kotthoff commented on SOLR-765:
bq. why don't you have an example/work directory?
A
46 matches
Mail list logo
