[
https://issues.apache.org/jira/browse/SOLR-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492543
]
Yonik Seeley commented on SOLR-221:
---
The results are slightly surprising.
I made up an index, and each document cont
[
https://issues.apache.org/jira/browse/SOLR-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-221:
--
Attachment: facet.patch
> faceting memory and performance improvement
> -
faceting memory and performance improvement
---
Key: SOLR-221
URL: https://issues.apache.org/jira/browse/SOLR-221
Project: Solr
Issue Type: Improvement
Reporter: Yonik Seeley
Assig
[
https://issues.apache.org/jira/browse/SOLR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492534
]
Otis Gospodnetic commented on SOLR-212:
---
Brian: interested!
> Embeddable class to call solr directly
>
[
https://issues.apache.org/jira/browse/SOLR-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492532
]
Yonik Seeley commented on SOLR-181:
---
Haven't looked at the code, but the description looks fine.
+1
> Support for
[
https://issues.apache.org/jira/browse/SOLR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492531
]
Ryan McKinley commented on SOLR-220:
I just checked in a much smaller patch that at least won't throw a status
cod
[
https://issues.apache.org/jira/browse/SOLR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated SOLR-220:
Attachment: QueryParsing.patch
the patch for "sort on undefined field"
> Solr returns "HTTP status c
Solr returns "HTTP status code=1" in some case
--
Key: SOLR-220
URL: https://issues.apache.org/jira/browse/SOLR-220
Project: Solr
Issue Type: Bug
Components: search
Reporter:
[
https://issues.apache.org/jira/browse/SOLR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-212:
--
Assignee: Ryan McKinley
> Embeddable class to call solr directly
> --
[
https://issues.apache.org/jira/browse/SOLR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-212:
---
Attachment: SOLR-212-DirectSolrConnection.patch
Updated to take an (optional) logging path
> Embeddabl
[
https://issues.apache.org/jira/browse/SOLR-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-181:
--
Assignee: Ryan McKinley
> Support for "Required" field Property
> ---
[
https://issues.apache.org/jira/browse/SOLR-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-181:
---
Attachment: solr-181-required-fields.patch
Finally got a chance to look at this. It looks good. I mad
[
https://issues.apache.org/jira/browse/SOLR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492522
]
Brian Whitman commented on SOLR-212:
Since the main use case of SOLR-212 is to embed it in client applications, we
> In an inverted index, terms point to documents. So you have to
> traverse *all* of the terms of a field across all documents, and keep
> track of when you run across the document you are interested in. When
> you do, then get the positions that the term appeared at, and keep
> track of them.
[
https://issues.apache.org/jira/browse/SOLR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492518
]
Brian Whitman commented on SOLR-212:
Much love from user land on this one. I just successfully put solr in a C app
Yonik Seeley wrote:
On 4/28/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
I have a few things I'd like to check with the Luke handler, if you call
could check some of the assumptions, that would be great.
* I want to print out the document frequency for a term in a given
document. Since that te
On 4/28/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
I have a few things I'd like to check with the Luke handler, if you call
could check some of the assumptions, that would be great.
* I want to print out the document frequency for a term in a given
document. Since that term shows up in the gi
[
https://issues.apache.org/jira/browse/SOLR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-212:
---
Attachment: SOLR-212-DirectSolrConnection.patch
Adding dataDir to an optional constructor.
> Embeddabl
I have a few things I'd like to check with the Luke handler, if you call
could check some of the assumptions, that would be great.
* I want to print out the document frequency for a term in a given
document. Since that term shows up in the given document, I would think
the term frequency must
[
https://issues.apache.org/jira/browse/SOLR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492512
]
Ryan McKinley commented on SOLR-204:
>
> should probably be something more like:
> throw new SolrException(400,
[
https://issues.apache.org/jira/browse/SOLR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492511
]
Yonik Seeley commented on SOLR-204:
---
OK cool, for something like an undefined field, it looks fine:
"undefined field
[
https://issues.apache.org/jira/browse/SOLR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492508
]
Ryan McKinley commented on SOLR-204:
sendError lets the web app decide how to format the response body. Typically
[
https://issues.apache.org/jira/browse/SOLR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-204:
---
Attachment: SOLR-204-HandleSelect.patch
applies cleanly with trunk
> Let solrconfig.xml configure the
As we move to arbitrary path based configuration, the JSP admin pages
don't really know where things are and what to link to.
In looking into how to replace get-file.jsp and how to have an upload
page for /update and /update/csv, I stumbled on the idea that we could
have the list of options
On 4/28/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
I'd like to move UpdateParams from o.a.s.handler to o.a.s.util
The other classes like it are in .util
objections?
No objections... this class and update plugins in general are very new.
-Yonik
On 4/28/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
If the configuration is in solrconfig.xml, we can set the example to use
the dispatcher but still leave the option of the 'old' style servlet if
that is desired. The only real difference between them is how errors
are returned. The dispatcher
[
https://issues.apache.org/jira/browse/SOLR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492505
]
Yonik Seeley commented on SOLR-204:
---
I wanted to try this out to see what sendError() output looks like, but the
pat
I'd like to move UpdateParams from o.a.s.handler to o.a.s.util
The other classes like it are in .util
objections?
Yonik Seeley wrote:
On 4/5/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> I'm certainly on board with adding a requestHandler mapping for
"/update",
> but i'm not sure how i feel about changing it under the covers ...
I'm suggesting we keep /update mapped to SolrUpdateServlet in web.xml,
but
On Apr 27, 2007, at 4:45 PM, Yonik Seeley wrote:
Off on a tangent: for contributors, we want to be careful about
implying that patches should always be complete, include unit tests,
and be documented. While it's nice, we'd still rather have a patch
than no patch at all.
Of course if someone is
On 4/5/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> I'm certainly on board with adding a requestHandler mapping for "/update",
> but i'm not sure how i feel about changing it under the covers ...
I'm suggesting we keep /update mapped to SolrUpdateServlet in web.xml, but map:
+1
I am no
On 4/26/07, Jason Cater <[EMAIL PROTECTED]> wrote:
I've recently implemented a SOLR solution internally. We typically use
python as our language of choice, so I needed a python library to
connect to SOLR.
Nice work. This looks like a really nice improvement on the python
client that is current
On 4/27/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
...My *personal* philosophy is probably more permissive than most:..
Thanks for sharing this, you're totally right that a half-baked patch
is better than no patch at all, and that there are different stages
which make sense in contributions
33 matches
Mail list logo
