I agree the feature is relevant / useful. Another angle on the module vs sandbox or wherever else is maintenance cost. If a lot of code is being contributed as is here, then as a PMC member I hope to get a subjective sense that folks are interested in maintaining it. On one hand we have a number of committers here from Bloomberg, yet the abandoned and now-removed "analytics" component shows that abandonment is a risk nonetheless. I don't know how to conclude this thought but I'm hoping to hear from folks that they intend to look after this module. It's not just being "thrown over the wall", so to speak.
Naming is hard... * ...-monitor-....: sorry I hate it * ...-percolator-.... No clue why this was chosen for ElasticSearch. I can appreciate a curious/non-obvious name like this that is not going to conflict with anyone's guesses at what a general name might convey. * "indexed-queries" or "query-indexing" would be a good name? This is the best technical name I can think of. * "reverse search" came to mind (based on the Netflix article) although that makes me think of leading-wildcard / suffix-search. * "inverted-search" * "indexed-query-alerts" incorporates "alerts" thus might better convey the use-case On Mon, Apr 1, 2024 at 3:53 PM Luke Kot-Zaniewski (BLOOMBERG/ 919 3RD A) <lkotzanie...@bloomberg.net> wrote: > > Hi All, > > A few months ago I wrote the user list about potentially integrating lucene > monitor into solr. I have raised this PR with a first attempt at implementing > this integration. I'd greatly appreciate any feedback on this even though I > still have it marked as draft. I want to make sure I'm heading in the right > direction here so input from solr dev community would be extremely valuable > :-) > > Many thanks, > Luke --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
