Is there an efficient way to update multiple documents with common values
(e.g. color = white)? An example would be to mark all white-colored items as
sold-out.
- Rih
This could work. Are there search/index performance drawbacks when using it?
On Mon, May 2, 2011 at 6:22 PM, Ahmet Arslan wrote:
>
>
> Is there an efficient way to update multiple documents with common values
> (e.g. color = white)? An example would be to mark all white-colored items
> as
> sol
Have the same requirement. What is your workaround for this?
On Thu, May 12, 2011 at 7:40 AM, arian487 wrote:
> I'm wondering if there is a way to get the field collapsing to collapse on
> multiple things? For example, is there a way to get it to collapse on a
> field (lets say 'domain') but A
Hey Martijn,
Did you find a good workaround?
Rih
On Sat, May 28, 2011 at 5:35 AM, Martijn Laarman wrote:
> Thanks Mike,
>
> I've opened https://issues.apache.org/jira/browse/SOLR-2553 for this.
>
> It's exciting to hear a workable implementation might be possible!
&g
formance issues with this
setup?
Looking forward to your ideas.
Rih
It will likely be what you suggested, one or two multi value fields. But
with 10,000+ members, does Solr scaled with this schema?
On Thu, May 20, 2010 at 6:27 PM, findbestopensource <
findbestopensou...@gmail.com> wrote:
> Hi Rih,
>
> You going to include either of the two fi
hu, May 20, 2010 at 11:04 PM, Ken Krugler
wrote:
>
> On May 19, 2010, at 11:43pm, Rih wrote:
>
> Has anybody done personalized search with Solr? I'm thinking of including
>> fields such as "bought" or "like" per member/visitor via dynamic fields to
>&
/favorited ) folders' provide a boost factor
> to the results.
>
>
>
> On 5/20/10, findbestopensource wrote:
> > Hi Rih,
> >
> > You going to include either of the two field "bought" or "like" to per
> > member/visitor OR a unique field per
