[
https://issues.apache.org/jira/browse/SOLR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467755
]
Ryan McKinley commented on SOLR-104:
Hymm, this is awkward. I'm not quite sure what happened. But this is what I
: We should have a good notice in the config warning people to have some
: security running before enabling streaming.
yeah ... you had me convinced of that before, but i'm leaning more
towards yonik's point now: Solr has a lot of inherient trust to anyone
that can hit it directly. if/when we a
[
https://issues.apache.org/jira/browse/SOLR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-104:
---
Attachment: DispatchFilter.patch
> Update Plugins
> --
>
> Key: SOLR-104
>
[
https://issues.apache.org/jira/browse/SOLR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467787
]
Ryan McKinley commented on SOLR-104:
Ok, I just uploaded (hopefully) a final version. It takes care of (most)
ev
On 1/25/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: IMO, we should strive to be nice and not repeat keys when the
: NamedList is more of the Map variety than the List.
we should try .. but we can't garuntee .. i don't have any compelling
cases where i've needed to reuse the same name, but
: Hymm, this is awkward. I'm not quite sure what happened. But this is
Yonik inserted a phrase for this in my lexicon: Ghost in the Machine.
: > - I'm really not fond of having SolrParams.STREAM_TYPE. Can we please,
: >please leave it out for now and rely on on content-type detection?
:
BTW: i'll try to look at the newsest version of hte patch tonight.
: > - What should the expectations of
: >ContentStream.getInputStream().close() be? Should the Dispatcher
: >iterate over any Iterable streams when writing the output and try
: >to close them, ignoring any Exceptions?
: No if we add streaming to the mix, anyone from anywhere can see any
: file on your system. (Assuming the example solrconfig.xml includes
: the dump handler) With multipart upload it is easy to upload an
: enormous .exe to solr. I think the potential problems opened up by
: streaming and multi-
Add persistent HTTP connection support
--
Key: SOLR-120
URL: https://issues.apache.org/jira/browse/SOLR-120
Project: Solr
Issue Type: Improvement
Components: clients - ruby - flare
Re
[
https://issues.apache.org/jira/browse/SOLR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Coda Hale updated SOLR-120:
---
Attachment: solrb_persistent_connections.diff
Passes all tests, etc.
> Add persistent HTTP connection support
Add support for multiple-document adds
--
Key: SOLR-121
URL: https://issues.apache.org/jira/browse/SOLR-121
Project: Solr
Issue Type: Improvement
Components: clients - ruby - flare
Re
[
https://issues.apache.org/jira/browse/SOLR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Coda Hale updated SOLR-121:
---
Attachment: solrb_multidoc_adds.diff
> Add support for multiple-document adds
> ---
Add optional support for Ruby-libxml2 (vs. REXML)
-
Key: SOLR-122
URL: https://issues.apache.org/jira/browse/SOLR-122
Project: Solr
Issue Type: Improvement
Components: clients - ruby
[
https://issues.apache.org/jira/browse/SOLR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Coda Hale updated SOLR-122:
---
Attachment: libxml.rb
> Add optional support for Ruby-libxml2 (vs. REXML)
> ---
[
https://issues.apache.org/jira/browse/SOLR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467997
]
Antonio Eggberg commented on SOLR-122:
--
Even though Hpricot or Xaagly is new but they are much faster then libxml
[
https://issues.apache.org/jira/browse/SOLR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467998
]
Coda Hale commented on SOLR-122:
I hadn't seen Xaagly, Antonio -- I'll check it out.
libxml2 is definitely the most st
16 matches
Mail list logo
