The current patch definitely supports facet before and after the collapsing.
Stephen Weiss wrote:
I just noticed this and it reminded me of an issue I've had with
collapsed faceting with an older version of the patch in Solr 1.3.
Would it be possible, if we can get the terms for all the collap
All work and progress on this patch is done under the JIRA issue:
https://issues.apache.org/jira/browse/SOLR-236
R. Tan wrote:
The patch which will be committed soon will add this functionality.
Where can I follow the progress of this patch?
On Mon, Sep 7, 2009 at 3:38 PM, Uri Boness
I just noticed this and it reminded me of an issue I've had with
collapsed faceting with an older version of the patch in Solr 1.3.
Would it be possible, if we can get the terms for all the collapsed
documents on a field, to then facet each collapsed document on the
unique terms it has col
>
> The patch which will be committed soon will add this functionality.
Where can I follow the progress of this patch?
On Mon, Sep 7, 2009 at 3:38 PM, Uri Boness wrote:
>
>> Great. Nice site and very similar to my requirements.
>>
> thanks.
>
> So, right now, you get all field values by defa
Great. Nice site and very similar to my requirements.
thanks.
So, right now, you get all field values by default?
Right now, no field values are returned for the collapsed documents. The
patch which will be committed soon will add this functionality.
R. Tan wrote:
Great. Nice site and very
Great. Nice site and very similar to my requirements.
> There's work on the patch that is being done now which will enable you to
> ask for specific field values of the collapsed documents using a dedicated
> request parameter.
So, right now, you get all field values by default?
On Sun, Sep 6,
You can check out http://www.ilocal.nl. If you search for a bank in
Amsterdam then you'll see that a lot of the results are collapsed. For
this we used an older version of this patch (which works on 1.3) but a
lot has changed since then. We're currently using this patch on another
project, but
Thanks Uri. Your personal suggestion is appreciated and I think I'll follow
your advice. We're still early in development and 1.4 would be a good
choice. I hope I can get field collapsing to work with my requirements. Do
you know any live site using field collapsing already?
On Sat, Sep 5, 2009 at
There's work on the patch that is being done now which will enable you
to ask for specific field values of the collapsed documents using a
dedicated request parameter. This work is not committed yet to the
latest patch, but will be very soon. There is of course a drawback to
that as well, the c
Anybody using it on public site? Would love to see some live examples.
On Sat, Sep 5, 2009 at 12:50 AM, R. Tan wrote:
> Okay. Thanks for giving an insight on how it works in general. Without
> trying it myself, are the field values for the collapsed ones also part of
> the results data?
> What i
>
> But, as I've discovered the field collapsing feature recently (although I
> haven't tested it), can't it solve this requirement?
>
>From the top of my head, no. The answer might change on deep thinking. It is
one of the most popular features which is yet to be incorporated into Solr.
Cheers
Av
Hmmm, interesting solution. But, as I've discovered the field collapsing
feature recently (although I haven't tested it), can't it solve this
requirement?
On Sat, Sep 5, 2009 at 1:14 AM, Avlesh Singh wrote:
> Well you are talking about a very relational behavior, Tan.
> You can declare a "locati
Well you are talking about a very relational behavior, Tan.
You can declare a "locations" and "location_*" field in your schema. While
indexing a document, put all the locations inside the field "locations".
Populate "location_state", "location_city" etc .. with their corresponding
location values.
Okay. Thanks for giving an insight on how it works in general. Without
trying it myself, are the field values for the collapsed ones also part of
the results data?
What is the latest build that is safe to use on a production environment?
I'd probably go for that and use field collapsing.
Thank you
I can't because there are facet values for each location, such as
state/city/neighborhood and facilities. Example result is "7 Eleven", 100
locations when no location filters are applied, where there is a filter for
state, it should show "7 Eleven, 20 locations.
On Fri, Sep 4, 2009 at 11:57 PM, Aa
can't you store the locations as part of the parent listing while storing.
This way there would be only one document per parent listing. And all the
locations related information can be multi valued attributes per property or
any other way depending on the attributes.
2009/9/3 R. Tan
> Hi Solrer
The collapsed documents are represented by one "master" document which
can be part of the normal search result (the doc list), so pagination
just works as expected, meaning taking only the returned documents in
account (ignoring the collapsed ones). As for the scoring, the "master"
document is
Thanks Uri. How does paging and scoring work when using field collapsing?
What patch works with 1.3? Is it production ready?
R
On Thu, Sep 3, 2009 at 3:54 PM, Uri Boness wrote:
> The development on this patch is quite active. It works well for single
> solr instance, but distributed search (ie
The development on this patch is quite active. It works well for single
solr instance, but distributed search (ie. shards) is not yet supported.
Using this page you can group search results based on a specific field.
There are two flavors of field collapsing - adjacent and non-adjacent,
the for
I think this is what I'm looking for. What is the status of this patch?
On Thu, Sep 3, 2009 at 12:00 PM, R. Tan wrote:
> Hi Solrers,
> I would like to get your opinion on how to best approach a search
> requirement that I have. The scenario is I have a set of business listings
> that may be grou
20 matches
Mail list logo