On Jan 19, 2007, at 11:34 PM, Yonik Seeley wrote:
On 1/19/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
So, where are we with these things now?
The one delta for my use case is getting ones that start with a
certain prefix. I'll look into adding this when I can.
The code for most of these
On Jan 19, 2007, at 9:59 PM, Erik Hatcher wrote:
I think a standalone request handler to return all the field names
in the index would be great. Anything this thing should return
other than a list of field names? I think this should be
standalone because it is separate from a search, and
On 1/19/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
So, where are we with these things now?
On Jan 11, 2007, at 2:24 AM, Tracey Jaquith wrote:
> 1) across the entire index, enumerate all the unique values for a
> given field.
&facet=true&facet.field={fieldname} can do this with the standard
req
So, where are we with these things now?
On Jan 11, 2007, at 2:24 AM, Tracey Jaquith wrote:
1) across the entire index, enumerate all the unique values for a
given field.
&facet=true&facet.field={fieldname} can do this with the standard
request handler. Right?
The one delta for my use cas
Hoss, I'm delighted to have annoyed you, if only *slightly*! ;-)
- J.J.
PS: +1 on Yonik's subsequent comment.
At 8:04 PM -0800 1/14/07, Chris Hostetter wrote:
>: - Apply the faceting criteria (e.g. facet.zeros, though facet.mincount
>: would have been a more flexible option in all cases)
>
>yo
On 1/14/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
you know what's *really* anoying? .. that my girlfriend lives 3 timezones
away.
OTOH I'm sure this factors into the extra time you can spend on Solr,
for which I'm sure many around here are glad :-)
-Yonik
: - Apply the faceting criteria (e.g. facet.zeros, though facet.mincount
: would have been a more flexible option in all cases)
you know what's *really* anoying? .. that my girlfriend lives 3 timezones
away.
you know what's *slightly* anoying? .. writing code that seems really
generic and reus
At 5:06 AM -0500 1/12/07, Erik Hatcher wrote:
>What the user-interface needs is a way to ask Solr for terms that begin with a
>specified prefix, as the user types. Paging via start/rows is necessary, and
>also sorting by frequency given some specified constraints. I like the
>start/end term i
On Jan 12, 2007, at 8:26 PM, Chris Hostetter wrote:
Yeah ... what Erik's talking about really sounds like a simple
faceting
issue: supporting prefix's for limiting the list of constraints ...
what
Tracey was talking about seems much more like Luke-esqe index info:
what
are all the fields, a
On 1/12/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
what
Tracey was talking about seems much more like Luke-esqe index info: what
are all the fields, and what are all the terms in those fields. (and what
is the docFreq of each of those terms)
Right... it's very similar in appearance, but a b
: Sounds like this stuff could/should be extensions to the current facet.field
Yeah ... what Erik's talking about really sounds like a simple faceting
issue: supporting prefix's for limiting the list of constraints ... what
Tracey was talking about seems much more like Luke-esqe index info: what
On 1/12/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
What the user-interface needs is a way to ask Solr for terms that
begin with a specified prefix, as the user types.
Sounds like this stuff could/should be extensions to the current facet.field
facet.field=year&f.year.facet.prefix=186
or
facet
Let's take this a step further, like I do with a (messy) custom
request handler in Collex. For an example, go to http://
www.nines.org/collex and type "sol" into the (slightly misnamed from
our technical perspective) "phrase" text box. The drop-down shows
all terms beginning with "sol", an
: > Attempting to enumerating
: > all of the values for a field could be dangerous
:
: We do it for faceting :-) But we don't drag it all into memory at once...
i ment trying to return them all to the user at one time ... even if we
decreased the server side memory usage risk my supporting Iter
On 1/11/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
Writing a more generic "Stats" request handler that does what you're
describing certianly seems like a good idea.
Hmmm, I hadn't thought of it as a separate handler, but as long as
these types of requests aren't related to a base query, and
: Code-searching for relevant lucene classes led me to try adding
:
: to my solrconfig.xml
holy cow, i forgot that thing even existed! ... as you can see by
skimmingthe code it's a hodge podge of misc crap that was used early on as
a simple way to test that things were working.
Writing a mor
On 1/11/07, Tracey Jaquith <[EMAIL PROTECTED]> wrote:
The Internet Archive is getting close to going live with Solr.
I have two remaining classes of problems.
1) across the entire index, enumerate all the unique values for a given field.
2) we use unrestricted dynamicField additions from doc
interesting!
Code-searching for relevant lucene classes led me to try adding
to my solrconfig.xml
This allowed me to try this request...
http://localhost:8983/solr/select?rows=0&qt=test&q=fields
which I think gets me (2) below.
--tracey
Tracey Jaquith wrote:
The Internet
The Internet Archive is getting close to going live with Solr.
I have two remaining classes of problems.
1) across the entire index, enumerate all the unique values for a given
field.
2) we use unrestricted dynamicField additions from documents. (that is
our users are free to add any named f
19 matches
Mail list logo
