Hi all,
We are trying to confirm that a Autoscaling ‘nodeAdded’ event triggers when a
node joins the cluster using the History Api.
We’ve added a node to the cluster but do not see any records in the Autoscale
History endpoint.
As a side note, we had to manually create the .system collection
t makes a nice user experience.
Aside from user history there are going to be other dynamic lists that
will be useful. Something like a "what's hot" filter that has the top
X% of titles by popularity today, this week, and this month. Or a
historical snapshot like what was popular thi
The problem is going to be 'near real time' indexing issues. Solr 1.4
at least does not do a very good job of handling very frequent commits.
If you want to add to the user's history in the Solr index ever time
they click the button, and they click the button a lot, and this
> Hi,
>
> I'm looking for ideas on how to make an efficient facet query on a
> user's history with respect to the catalog of documents (something
> like "Read document already: yes / no"). The catalog is around 100k
> titles and there are several thousand users.
Hi,
I'm looking for ideas on how to make an efficient facet query on a
user's history with respect to the catalog of documents (something
like "Read document already: yes / no"). The catalog is around 100k
titles and there are several thousand users. Of course, each user has
Accidentally I have a very similar use case. Thanks for advice.
On 7/8/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 7/7/07, Brian Whitman <[EMAIL PROTECTED]> wrote:
> I have been trying to plan out a history function for Solr. When I
> update a document with an existing u
.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik
Seeley
Sent: Saturday, July 07, 2007 9:21 AM
To: solr-user@lucene.apache.org
Subject: Re: history
On 7/7/07, Brian Whitman <[EMAIL PROTECTED]> wrote:
> I have been trying to plan out a history function
On 7/7/07, Brian Whitman <[EMAIL PROTECTED]> wrote:
I have been trying to plan out a history function for Solr. When I
update a document with an existing unique key, I would like the older
version to stay around and get tagged with the date and some metadata
to indicate it's not
I have been trying to plan out a history function for Solr. When I
update a document with an existing unique key, I would like the older
version to stay around and get tagged with the date and some metadata
to indicate it's not "live." Any normal search would not touch
hi
