alessandrobenedetti commented on PR #2489: URL: https://github.com/apache/solr/pull/2489#issuecomment-2153161526
> I haven't looked at this in detail but I'm wondering could we instead have a single 'q' query parser, that is itself a "query combiner" of its children clauses? Ultimately this would mean not needing all this special code in QueryComponent. I'm trying to make recommendations that "fit in" well with Solr's architecture; less bolted / hacked on. > > CC @hossman I think you'd have good inputs on this one too In principle I agree, correct me if I'm wrong, your proposed solution means: 1) a Lucene contribution to create a new query 2) a Solr query parser to combine N queries into the new Lucene one? I would need to think and design this possible solution, but I have no idea when this will happen as I am afraid it would take a significant amount of time. (of course anyone is happy to help). Do you think it would make sense to start refining this contribution, bake it in so that users have this new possibility decently quickly and then iteratively replace it? It's not because I have a strong opinion on this, I am just realistically think what could bring value from my side, in accordance with my future availabilty. Happy to discuss! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
