eventually lead to something that is part of SolrJ. If that
time comes, I would like to help.
Sincerely,
Geoffrey Slinker
> On Aug 26, 2024, at 6:06 AM, Jason Gerlowski wrote:
>
> No concrete feedback for the refactor (i.e. move to SolrJ) you've got
> underway.
>
> But
ot
> underway.
>
> But I just wanted to add a note of encouragement and a +1 to the
> general idea. If it's done right a query-builder would be a huge
> boost for Solr's users IMO!
>
> Good luck w/ the refactor Geoffrey and thanks for bringing this up!
>
> J
t;>>> waste time and/or grow attached to sunk costs.
>>>>>
>>>>> Feedback:
>>>>> * avoid the word "term"; it already has Lucene definition and a Solr
>>>>> query parser but you're using it in a way that isn't eithe
>>> recommend simply for "fieldQuery" -- these queries target specific
>>>>> fields after all.
>>>>> * Can we avoid top level classes that the user must know about;
>>>>> instead having one class -- QueryBuilder (or named QueryStringBui
Solr
> query parser but you're using it in a way that isn't either. I
> recommend simply for "fieldQuery" -- these queries target specific
> fields after all.
> * Can we avoid top level classes that the user must know about;
> instead having one class -- QueryBuilder
ase check
out my branch and experiment with the code. If this is something the community
agrees that it would be a good addition to SolrJ then I will continue the
process of contributing this code.
If this is not needed please let me know.
This code is a subset of code that I use daily that has evolved over several
years. I have re-implemented only the most basic functionality.
Geoffrey Slinker
-
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org
I will refactor my idea to be found under SolrJ. Also, I will refactor trying
to better fit the domain terminology.
After I get the refactoring finished I will post a new message.
If there are those that have time to look at the branch that is in my fork of
Apache Solr, especially at the classe
specific example)? If it's nowhere
> at all, it might be an awkward thing to include. Maybe there's 100%
> test coverage but I suspect no tests for if the string is actually
> parseable and parsed as-intended (i.e. has the Query structure). If
> it's for users of Solr (whi
lusion"));
recordsGroup. setBoost(0.5f);
The code can be found here:
https://github.com/gslinker/solr/tree/QUERY_TERM_GROUPER
Unit tests provide 100% coverage on all lines of code and on all branches in
the code.
Please share your thoughts.
Sincerely
Geoffrey Slinker
-
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org
Hello,
I need a Jira account so that I can contribute to Apache Solr.
Thank you,
Geoff
-
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org
10 matches
Mail list logo
