Luwak is good to me!
On Tue, Apr 30, 2024 at 4:01 PM Luke Kot-Zaniewski (BLOOMBERG/ 919 3RD
A) wrote:
>
> I love the name "luwak"! I was about to suggest the same but was worried
> about the trademark concerns and I assumed there was a reason they changed
> the name when donating it to lucene.
I think I'd prefer a more self-descriptive name than "Luwak", which is just
a product name that was decided a while ago.
I kind of like "search-alerts". "query-alerts" sounds like alerting on
query metrics, but IMO "search-alerts" doesn't come with the same baggage.
Luwak is fine though if everyo
> I kind of like "search-alerts". "query-alerts" sounds like alerting on
> query metrics, but IMO "search-alerts" doesn't come with the same baggage.
Someone in the PR had mentioned that "alerts" is a bit off because the proposal
does not really manage alerts and it feels too far out of solr's do
Do people want to spend the next ten years explaining that the the alerting
feature is called “Luwak”? I’d call it “Alerting” or “Alerts". —wonder
> On May 1, 2024, at 1:16 PM, Houston Putman wrote:
>
> I think I'd prefer a more self-descriptive name than "Luwak", which is just
> a product nam
The functionality is alerts, but that doesn’t mean it has to be a push API.
Alerts can be fetched just as easily as pushed.
I don’t know the limits of this proposal, but LexisNexis needs alerting as we
move all of our 114 billion documents onto Solr. I’m retiring this week, so I
won’t be around
