: > (the trick being that the servlet would need to parse the "st" info out
: > of the URL (either from the path or from the QueryString) directly without
: > using any of the HttpServletRequest.getParameter*() methods...
:
: I haven't followed all of the discussion, but wouldn't it be easier to
:
the one thing that still seems missing is those "micro-plugins" i was
[SNIP]
interface SolrRequestParser {
SolrRequest process( HttpServletRequest req );
}
I left out "micro-plugins" because i don't quite have a good answer
yet :) This may a place where a custom dispatcher servlet
On 1/16/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
interface SolrRequestParser {
SolrRequest process( HttpServletRequest req );
}
(the trick being that the servlet would need to parse the "st" info out
of the URL (either from the path or from the QueryString) directly without
u
[
https://issues.apache.org/jira/browse/SOLR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465047
]
Hoss Man commented on SOLR-107:
---
i only briefly skimmed the patch, but a couple quick questions came to mind...
1) inste
: Iterator getContentStreams();
:
: Consider the case where you iterate through a local file system.
right, a fixed size in memory array can be iterated, but an unbounded
stream of objects from an external source can't allways be read into an
array effectively -- so when it doubt go with the Iter
:
: I hate to inundate you with more code, but it seems like the best way
: to describe a possible interface.
...
the one thing that still seems missing is those "micro-plugins" i was
talking about that can act independent of the SolrRequestProcessor used to
decide where the data streams come fro
When I perform a search from indexed items..
The count name only shows partial count name, however the results show
the full name
The count Name value, shows partial state " texa ", even though in the
index is Texas for a document.
And also if I put United States, it shows a count.getName() o
interface SolrRequest
{
SolrParams getParams();
ContentStream[] getContentStreams(); // Iterator?
long getStartTime();
}
correction: this should be:
Iterator getContentStreams();
Consider the case where you iterate through a local file system.
--
In addition to RequestProces
: (I mentioned this on solr-user, but people didn't seem to respond.)
You've got to give people more then a day dude ... especially on a weekend
(a three day weekend in many parts of the US)
I already replied to your solr-user message, but you've made some
slightly different points here i'd like
[
https://issues.apache.org/jira/browse/SOLR-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465016
]
Erik Hatcher commented on SOLR-105:
---
Lets discuss this further. I'm not quite on board with document round tripping
[
https://issues.apache.org/jira/browse/SOLR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-108.
---
Resolution: Fixed
Assignee: Erik Hatcher
Applied, thanks. I did have to add if conditions on the
On 1/15/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: The most important issue is to nail down the external HTTP interface.
I'm not sure if i agree with that statement .. i would think that figuring
out the "model" or how updates should be handled in a generic way, what
all of the "Plugin" t
On 1/15/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: > SolrRequestHandler => SolrUpdateHandler
: > SolrQueryRequest => SolrUpdateRequest
: > SolrQueryResponse => SolrUpdateResponse (possibly the same class)
: > QueryResponseWriter => UpdateResponseWriter (possible the same class)
: >
: > SolrRequestHandler => SolrUpdateHandler
: > SolrQueryRequest => SolrUpdateRequest
: > SolrQueryResponse => SolrUpdateResponse (possibly the same class)
: > QueryResponseWriter => UpdateResponseWriter (possible the same class)
: >
:
: Is there any reason the plugin system needs a differ
: > Right, you're getting at issues of why I haven't committed my CSV handler
yet.
: > It currently handles reading a local file (this is more like an SQL
: > update handler... only a reference to the data is passed). But I also
: > wanted to be able to handle a POST of the data , or even a fil
: The most important issue is to nail down the external HTTP interface.
I'm not sure if i agree with that statement .. i would think that figuring
out the "model" or how updates should be handled in a generic way, what
all of the "Plugin" types are, and what their APIs should be is the most
impor
: package/project/source folder? If it is in the main tree: the unit
: tests require mysql-connector.jar and assume you have a database at:
: jdbc:mysql://localhost/solrtestsql with user=solr and password=solr.
: Any suggestions on how this should be handled or structured.
i havne't had a chance
: Log: SolrConfig says 'system property solr.solr.home not set' in the
: log, when using default Solr home
this seems like an odd thing to call out in the log ... it implies the
system proerty should be set, but using JNDI to set the solr.home is just
as valid of a way to specify where things liv
Hi,
(I mentioned this on solr-user, but people didn't seem to respond.)
It was a claim that Solr was probably not the right tool for indexing
lots of different files (e.g. PDF files) across file systems, and that
Nutch would be more appropriate. Does everyone agree with this opinion?
Solr ai
Chris Hostetter wrote:
: Ah, I hadn't realized that they might not be supported everywhere... I
I'm just trusting the javadoc for NativeFSLockFactory ... i have no idea
if it's accurate or not.
Hi! I had added the caveat about native locks based on my dicey
experience getting them working ove
variable substitution in lucene query params
Key: SOLR-109
URL: https://issues.apache.org/jira/browse/SOLR-109
Project: Solr
Issue Type: New Feature
Reporter: Thorsten Scherler
Allow
[
https://issues.apache.org/jira/browse/SOLR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464742
]
Thorsten Scherler commented on SOLR-109:
background: http://marc.theaimsgroup.com/?l=solr-dev&m=116679058126559
[
https://issues.apache.org/jira/browse/SOLR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464737
]
Thorsten Scherler commented on SOLR-86:
---
Hi Hoiss, I had a look at your version and it is good as gold.
I personal
[
https://issues.apache.org/jira/browse/SOLR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464709
]
Bertrand Delacretaz commented on SOLR-86:
-
I like the idea of a very simple "update only" client.
It's probably
On Fri, 2007-01-12 at 15:41 -0500, Yonik Seeley wrote:
> On 1/10/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> > The one hitch i think to the the notion that updates and queries map
> > cleanlly with something like this...
> >
> > SolrRequestHandler => SolrUpdateHandler
> > SolrQueryRequest
[
https://issues.apache.org/jira/browse/SOLR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464698
]
J.J. Larrea commented on SOLR-106:
--
Case for Facet Count Caching: Paging through the hitlist (as well as paging
throu
26 matches
Mail list logo
